[Model Edit Fix] Official Model Edit Fix Thread

[Varu]

Demon, I am just wondering how they can be pleased when it doesn't work or you don't try to help them.
All you do is flame them.

I know it can be annoying but really...it can't be pleasing when it isn't working for them or can't figure out their problem.

Really...

I on the other hand am having no problems and love this thread

[EDIT]: Spelling

Lol... If most of the people would just think about what can be wrong, most of the time they just don't put it in the right folder, or they did something to screw up WoW. If the program doesn't work there's no one else to blame but the person, as the program works for around 95% of the people who download it

[Demonkunga]

Lol... If most of the people would just think about what can be wrong, most of the time they just don't put it in the right folder, or they did something to screw up WoW. If the program doesn't work there's no one else to blame but the person, as the program works for around 95% of the people who download it

Exactly. I really am tired of all the people that come to me with problems, as I and many others don't have these problems. It is all on them, not us.

[Sabith]

What both of you said is very true

But, like I said they can't be pleased when they're screwing up=p

But yeah, I've said it's their fault too.

And...to be honest I don't do the exact way chaz has it on the MEF (the directions) I have to press HOME BEFORE it reaches my character list or else I crash. I dunno if you (demon) or chaz have to choose your realm before going into a realm every time, but I don't, it goes right to my character list that I last logged out of.

So when it says "Hand Shaking" ect I have to press HOME before it's through with all that or else I crash because it sees the model edit (My Undead Female -> Undead Male) before the MEF is re activated, which unfortunately makes me crash.

But yes, it's the live fix is definitely their own fault, dunno so much about the PTR.

And to all the people who says the MEF has a trojan "in it", there isn't one, and in fact I think it says that because the MEF is like a "hack" if you will which makes it say it's a trojan. But don't quote me on that.

[Lovemonkey]

Avast! is reporting this as a trojan, and as I know it's not, how do I make Avast! stop reporting it and disabling it?

[Destrukt]

Wow... cry more guys.
There is no pleasing any of you.

maybe if new fix actually worked like its supposed to? lol

and now im not just making some stupid mistake like putting it in the wrong folder

[Uligy]

Model Edit on PTR is dead, says that it is unable to validate the game version after the game fully loads and I press END to disable the fix... Live server Model edit is fine for me though.

I wish the old MEF guy would come back and solve all the problems we have had. QQ

[Cypher]

Model Edit on PTR is dead, says that it is unable to validate the game version after the game fully loads and I press END to disable the fix... Live server Model edit is fine for me though.

I wish the old MEF guy would come back and solve all the problems we have had. QQ

I talk to the 'old mef guy' on MSN, and I was the first one to work out how to patch the PTRs, at which point I released my fix and full instructions on how I did it. The method has changed because Blizz has added in extra security. Also, make sure you're pressing END into the MEF window rather than the WoW window.

If you don't like the work that people are doing for your (free of charge I might add), then either do it yourself or go complain somewhere else. It is working for the people who can follow instructions like WoW>Life, so please try and think about what you're doing before you come on and complain things aren't working.

Also, WoW>Life, I (and probably DK too), get a lot of PMs regarding the MEF and it can be quite frustrating to have to go through them all reading the stupid questions that have been answered 100 times in the thread, then you get the just plain ridiculous ones like "hey, did u put ttr0jan in ur progam, i not need get virus, pls help no trojan".

In short, the MEF works, you just need to follow instructions carefully, and I apologise if the mods and I seem to have a short fuse but it's because we have to put up with a lot of stuff that goes on both publicly and behind the scenes.

[Cypher]

Also, in regards to the 'trojan' claims. THERE IS NO TROJAN IN THE MEF IT IS A FLASE POSITIVE.

There are two reasons it may be flagged as a trojan.
1. It is accessing and editing the memory of a process it doesn't own, that pisses off a lot of AV software because it thinks you're trying to do something malicious.
2. The MEF is compressed with UPX to make it smaller, now this one I don't understand, UPX is open source and includes a decompression algorithm, it would take about 10 minutes worth of coding to look at the compressed executable, verify it's UPX'd and add in an auto-decompresser before scanning.

Anyway, below are the source files for both the live and PTR fixes. Now all the QQing can stop and you can compile the programs yourself if you want. I shall also release the offset to put into the fix with each update if you still don't trust my binary releases.

NOTE: I WILL NOT BE GIVING SUPPORT IF YOU CANNOT COMPILE THESE FILES, EITHER WORK IT OUT FOR YOURSELF OR DOWNLOAD THE BINARIES, THAT'S WHY THEY'RE THERE.

Recommended tools and command:
MinGW
UPX

g++ modeleditlive.cpp -o modeleditlive.exe
strip --strip-all modeleditlive.exe
upx -9 modeleditlive.exe

modeleditlive.cpp

#include <Windows.h>

int main(int argc, const char* argv[]) {
    DWORD dwOffset = 0x00CC0A44;
    DWORD dwEnable = 0x00000001;
    DWORD dwDisable = 0x00000000;

    STARTUPINFO sInfo;
    PROCESS_INFORMATION pInfo;

    ZeroMemory(&sInfo, sizeof(sInfo));
    sInfo.cb = sizeof(sInfo);
    ZeroMemory(&pInfo, sizeof(pInfo));

    if (CreateProcess(NULL, "WoW.exe", NULL, NULL, FALSE, CREATE_DEFAULT_ERROR_MODE, NULL, NULL, &sInfo, &pInfo)) {
        if (WriteProcessMemory(pInfo.hProcess, (LPVOID)dwOffset, &dwEnable, sizeof(dwEnable), NULL)) {
            while (true) {
                if (GetAsyncKeyState(VK_END)&1) {
                    WriteProcessMemory(pInfo.hProcess, (LPVOID)dwOffset, &dwDisable, sizeof(dwDisable), NULL);
                    break;
                }
            Sleep(1);
            }
        }
    }

    CloseHandle(pInfo.hProcess);
    CloseHandle(pInfo.hThread);
}

modeleditptr.cpp

#include <Windows.h>
#include <cstdio>

int main(int argc, const char* argv[]) {
    DWORD dwOffset = 0x004020F8;
    BYTE bEnable = 0x01;
    BYTE bDisable = 0x00;
    bool Enabled = true;

    STARTUPINFO sInfo;
    PROCESS_INFORMATION pInfo;

    ZeroMemory(&sInfo, sizeof(sInfo));
    sInfo.cb = sizeof(sInfo);
    ZeroMemory(&pInfo, sizeof(pInfo));

    if (CreateProcess(NULL, "WoW.exe", NULL, NULL, FALSE, CREATE_DEFAULT_ERROR_MODE, NULL, NULL, &sInfo, &pInfo)) {
        if (WriteProcessMemory(pInfo.hProcess, (LPVOID)dwOffset, &bEnable, sizeof(bEnable), NULL)){
            puts("Press END on your keyboard to disable the fix when prompted and HOME to enable it.r");
            puts("Once WoW has finished loading fully please press END then log in.r");
            puts("Once logged in (before or after entering the actual realm) press HOME to renable the fix and all model edits.r");
            puts("Hopfeully this inconvenience is only temporary, a 'better' fix is being worked on right now.r");
            while (true) {
                if (Enabled) {
                    while (true) {
                    if (GetAsyncKeyState(VK_END)&1) {
                        WriteProcessMemory(pInfo.hProcess, (LPVOID)dwOffset, &bDisable, sizeof(bDisable), NULL);
                        puts("Patch disabled");
                        Enabled = false;
                        break;
                    }
                    Sleep(1);
                }
                } else {
                    while (true) {
                    if (GetAsyncKeyState(VK_HOME)&1) {
                        WriteProcessMemory(pInfo.hProcess, (LPVOID)dwOffset, &bEnable, sizeof(bEnable), NULL);
                        puts("Patch enabled");
                        Enabled = true;
                        break;
                    }
                    Sleep(1);
                    }
                }
                Sleep(1);
            }
        }
    }
    CloseHandle(pInfo.hProcess);
    CloseHandle(pInfo.hThread);
}

[Sabith]

Chaz, I hate to complain or what ever but the newest PTR you've uploaded seems to not work.

YES, I am alt tabbing out of WoW and pressing END in the MEF itself and alt tabbing back and LOGGING IN, but it stills says invalid game version. I'll keep trying and doing different things but... your directions seem to not work lol

I'll edit if I get it to work...

I am editing this because I forgot to ask you something, do you use the new fixes you upload? (talking about PTR here and this whole post)
And does it work?

[roxen000]

cool nice job

[southsidehomie]

I don't know how you guys are getting it to work. I've been using the fix for weeks, and its worked fine.

I've downloaded the newest version (Live), run from \WorldofWarcraft, but the mef window only stays open for half a second, then WoW launches and the window closes so I am unable to focus on it to hit home/end. :S

[MNoObS]

really thanks

[S0und]

Chazwazza, iam respecting your great work, but if many ppl says that, it's not working, and hey, it's not!

"Once WoW has finished loading fully please press END then log in" - Ye, WoW is fully loaded, iam pressed END in MEF window, and then i entered my password, and look what happends ->

Question2.jpg

[Cypher]

I've been raiding for a while, just got back, okay, I'm going to test it myself and see once and for all if it is working or not.

[Cypher]

Okay, extremely sorry, off by one error.

In the following line.
push 00

I was overwriting it with
01 00

Rather than
push 01

My offset was of by one byte because I forgot to account for the size of the push instruction, that's what happens when you're in a hurry because people are QQing about a lack of updates and you PM box gets flooded. >.>

Anyway, the new offset is '0x004020F9'. New fix has been uploaded. kthx