[Announce] Model Edits 4.0.3a

[Cromon]

No, if you run it without command line (just open the exe with double click) you dont hit the assertion. The assertion is only made when argc >= 2

[Jimbob99]

p.s. Jimbob99 is a douche.

And you are obviously the kind of mindless child that gets things nerfed, broken or flat out removed in the first place.

[sitnspinlock]

cromon, you seem to have pretty good static analysis skills O.O

as for me im not that great, still learning.. correct me if im wrong but it seems to me wow generates a hash of the client data in the mpq's then its checked at runtime? so i havent gotten home yet to write it out in vs but im thinking of using openprocess for a wow handle and then using writeprocessmemory for the offset of the check function, pretty sure i have it for the current build.

OR

am i thinking about it all wrong

you tell me ;p

edit-

if im right then we can get this down to about 15 lines with a single exe.

unless ASLR playes a roll here? i used to do similar things with xp before the "protected process" was introduced with windows vista which made it harder to run shit in another procs address space.. lemme know..

[Cromon]

cromon, you seem to have pretty good static analysis skills O.O

as for me im not that great, still learning.. correct me if im wrong but it seems to me wow generates a hash of the client data in the mpq's then its checked at runtime? so i havent gotten home yet to write it out in vs but im thinking of using openprocess for a wow handle and then using writeprocessmemory for the offset of the check function, pretty sure i have it for the current build.

I haven't had a look on what the client does with its existing MPQs as i try to not mix up modified data with the original data of blizzard as it may lead to errors when patching. There is a struct with infos about each MPQ starting on 0x830130 (4.0.3 beta client) with expansion level, flags, prefix, name, ..., maybe you find something there.

unless ASLR playes a roll here? i used to do similar things with xp before the "protected process" was introduced with windows vista which made it harder to run shit in another procs address space.. lemme know..

With NtQueryInformationProcess ASLR doesnt make a bit difference.

[T4PO]

I double clicked the injector and still gives me the error >.<

[Cromon]

When you double click the exe you dont hit the assertion, you can see that in the source code. Thats actually why i didnt release any binaries at the beginning.

[T4PO]

I dont hit anything else other than just double clicking the Injector.exe

[Cromon]

Ye, i know. But hitting an assertion means not fulfill the condition in the assertion.

[coldman]

has anyone tried this on retail on a full account yet? Just curious on if the risk is high or just as high when knyox was releasing his.

[megax780]

I have tested this on real account for past two days nothing bad so far also I notice the exe doesn't stay on the whole time. When playing wow it injects the mpqs then it shuts off. But it keeps my model changes till I exit the game.

[coldman]

hmmm im a noob at C++ and compiling lol, But Cromon was nice enough to lead me in the right direction, I got the dll's and exe compiled, no errors or anything but if i click the exe before opening wow I get this message, I also get this same message when I have wow on the login screen but instead of line 66 in cmd it says line 72. Any idea what I am doing wrong?

http://i56.tinypic.com/2akh92x.jpg picture of error

[Knuckles_]

I got all that compiled on a friend's PC (can't find my VS CDs), installed the VS2010 redist. I dropped both DLL and the EXE in the WoW folder. made a brand new MPQ w/ Ladik's MPQ editor. I added files I just extracted from the game and added them like in any MPQ I already did. I run the injector w/ -nodelay , the injector cmd window opens, the game starts, I log in, but nothing is changed (changing race to race).... any idea? O.o

Edit: here how it worked:
-I asked a friend that had Visual Studio 2010 installed.
-I copied the code of the 3 files in a text file and sent him (and told him the name of each file)
-He compiled both DLL and the EXE without error and sent them back to me.
-I copied all 3 files in my WoW directory
-I created the file MpqFiles.txt in my D:\World of Warcraft\ Directory
-I entered in the text file: Data\Patch-X.MPQ (I also tried "D:\World of Warcraft\Data\Patch-X.MPQ" also copied file in the C: root and tried "C:\Patch-X.MPQ" and without " " marks but it gave the same result)
-It warned me for missing files so I went and downloaded/installed the VS2010 redistributable to have the missing files
-I Launched the game, then launched the Injector RESULT : nothing changed
-I tried with the command line (since WoW.exe is in the same folder) this : D:\World of Warcraft\> Injector.exe -nodelay RESULT: The game starts but nothing happens.
-I moved the files into the root of my D: drive and did this in command line: D:\> Injector.exe -nodelay RESULT: warned me it couldn't find the WoW.exe file <---- that was expected so it's all good.
-Next I did this in command line: D:\> Injector.exe -nodelay "D:\World of Warcraft" RESULT: Game started, nothing changed.

Can't think of anything else

[Btbam]

Nerds discussing. Stop wanking over each others nerd comments and create a program so we can use this shit.

Thanks!

[Cromon]

-Next I did this in command line: D:\> Injector.exe -nodelay "D:\World of Warcraft" RESULT: Game started, nothing changed.

Try this again and when wow runs go to the data directory and try to delete patch-X.MPQ. If it gets deleted something went wrong with injecting. If you get an error that the file is used by another process wow has locked it and its loaded correctly.

[tikigenius]

Try this again and when wow runs go to the data directory and try to delete patch-X.MPQ. If it gets deleted something went wrong with injecting. If you get an error that the file is used by another process wow has locked it and its loaded correctly.

Great little test suggestion, though I would recommend attempting to move it to another directory so you don't lose all of your work if it succeeds and that was the only copy you have! =)

Nerds discussing. Stop wanking over each others nerd comments and create a program so we can use this shit.

Looks like we need the ban hammer.