[TUTORIAL] Remove GlueXML-Check from WoW.exe

[Buddiman]

Hey,

with this tutorial i try to explain to you, how you can remove the GlueXML-check of the WoW executable, which checks wether the Interface-Files are damaged (or Edited ) or not. After Following this tutorial you should be able to edit your Interface Files without problems and you can realize many new things, such as new races/classes or simply editing the thing you see on the following screen:



Things we need:
A WoW Executable; The Program OllyDBG; This Tutorial.

WARNING!! ALWAYS backup your executable. I'm not responsible for any damage at your WoW-Files!!!!!

Now let us begin... Open the WoW-executable in OllyDBG and press F9. It should look like this:



Let us take a closer look at the picture: This black edged window shows the WoW code in assembler-language (Assembler), to open the blue window we make a Rightclick in the black one and chose > Search For -> All referenced Text Strings. We scroll in the blue window that appeared up to the beginning! Then we make right click > Search for text (select Case sensitive should be active) in the blue window and type "GlueXML" (take care of small initial letters) in! We make in the blue window now as long as we have found "ASCII "GlueXML missing signature"" right click > Search Next, mark it and press Enter! Now we can close the blue window, because from now on we are only interested in the black one! It should look approximately that way:



Therefore for our theory:

(We ignore the addresses in front in the black window, thay are only correct at 3.2.2a) We start WoW with a changed LUA file. Now WoW checks whether a LUA file of WoW is changed or not. This happens in the green edged place ,WoW declares a switch here, if with a file something is not correct, Case 0-2 is called (marked in the picture with 1,2,3) and WoW closes. Only if the file is not changed, he jumps to Case 3 and WoW starts (marked in the picture with 4.) We fortunately see because of the comments when which case of the switch begins. We must find the address of Case 3 now to which the program shall jump. The addresses are in the first column in our window and at Case 3 the adress would be at 3.2.2 a 0047D2AA (also called offset), with you it will differ at another wow version therefore you must look it itself up. If we have the address, Case 3 gets completely unimportant for the next time. Now we have to divert the Case 0-2 so that they do not end wow but jump to Case 3. The jump command for assemblers is JMP, here JMP SHORT which is only a variation of JMP.

Now we look at Case 0: We see Case 0 is executed, it pushes, makes other things and he shall execute a JMP and jump to the error message and then close WoW. Here we must change this JMP so that it jumps to Case 3. So we mark the JMP SHORT instruction and push the space bar to change it. There should be following to see: "JMP SHORT error address", you must now replace the "error adress" with the adress of Case 3 and push Assemble.

Do it the same way with Case 1.

At the End Case 2:

At Case 2 it is so that it we didn't discover any JMP, because there is another function instead of "JMP", it's "CALL". But we didn't want to WoW to reach this "CALL". We prevent this, when we press Space in the first line of Case 2 and change the command that stands there to "JMP SHORT Adress of Case 3" and press Assemble.

Every JMP you have to change is red framed, also the adress with the destination for the JMP's.


These were already all modifications. To save this into your WoW executable you have to do right click > Copy to Executable > All Modifcations, chose Copy All and make right click > Save file and save it...

Now your Game Client should load modificated LUA/XML Files properly without any error.

Additional Info:
I have mentioned if you start WoW with the Removed GlueXML-Check you get an Error in one of Blizzards LUA-Files (VideoOptionsPanels.lua) In the file (interface/GlueXML/VideoOptionsPanels.lua) you have to ccroll to the line which is given you in the error-message. Now change the following:

Code: [Select]

VideoOptionsEffectsPanelQualityLabel:SetFormattedText(VIDEO_QUALITY_S, _G["VIDEO_QUALITY_LABEL" .. quality]);  to

Code: [Select]

VideoOptionsEffectsPanelQualityLabel:SetFormattedText("VIDEO_QUALITY_S", _G["VIDEO_QUALITY_LABEL" .. quality]);  and the error should be removed.

Have fun with this Tutorial!

For suggestions, praise and criticism I'm always open. Also for Questions regarding this tutorial.

Please spread this tutorial only with mention of my name. It mustn't be changed.

[Jack]

Thanks a lot for that great tutorial, I guess the people here will appreciate it

[zimbb]

Use this tool!

[vink]

Epic!!!!
 :ulol:

[Laniax]

This topic was created more then a year ago, yet it is still something alot of us have to do.

If you want to do this; use this program in my attachment.
It lets you remove the GLUE protection and more with a simple click, or even restore them again.

screenshot:



credits for this program go to VX.

[Steff]

Thanks. Please repost in resources.

[Zim4ik]

Nice tutorial! Thanks. Helped with cata early builds

[slowy]

Hello it's possible for mac please ?

Thanks

[hardin015]

Im getting Stuck on The part of if we have address  Case 3 gets completely unimportant for the next time. Now we have to divert the Case 0-2 so that they do not end wow but jump to Case 3. The jump command for assemblers is JMP, here JMP SHORT which is only a variation of JMP.

Now we look at Case 0: We see Case 0 is executed, it pushes, makes other things and he shall execute a JMP and jump to the error message and then close WoW. Here we must change this JMP so that it jumps to Case 3. So we mark the JMP SHORT instruction and push the space bar to change it. There should be following to see: "JMP SHORT error address", you must now replace the "error adress" with the adress of Case 3 and push Assemble.
Im a little bit confused , can somebody give me  a link to a program that can just remove the GlueXML for 3.3.5a???

[hardin015]

I dont have interface/GlueXML/VideoOptionsPanels.lua PLEASE HELP!!!!

[Dlink_lip]

Im sure that this tutorial doesnt work for tbc wow. If somebody already did it for TBC. please, tell me.
Because wow.exe has an other checking. If you did that contains this tutorial. You will get an other mistake like #131 "File Corrupt"...
_________________________________

I got solution of my problem.