EQ2Harvest NULL node

[s281e47]

I've never seen this problem before but eq2harvest finds a NULL node and tries to get to it and gets stuck on it and doesn't stop trying to get it. It seems to get locked onto the NULL target from quite a distance and ignores all other nodes inbetween it.

I'm rather new to coding with innerspace but I guess I'm trying to find a way to put in the eq2harvest.iss is something like if node == "NULL" then ignore it and save it as a bad node or something?


edit: Well last night I messed around with it for a few hours trying to see if I was doing something wrong or some way to get it to work without changing the code and I had no luck but this morning I ran it for about 30 minutes in the spot that was causing me problems and I have yet to see it bug out. Maybe I just needed to restart the game client? I'll be trying it more later when I get back home but as of now it seems to be working perfect.

 

[Forlon]

s a bug with IS/ISX not supporting the ability to reference memory after a certain point. I explain it some at http://www.isxgames.com/forums/showthread.php?t=3711

So restarting EQ2 if used memory > 1.5GB will fix it, until mem useage gets that high again. I also posted a workaround so those nodes don't completely stop the script.

 

[grimgolem2]

nah, the problem is when it picks up a node, and as its running towards it, it disappears. in other words, someone else harvested it. so when the bot gets there, there's nothing to harvest. it'll throw up the null message and just continue to auto run for about a minute stuck on the "null" msg, but then it'll correct itself.

at least this is what happens in my experience thus far

 

[Kannkor]

Forlon - Hmm.. For raw curiousity sake, how did you determine it was an IS/ISX and memory issue? While anything is possible, I'm going out on a limb to say that's not the issue at all.

From my experience, there are a few things to cause a NULL, most of them result in the node disappearing for some reason or another (someone else took it, it despawned, or even lag. If it disappears from your radar, the client loses access too it, making it NULL. Depends how it is coded, but if it is put into a variable, the NULL will remain for ever unless a NULL check is in place.

New harvest bot - 01/10/10!