bad nodes not working?

[skander]

badnodes are working as it should
post your file(badnodes) here and i will check it
post your debug as well
both files as attachment

Badnodes are broken.

Attachements: badnodes.xml & Debug.html

My dwarf has now died 3 times over 5 days on the same bad node, that is listed right at the top.

and don't give me the same old EN-US language setting, that's what I'm using, you need to use a more flexible xml reader; not make us clients change at your whim, or at least have it spit out more errors.

Sorry for sounding pissed off, but... whenever Gatherbuddy acts weird it increases my chances of getting reported... the gathering time I lose is nothing in comparison. Bad Nodes are listed specifically so that the bot doesn't go chasing ghosts. It's VITAL to being a good bot.

cheers

 

[chinajade]

skander,

Thanks for providing the Debug.html and your badNodes.xml file, it helps diagnose the problem. This is a line in the very early part of your Debug.html file:

[05:58:10:479]:Error in XmlDocument load: Name cannot begin with the '-' character, hexadecimal value 0x2D. Line 27, position 63.​

If you pull up your badNodes.xml file in Notepad++, you will immediately see the problem (due to colorization and line numbers provided by Notepad++). Basically, a <waypoint> tag is missing the final ">":

<bad_location><name>Twilight Jasmine</name><waypoint-3657.027 -6135.734 13.69302</waypoint><comment>Horde camp: 23/12/2010 21:22:54 </comment></bad_location>​

When an XML file is this badly botched, there is a chance the entire file contents will be ignored.

Problems such as this are not Gatherbuddy's making, but can only be the result of incorrectly hand-editing a badNodes file. So, please don't blame Gatherbuddy for a problem of your own making.

cheers and have fun,
chinajade

 

[skander]

ok thanks.

I've run the document on my side with 2 different xml parsers and no problem was found... I'll check again...

either way, a bad nodes loading errior needs to be a full on warning before launching GB

 

[chinajade]

either way, a bad nodes loading errior needs to be a full on warning before launching GB

If you feel strongly about that, then submit an enhancement request to Bugtracker. The XML specification itself says programs are supposed to ignore tags they don't understand, and malformed elements to the best of their ability.

So, your request is to violate the XML standard, and as such it may be denied. But you never know.

cheers,
chinajade

 

[skander]

oh quit nit picking will you,

I realize I missed one '>' in my badnodes...all I'm asking is that GB gives me a proper warning before I send off my bot char to epic fail on the same node for 8 hours...

....

 

[skander]

and tbh, every gatherbot profile, including Tony's, promotes altering the badNodes.xml file...

Errors are bound to happen. But instead of acknowledging and warning the user about errors properly, GB just goes on, starts up, and pretends like the badNodes.xml file never existed...

That's a problem, in my humble opinion.

 

[mezz0]

errors with the badnodes file are usually in debug.html..