[Announce] Model Edits 4.0.3a

[RaptorMX]

Its strange that some of you got problems with client checking md5 of files, for me all model edits, race swaps etc.. work fine without any md5 changes in wow-update-xxxxx.MPQ files.

Im running human male to goblin male and blood elf priest to nelf priest with better looking body edit, also nelf's body size has been made litlebit smaller, no problems so far.

All of those files are combined to 1 file, patch-1.MPQ that is residing in Data folder.

One possible explanation for this thing is that the file names in treepaths came even more specific when Cataclysm came. It seems to me (when looking at the treepaths in the ADT) there are two 'types' of treepaths leading to the files. Ones with e.g. tileset written in capital (TILESET) and others with not (Tileset), this could be the problem since I've noticed that many of the MPQ editors combine two folders with the same name to one without looking at these differences (there might be an option to turn this off, unable to check now).

Yes, they are more specific than in wotlk, and all those teethpath's and files are case sensitive even .m2 file endings are case sensitive.
There is 2 teethpaths to files, one is "virtual" and one is by folder structure and names.

[VX2]

...Did it work ingame?

sorry, I can't tell you about this. my client not completely upgraded to cc, and I can't enter world, only glue screens. at weekends, I try to get full version and after, I could tell you something more...

I'm at home and I test it. looks like works:

but sometimes client may crash, and I think what reason of this crashes - is some incompatible animations, because I can crash "on demand" any time what I will, just by draw weapon (default key "x"). and when "it" try draw weapon, before crash, character are "explodes on separate textures":

[twilightsamus]

Holy crap, something finally works and is in screenshot form.

[Xel]

VX2, you should totally post the methods you used/create another thread.

[blaize9]

I get this error running on windows 7 Ultimate x64, ive checked that the .dll is in my system32 folder and also i placed it in my wow folder.

[Garneth]

Any word on the compiled version, Cromon?

[felibu]

Has anyone had any experience with this on live servers?
I'm wondering if this is picked up by Warden...

[Taks_]

Has anyone had any experience with this on live servers?
I'm wondering if this is picked up by Warden...

Warden is kinda crap, it only detects old hacks 'n exploits, like it does in w3..
i used this injector for quite a couple of days and still got no ban on live servers^^

nice jop btw @ te

ps:
DWORD dwFunction = dwBase + 0x6176;
its kinda crazey, eh?

[The-Eradicator]

Warden is kinda crap, it only detects old hacks 'n exploits, like it does in w3..
i used this injector for quite a couple of days and still got no ban on live servers^^

Warden can be updated to detect this. There's no guarantee they will, but there's even less of a guarantee they won't. Even the author of the program has said that multiple times.

I wouldn't recommend using this on retail if you're at all concerned about getting banned.

[joeyshinobi88]

Warden can be updated to detect this. There's no guarantee they will, but there's even less of a guarantee they won't. Even the author of the program has said that multiple times.

I wouldn't recommend using this on retail if you're at all concerned about getting banned.

Let me explain what i understand about live server safety for the masses. if anybody has anything to add or clarify be my guest.

given that bliz can update warden to detect any newly discovered tampering method at any time - as long as you're not doing anything to change how your character interacts with the environment to cheat or anything that screws blizzard out of money (i.e. race swap... i think they charge like $5?) you should go undetected on live servers.

for example. i play a goblin rogue. every time i run into a female character she looks different on my screen than she does on anybody else's because my boobmod is client side and all it changes is what i see on my computer screen... nothing else about my gameplay experience is different than that of the average wow-subscriber and blizzard is none-the-wiser.

now, if i went and did something like raise the water level in every zone so high that i'm always underwater on my client - i could swim above other players who are not effected by my client's water mod. this would make it obvious to any observer that i'm modifying the game. Same goes for terrain changes - having a super-sweet tree house in the middle of Orgermar that nobody else can see also gives you away. Worse - mesh data can be altered to have no data at all - giving you an advantage in battlegrounds by deleting the starting gate but, what i'm sure REALLY pisses blizzard off is people using it to change things that they allow you to change if you pay them money. Race-swaps are on the edge in my mind - changing your character drastically in size can possibly alter collisions with the environment (gnome/dwarf/goblin to tauren swap is what i think would be the most risky... maybe i'm crazy... as long as a tauren can go anywhere a gnome can go without getting caught because of the larger model size it'd theoretically be safe but that's one of those unknowns... if blizzard watches you have trouble going through gnome size doors too many times they may become suspicious and begin monitoring you? this is just a hypothetical situation i thought of - if someone knows better please elaborate.)

as i gather it, seeing how model editing has changed over the past few years, model editing will probably never be killed completely. every hole that's patched only forces model editors to examine the changes and adapt like the borg... we are foxes always a step ahead of the hound, and it seems the longer we don't give away our positions the better... it is NOT suggested that you run any mod on a live server what-so-ever because the more people who abuse the art in blizzards eyes the more blizzard knows what they need to do to make thing's harder for us.

tl:dr using a mod on a live server is as safe as what-ever you plan to do... as long as you don't do anything stupid or obvious, blizzard wont know to change warden to catch you and everybody else.

[The-Eradicator]

Let me explain what i understand about live server safety for the masses. if anybody has anything to add or clarify be my guest.

given that bliz can update warden to detect any newly discovered tampering method at any time - as long as you're not doing anything to change how your character interacts with the environment to cheat or anything that screws blizzard out of money (i.e. race swap... i think they charge like $5?) you should go undetected on live servers.

for example. i play a goblin rogue. every time i run into a female character she looks different on my screen than she does on anybody else's because my boobmod is client side and all it changes is what i see on my computer screen... nothing else about my gameplay experience is different than that of the average wow-subscriber and blizzard is none-the-wiser.

now, if i went and did something like raise the water level in every zone so high that i'm always underwater on my client - i could swim above other players who are not effected by my client's water mod. this would make it obvious to any observer that i'm modifying the game. Same goes for terrain changes - having a super-sweet tree house in the middle of Orgermar that nobody else can see also gives you away. Worse - mesh data can be altered to have no data at all - giving you an advantage in battlegrounds by deleting the starting gate but, what i'm sure REALLY pisses blizzard off is people using it to change things that they allow you to change if you pay them money. Race-swaps are on the edge in my mind - changing your character drastically in size can possibly alter collisions with the environment (gnome/dwarf/goblin to tauren swap is what i think would be the most risky... maybe i'm crazy... as long as a tauren can go anywhere a gnome can go without getting caught because of the larger model size it'd theoretically be safe but that's one of those unknowns... if blizzard watches you have trouble going through gnome size doors too many times they may become suspicious and begin monitoring you? this is just a hypothetical situation i thought of - if someone knows better please elaborate.)

as i gather it, seeing how model editing has changed over the past few years, model editing will probably never be killed completely. every hole that's patched only forces model editors to examine the changes and adapt like the borg... we are foxes always a step ahead of the hound, and it seems the longer we don't give away our positions the better... it is NOT suggested that you run any mod on a live server what-so-ever because the more people who abuse the art in blizzards eyes the more blizzard knows what they need to do to make thing's harder for us.

tl:dr using a mod on a live server is as safe as what-ever you plan to do... as long as you don't do anything stupid or obvious, blizzard wont know to change warden to catch you and everybody else.

This used to be the case, but that was when you were just editing client data files.

This is an actual modification of the game client, and is thus a far more serious offense, no matter how you use it.

[joeyshinobi88]

This used to be the case, but that was when you were just editing client data files.

This is an actual modification of the game client, and is thus a far more serious offense, no matter how you use it.

more serious an offense indeed but how is the risk of getting caught different than before? please elaborate.
.

[BLUBBER511]

will this work with patch 4.0.6?

[Jimbob99]

will this work with patch 4.0.6?

No, the patch breaks it at the moment.
Probably just needs recompiled with a new offset.

[Havoc06911]

Hopefully a new injector is created cause just confirmed what Jimbob99 says about the patch breaking when trying to use the injector