Forum > Resources and Tools

[Project] Removing the Failsafe in 3.3.5

(1/3) > >>

Gurluas:
I have been researching a very annoying pheonomenon regarding 3.3.5 which causes it to filter any unnatural skin, face, haircolor etc. to value 00.
Say, you make a Blood elf with deathknight eyes, in this case face 10, anyone else will see a Blood elf with face 00.
This was not the case in earlier versions such as 1.12.1.

In my server, I wish to give access to skins such as Mag'har, or High elves to all players.
Since the client has been edited before, for instance, to enable new races, would it be possible to edit it to remove the failsafe?

I would gladly cooperate with anyone to make this possible.

PS. This has NOTHING to do with model editing. This isn't about replacing a current skin with an npc skin, it's about letting players use the npc skin directly, which is possibly but the client filters it away.

I hope anyone with experience can help.

Oh and here is a screenshot to demonstrate how it works in 1.12.1:
http://oi35.tinypic.com/2vta4wl.jpg


This was originally posted on Ownedcore, but I am sure some of you can find a way to help.
http://www.ownedcore.com/forums/world-of-warcraft/world-of-warcraft-bots-programs/wow-memory-editing/411516-help-removing-failsafe-3-3-5-a.html#post2732302

Ascathos:
Right off the bat, is that a client limitation ?

Gurluas:

--- Quote from: "Ascathos" ---Right off the bat, is that a client limitation ?
--- End quote ---

The Trinity core devs says it is, and 3.3.5 has it, 1.12.1 doesn't, so yeah I am pretty sure it is a client filter.

Somewhere along the line it filters away anything non-normal, such as Deathknight skins on other classes or npc skins.

Ascathos:
This is a personal opinion, but, I think removing that is not possible. I assume that it is sort of a client-side information, transmitted from server to client with the core information, e.g. skin data, where it validates, before moving it serverside-wise to the clients for another check. I do not believe this to be client-wise. I could imagine, though, that the charsections flags 0x2 which is not further used is somehow related to this. We'd need to see what previous data these "core" files contain (CharSections, etc.)

Gurluas:
Hm it is possible, but from a quick glance they seems identical. (Sans all the non implemented stuff ofc)


I tried removing the NPC flag from those skins, yet the block serverside remained, even when the changed DBC was used. This led me to believe it was either a server core thing or a clienside thing.

Whether we disable it, or add all skins to the "allowed" list, both works fine for me.

Navigation

[0] Message Index

[#] Next page