trouble with eq2bot pathing

[anongamer]

Hi. I am having trouble getting the different pathing options to work right. I've gotten the dungeon crawl mode to run properly one time but when I tried to adjust it I broke it again.

I am creating PoI points running around lowbie zones to try to figure out how to make it work. The bot seems to stop responding to the movement because the status keeps quickly saying Moving to start... moving to point1, point2 ... all the way through my list of points, but the bot never moves. Can someone help me out with this please?

Since I can't seem to get a basic path with 4 PoI's to work repeatedly I am assuming I am doing it wrong.

Thanks

 

[anongamer]

I think I just wasn't mapping the area out well enough. I just took 10 minutes running back and fourth over the a large area and it started working pathing around all of my waypoints as expected.

 

[Pygar]

It is fairly particular and covering more ground for linked points does increase its ability to successfully nav.

The code that moves it from un-naved regions back to the saved path is sketchy at best.

This type of AFK automation tool though has not been high on our list of enhancements for the bot.

In essence, the fact that this feature is difficult and takes time to understand keeps the number of afk bot crews I see running on my server lower.

 

[anongamer]

It is fairly particular and covering more ground for linked points does increase its ability to successfully nav.

The code that moves it from un-naved regions back to the saved path is sketchy at best.

This type of AFK automation tool though has not been high on our list of enhancements for the bot.

In essence, the fact that this feature is difficult and takes time to understand keeps the number of afk bot crews I see running on my server lower.

Fair enough. I guess I will spend the time and start working on my own scripts for this game. I haven't really written any complex macros since I quit playing vanguard awhile back so I was hoping this would work for me.

 

[Pygar]

Fair enough. I guess I will spend the time and start working on my own scripts for this game. I haven't really written any complex macros since I quit playing vanguard awhile back so I was hoping this would work for me.

Fair enough.

Amadeus has been very clear that the goal of ISXEQ2 was not to provide AFK automation tools. I and many of the core contributors agree with this stance as it is this stance alone that has kept SoE from targeting us directly like they have other automation software. The writ limit in Craft, and the timer in ogre harvest are prime examples of this philosophy.

I've been on the fence about updating this code in EQ2Bot. As if I made it easy to do and public, I'd have to also add the controls to force it to shut down after a timeout period. Fact is, most of the userbase for the bot is using it for boxing vs afk botting and my efforts have been directed to reflect that.

That being said, if you created a navigation / movement script and had it pause when aggro is detected, you can run eq2bot in manual movement mode and it will react to aggro and kill stuff and loot for you. Just be careful about the custom actor array, and do not create an array with different options than what the bot is using.

If you for example created an array that didn't include all possible aggro npc types, the bot would read that array and no longer detect aggro correctly.

A shared 'common code' actor array management widget is one of those community scripting objects that is still needed and currently on the list to get to eventually.

 

[anongamer]

Fair enough.

Amadeus has been very clear that the goal of ISXEQ2 was not to provide AFK automation tools. I and many of the core contributors agree with this stance as it is this stance alone that has kept SoE from targeting us directly like they have other automation software. The writ limit in Craft, and the timer in ogre harvest are prime examples of this philosophy.

I've been on the fence about updating this code in EQ2Bot. As if I made it easy to do and public, I'd have to also add the controls to force it to shut down after a timeout period. Fact is, most of the userbase for the bot is using it for boxing vs afk botting and my efforts have been directed to reflect that.

I definitely understand the position you guys have taken and there is no resentment on my part. I think it is a smart stance for the product to take and makes the most sense from the isxgames team's perspective and probably for the isxgames community as well.