Hoping for a way to disable returning to hotspot while gathering.

So while gathering it has become more noticeable in heavensward that once finished with a node set it returns to the center of the hotspot it first stopped at prior to gathering before moving on to the next hotspot. Not an issue prior to heavensward because all of the nodes fit inside and were detectable in one hotspot.

In a stealth profile I had made, I had hoped to prevent this by adding the "<Gather Loops="2"> I had seen in older unspoiled nodes. So that way once the last of the twin nodes was gathered for a hotspot it went straight to the next hotspot or gather point. Sadly that does not complete that objective.

My concern is that while gathering, the bot moves to the hotspot location. Then detects the nodes and gathers, once completed it returns back the exact same hotspot. Finally the bot moves on to the next pair of nodes/hotspot. No human player acts in this way. Its close but once they finish the second node they are already moving to the next hotspot. Is there an easy way to try and override with a chunk somehow to end the gather objective if two nodes are completed/perished? So that it does not return to the center before moving on with the profile.

I know mastahg has a lot on his to do list so I am curious if somebody else can possibly think of a work around for this.

 

The best I've found is to set the hotspot right next to where one of the nodes spawn so when it runs there it looks like you are going to harvest. Even when the nodes didn't spawn there since other players can't see your nodes.

 

https://www.reddit.com/user/Lorthew

Seems this guy has a vendetta against botters. lol I thought it was bad looking myself but when you see it talked about on reddit which is full of people who care way too much. He is way off on the majority of his claims but close on some.

 

There are always a few that see bots as the end of the world.

 

You could use an inherited class based on the Gather class/tag (called GatherNoReturn or something) and place it in the OrderBotTags folder in the PlugIns directory.

Unfortunately, Profile Tags seem to have a tough time decompiling for me so I can't tell exactly what the Gather tag does in coding terms, which makes overriding the correct methods very difficult. If I could openly read all related code, I could just override the specific method that returns to the hotspot center after mining all detected node to bypass that part and run to the next hotspot instead.

The other option is to create the new tag from scratch, simulating what the current Gather tag does as best as possible through code; this might be easier if the actual Gather Tag class cannot be seen, but it would also take a good chunk of work and testing to make sure it behaves correctly.

 

Thanks for the replies! Sounds like even more reason to speed up me getting even a small coding background.