Issues with harvesting bot since LU37
- Thread starter dogface
- Start date
insanitywiz
Senior Member
Check your movement keys in moveto.iss, make sure they match up with the movement keys you use in game.
This is the error i'm getting after trying to run the harvester.
any suggestions?
Code:
navpath object type is deprecated. LavishNav can be used in exactly the same way
navpath object type is deprecated. LavishNav can be used in exactly the same way
navpath object type is deprecated. LavishNav can be used in exactly the same way
navigation object type is deprecated. LavishNav can be used in exactly the same way.
navpath object type is deprecated. LavishNav can be used in exactly the same wayspeedycerv
Active Member
Thanks for the avatar relative advice, I was wondering if that backing up and sideways walking normal. Any info on: 1. what "roaming range" does? (either range it will gather nodes off the beaten path? or something else? because it doesn't seem to go 30m out of the way when i put in 30, maybe it's just me) 2. What is the Distance outside max roaming range is for?
On another note it will end the script at times, and not delete the things I picked to delete that were harvested, anyone else experience this?
Edit Update: I found out that by looking at a file (Harvest.xml), that for tier 1 the ore name is incorrect, it should be "blemished ore". But i changed it, and the bot still harvests everything but the ore. Any idea what needs to be changed?
On another note it will end the script at times, and not delete the things I picked to delete that were harvested, anyone else experience this?
Edit Update: I found out that by looking at a file (Harvest.xml), that for tier 1 the ore name is incorrect, it should be "blemished ore". But i changed it, and the bot still harvests everything but the ore. Any idea what needs to be changed?
Last edited:
Pygar
EQ2Bot Specialist
Sigh, I'm tired of answering all the same old questions.
Movement is controlled by moveto.iss. There are key definitions in this file that MUST match the in game movement keys.
Harvest.xml contains a list of node names by ZONE. And if you are skipping nodes, its for one of the following reasons:
1. Your character config file is hosed and the UI value of selecting ore is not applying. Delete your character config file and restart the script
2. the node name under the xml set for the ZONE NAME you are in is in correct. This is tricky as some zones have more than one ore name, and the bot only works with one. Make sure it matches correctly using exact case. Also, the ID number next to the name is what tells it that name is ore,wood, etc, so if the ID is wrong it wont work.
3. The node was previously unreachable and is now marked as a badnode, and will be skipped until you restart the script.
Regarding settings:
Roaming Range is the distance it scans for nodes from the navpath. Any node found in that distance it will try to nav to. It will ignore nodes in that range that are more than 10 delta-y from you (too far above or below).
Distance outside of max range. When it paths to a node to harvest it, before returning to the path, it first checks for other nodes nearby. This uses this Distance outside of max range setting to check for other nearby nodes before returning to the path to use the normal roaming range distance check.
This is important to do otherwise you would run way over from your path, get a node, return to the path, then run way back over to a node that was only 10 distance from the first node, and keep repeating. Looks really suspicious.
View Relative vs Avatar Relative, I have no idea what impact that might have. However if setting one of those options causes a,w,s,d,q,e,num lock to move the camera rather than turn your toon, then yes thats going to fuck up the bot, as it expects those keys to move, turn, backup, strafe, and autorun perspectively.
Providing those keys cause your toon to move as expected, the bot can and will path you around as needed.
The same is true for other scripts that move your toon. EQ2Bot uses its own movement key definitions near the top of eq2bot.iss. Craft and Harvest both use the commands in moveto.iss.
Now seriously, I'm not going to answer this question again.
Pygar
Movement is controlled by moveto.iss. There are key definitions in this file that MUST match the in game movement keys.
Harvest.xml contains a list of node names by ZONE. And if you are skipping nodes, its for one of the following reasons:
1. Your character config file is hosed and the UI value of selecting ore is not applying. Delete your character config file and restart the script
2. the node name under the xml set for the ZONE NAME you are in is in correct. This is tricky as some zones have more than one ore name, and the bot only works with one. Make sure it matches correctly using exact case. Also, the ID number next to the name is what tells it that name is ore,wood, etc, so if the ID is wrong it wont work.
3. The node was previously unreachable and is now marked as a badnode, and will be skipped until you restart the script.
Regarding settings:
Roaming Range is the distance it scans for nodes from the navpath. Any node found in that distance it will try to nav to. It will ignore nodes in that range that are more than 10 delta-y from you (too far above or below).
Distance outside of max range. When it paths to a node to harvest it, before returning to the path, it first checks for other nodes nearby. This uses this Distance outside of max range setting to check for other nearby nodes before returning to the path to use the normal roaming range distance check.
This is important to do otherwise you would run way over from your path, get a node, return to the path, then run way back over to a node that was only 10 distance from the first node, and keep repeating. Looks really suspicious.
View Relative vs Avatar Relative, I have no idea what impact that might have. However if setting one of those options causes a,w,s,d,q,e,num lock to move the camera rather than turn your toon, then yes thats going to fuck up the bot, as it expects those keys to move, turn, backup, strafe, and autorun perspectively.
Providing those keys cause your toon to move as expected, the bot can and will path you around as needed.
The same is true for other scripts that move your toon. EQ2Bot uses its own movement key definitions near the top of eq2bot.iss. Craft and Harvest both use the commands in moveto.iss.
Now seriously, I'm not going to answer this question again.
Pygar
Pygar
EQ2Bot Specialist
Oh, something to try out on view relative and avatar relative.
The other mechanic the bot uses for movement is the /face command.
So go somewhere with these 2 settings that you can /face somenpc or /face somenode.
It is our expectation that /face will turn your toon to face that actor. However, if either of those 'relative' settings cause the camera to fact the actor vs turning your character to face that actor, thats going to be a problem.
You must use whatever setting allows /face to actually turn you're character.
The other mechanic the bot uses for movement is the /face command.
So go somewhere with these 2 settings that you can /face somenpc or /face somenode.
It is our expectation that /face will turn your toon to face that actor. However, if either of those 'relative' settings cause the camera to fact the actor vs turning your character to face that actor, thats going to be a problem.
You must use whatever setting allows /face to actually turn you're character.
speedycerv
Active Member
After looking at all the reasons why it would skip all the ore in the zone that you gave, i'm sure that the reason is number 2.
"2. the node name under the xml set for the ZONE NAME you are in is in correct. This is tricky as some zones have more than one ore name, and the bot only works with one. Make sure it matches correctly using exact case. Also, the ID number next to the name is what tells it that name is ore,wood, etc, so if the ID is wrong it wont work."
The original name under oakmyst was combine ore I believe, I changed it to blemished ore, but you are saying that some zone may have more than one name for ore. though I couldn't find any combine ore. But either way you are saying the ID number must match, so where is the id number so I can change it, and how do i find out what the id number should be? Thanks for answering all these questions you've been asked probably a thousand times, and for your patience.
"2. the node name under the xml set for the ZONE NAME you are in is in correct. This is tricky as some zones have more than one ore name, and the bot only works with one. Make sure it matches correctly using exact case. Also, the ID number next to the name is what tells it that name is ore,wood, etc, so if the ID is wrong it wont work."
The original name under oakmyst was combine ore I believe, I changed it to blemished ore, but you are saying that some zone may have more than one name for ore. though I couldn't find any combine ore. But either way you are saying the ID number must match, so where is the id number so I can change it, and how do i find out what the id number should be? Thanks for answering all these questions you've been asked probably a thousand times, and for your patience.