this happens when you edit something in the xml the game can't read like say <Scale_Factor>0.7</Scale_Factor and there is no > at the end there the game will exception and when the game gives you the _logfile.txt and _except.txt they don't even tell you the problem they only show a crap load of number.
Sorry to say the only wait to fix this is to open every xml you've edited with your mod and open them in firefox and if they load and you can see everything thin it's ok thin go onto the next one but if it doesn't load and shows you a XML Parsing Error: not well-formed look down and follow these Line Number (whatever number it gives you), Column (same thing as in line number):
If your using notepad++ follow the numbers on the side with the line number given and that is where your error is.
Thin refresh firefox and if the xml loads and doesn't give you a XML Parsing Error: not well-formed thin your good and the game is fixed
I wans't really saying I have a problem with the mod right now, just that I get tired of seeing it. I was posting this since almost every modder has most likely seen this. And I already know how to fix it. I just really don't like looking through 10-15 xmls to find the problem.
Unfortunately, sometimes players using mods get these, too. Some mods are worse than others in this regard (this is not one of the bad ones). Yeah, though, these are a pain.
I see this about 20 times a day when I have modding sessions.
Best way to resolve the problem is make edits to one file at a time and test the game each time you do that. That way you don't have to browse through 9 files figuring out which one has the problem.
As a student of web design, I work with xml coding and can attest to the unending frustration that can come from a tag being left out. This is why I use Notepad++; color coding, syntax checking, -etc. really help in ensure a clean xml file. My advice is to always check the color coding first. In the version I am running, correct tags are shown in purple highlight. :-)
Probably irrelevant here but,... WHAT THE HECK HAPPENED TO MODDB? I don't know what the heck is going on, but this whole page is looking like a poorly put together microsoft word document! (if this makes no sense to you, please disregard)
this happens when you edit something in the xml the game can't read like say <Scale_Factor>0.7</Scale_Factor and there is no > at the end there the game will exception and when the game gives you the _logfile.txt and _except.txt they don't even tell you the problem they only show a crap load of number.
Sorry to say the only wait to fix this is to open every xml you've edited with your mod and open them in firefox and if they load and you can see everything thin it's ok thin go onto the next one but if it doesn't load and shows you a XML Parsing Error: not well-formed look down and follow these Line Number (whatever number it gives you), Column (same thing as in line number):
If your using notepad++ follow the numbers on the side with the line number given and that is where your error is.
Thin refresh firefox and if the xml loads and doesn't give you a XML Parsing Error: not well-formed thin your good and the game is fixed
I wans't really saying I have a problem with the mod right now, just that I get tired of seeing it. I was posting this since almost every modder has most likely seen this. And I already know how to fix it. I just really don't like looking through 10-15 xmls to find the problem.
Unfortunately, sometimes players using mods get these, too. Some mods are worse than others in this regard (this is not one of the bad ones). Yeah, though, these are a pain.
I see this about 20 times a day when I have modding sessions.
Best way to resolve the problem is make edits to one file at a time and test the game each time you do that. That way you don't have to browse through 9 files figuring out which one has the problem.
As a student of web design, I work with xml coding and can attest to the unending frustration that can come from a tag being left out. This is why I use Notepad++; color coding, syntax checking, -etc. really help in ensure a clean xml file. My advice is to always check the color coding first. In the version I am running, correct tags are shown in purple highlight. :-)
Ah this used to be a massive problem for me!!
Install XMLPad and use that to edit your xml's.
It automatically tells you if there is an error due to a piece of code missing! eg a missing >
Probably irrelevant here but,... WHAT THE HECK HAPPENED TO MODDB? I don't know what the heck is going on, but this whole page is looking like a poorly put together microsoft word document! (if this makes no sense to you, please disregard)
NVM...