Fixing a super annoying error

[J-Fire_Man 0]

Hmm....after modding ZH for quite a long time, the most annoying error I've ever faced is an error which even the application can't locate the source of the error, the game wont's start until you repaired the error. This could be really annoying if you can't find the solution, but there is always a solution to solve a problem. by far, I only know one way to fix this super serious error, and that is to check the INI manually and repair the source of the problem. Try to remember how many ini files and codes have you modded. And then after you know how many INI files you have modded, move the INI files that you modded one by one to other directory (it will be better if you put it outside ZH directories). Everytime you move the INI file, run the ZH application, this is important to locate the source of the problem. If there is no error, that means the error souce is located in the file that you moved. But, if there is still an error, move back the INI files that you moved to INI directory, and then move another INI. Try doing that constantly until you get no error message.

 

But beware, when you got an error, check the "ReleaseCrashInfo.txt" located in your My Document's zero hour directory. If the text say "Reason Uncaught Exception...." then you should continue moving the INIs. But if it say like "Error parsing INI............", ussualy it will tell you about the source of the error, reapir it first, then continue moving the files.

 

If you have finished doing all those things, and found the INI file which the contains source of the error, it's now the time to check the codes. This will spin your head if there are lots of codes in the INI, I meant VERY lots of. Now you have 3 options, first is to check the entire codes in the INI and find the wrong code. If you're lucky, you will found it fast. If you don't want to check the entire codes (I prefer this second way because I'm not crazy enough to waste my time by looking at all of the codes), there is a second way, and this is like the way you did to find the INI file which is the source of the problem. Try to remember the codes that you have modded or the new objects or something that you have added to the INI. Now, move or delete or cut the codes per "Object", and then run teh application. Do it constantly until you get no error. And the fix the error. If you are too confused about the first and the second way, there is still the last way, rebuild the entire codes in the INI.

 

Usually all of this kind of problem was caused by a mistype. Last time I got this error because only a letter, and the damn "S" So I just delete it and things go ok again.

 

If you have any question, ask it here. Or, if you already loss hope about repairing it, I maybe will help you. But....dunno :?

 

My advice is, if you are planning to mod a game, mod it carefully, and becarefull of mistyping :wink:

[Koen 2]

To catch the typos, I might know another way:

Start a TibEd 2 project, then go to the project explorer and delete all files and import your own. Now, if you select "SpecialPower" for SpecialPower.ini and TibEd gives an error (crashes) then you know there is something wrong with the opening and closing tags in your file somewhere.

You can only use the TibEd 2 parser this way to catch opening/closing tag errors, but still it's better then nothing sometimes.