Quote from: "Buddiman"

Hey guys,

do you know a place where to find the GlueXML and FrameXML functions used in LUA-files for Interface Creation?

wowwikis list is not complete.
Maybe there is already a list of functions and the parameters used out there.

Otherwise I see no other chance than having fun with IDA Pro :/

When you search strings in the binary it displays all the function names as strings. This would give you a reference list which you could compare to the ones on wowwiki / wowdocumentation.

You shouldn't need to know the parameters - when you try to use the functions, it will tell you "expected number value got nil" or something similar, telling you it wanted an integer/float not a nil (no) value. You can get the correct parameters through trial and error through this method.

Ok thank you

When I have enough time I start writing a function documentation

I quitted WoW modding and WoW in general for a while, but now I started again because it's really fascinating.

The Tutorials helped me to get an quick overview of all the things again (German Translation).
(Especially Part 2 - a really practical Environment).


But I think I found an Error in Part 2 -> The extraction settings showed in Picture


"Delete all existing files in the target directory", I think you should not set this option on all MPQ-Archives. If you do, you will have at the end only the content of  "patch-enUS-3.MPQ" in the ClientFiles Folder.


Also a question, is everyone allowed to continue the translation of the tutorials or only the Member who translated the first parts? I could help translating into german

To be clearly, what did you change? I'm talking of MAX_RACES = RACECOUNT; line 2 in CharCreate.lua.

Ok it was my fault. Very stupid fault I have made, sry. I calculated sizeof(MDDF)*numberof(filenames). But actually there can be more than one MDDF Block for one Filename.

With this fixed, I can use my tool. But when I try to change an existing WMO, this happens ingame:


The filepath is not wrong, I have checked it with a Hexeditor. Is there something like a boundingbox that I need to change? Maybe the MCNK-Chunk in the obj0-Files, even now I don't know exactly what they do, only that if there is no entry no Model gets spawned.

Maybe someone had the same error or has seen it somewhere

I think all the tutorials for really new beginners will come soon enough.

To your question for the WoW-version, i would choose 3.3.0 or 3.3.2... You can edit all the files and most of the stuff for newer versions is really good documentated (e.g. look at wowdev wiki at madx.dk)

The other questions i think its better to wait for tutorials. I think I'll go to write some tutorials in the next days.

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:

VideoOptionsEffectsPanelQualityLabel:SetFormattedText(VIDEO_QUALITY_S, _G["VIDEO_QUALITY_LABEL" .. quality]);  to
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.