Unexpected movement behavior

[mistahmikey]

On a toon that has "Move To Area" and "Auto Follow Mode" checked, I set a campspot. The toon is set to follow "Me". I move away from the toon; it stays put as expected.

I then uncheck "Move To Area" and "Auto Follow Mode", then call "OgreBotAtom a_StopFollow" followed by "OgreBotAtom a_LetsGo". I would have expected the toon to not move, and be in a state that I could now move it manually without it a) trying to run back to me or b) trying to run back to the campspot. However, it runs right back to me as if it is still in the "follow" state. If I then reissue "OgreBotAtom a_StopFollow", then it stops following me. Its as if either "OgreBotAtom a_LetsGo" somehow reconstituted the "follow" state, or "OgreBotAtom a_StopFollow" was ignored while the toon was in the "campspotted" state.

Not sure if this is a bug or a feature. However, if its a feature, I really would appreciate some wisdom on what I need to do to "release" an individual toon from its "campspotted" and "follow" states simultaneously so it stays where it was when campspotted and I can then move it manually if I desire.

 

[Kannkor]

On a toon that has "Move To Area" and "Auto Follow Mode" checked, I set a campspot. The toon is set to follow "Me". I move away from the toon; it stays put as expected.

I then uncheck "Move To Area" and "Auto Follow Mode", then call "OgreBotAtom a_StopFollow" followed by "OgreBotAtom a_LetsGo". I would have expected the toon to not move, and be in a state that I could now move it manually without it a) trying to run back to me or b) trying to run back to the campspot. However, it runs right back to me as if it is still in the "follow" state. If I then reissue "OgreBotAtom a_StopFollow", then it stops following me. Its as if either "OgreBotAtom a_LetsGo" somehow reconstituted the "follow" state, or "OgreBotAtom a_StopFollow" was ignored while the toon was in the "campspotted" state.

Not sure if this is a bug or a feature. However, if its a feature, I really would appreciate some wisdom on what I need to do to "release" an individual toon from its "campspotted" and "follow" states simultaneously so it stays where it was when campspotted and I can then move it manually if I desire.

Doing a 'stop follow' simply tells the bot to not engage follow mode, and if following, stop following.

Doing a 'lets go' clears almost all movement flags, so the bot should move/function like normal. This includes following. It is working exactly as designed in your above scenario.

You can do a lets go to clear a campspot, then do a stop follow to prevent following.

 

[mistahmikey]

Doing a 'lets go' clears almost all movement flags, so the bot should move/function like normal. This includes following. It is working exactly as designed in your above scenario.

What is confusing about this is that I turned off following (unchecked "Auto Follow Mode") before issuing "lets go". Why then would it start to follow me when I disabled that feature?

 

[bjcasey]

He already told you. Lets Go removes almost all movement flags. You are telling it to stop following and then start following.

 

[mistahmikey]

You are telling it to stop following and then start following.

Au contraire, mon ami. I disagree entirely that is what I have "told" it. I have "told" Ogre that I no longer wish to follow. Anyone who understands english would reasonably conclude that disabling an option called "Auto Follow Mode", followed by calling "OgreBot aStopFollow", would result in the toon no longer following when a subsequent "Lets Go" is issued. That ain't happening. There is no way that, under those circumstances, the observed behavior is the least bit obvious.

It's not a big deal, though. If that's the way Kannkor wants it to work, so be it. I just wanted to make sure it was not a bug. But thanks for reinforcing what Kannkor already told me - that second iteration made things perfectly clear to a dummy like me

 

[Kannkor]

Au contraire, mon ami. I disagree entirely that is what I have "told" it. I have "told" Ogre that I no longer wish to follow. Anyone who understands english would reasonably conclude that disabling an option called "Auto Follow Mode", followed by calling "OgreBot aStopFollow", would result in the toon no longer following when a subsequent "Lets Go" is issued. That ain't happening. There is no way that, under those circumstances, the observed behavior is the least bit obvious.

It's not a big deal, though. If that's the way Kannkor wants it to work, so be it. I just wanted to make sure it was not a bug. But thanks for reinforcing what Kannkor already told me - that second iteration made things perfectly clear to a dummy like me

My apologies, I actually missed where you said you UNCHECKED Auto Follow mode.
Are you using OgreFollow? Because that changes the answer.

If you are NOT using OgreFollow (OFol), then the toon should not have followed you.

However, OgreFollow does not check AutoFollow Mode (which... Maybe it should.. but.. it's been this long...) so in that case, the unchecking AutoFollow Mode did nothing.

 

[Kannkor]

My apologies, I actually missed where you said you UNCHECKED Auto Follow mode.
Are you using OgreFollow? Because that changes the answer.

If you are NOT using OgreFollow (OFol), then the toon should not have followed you.

However, OgreFollow does not check AutoFollow Mode (which... Maybe it should.. but.. it's been this long...) so in that case, the unchecking AutoFollow Mode did nothing.

To add if you are using OFol, if you want a toon to stop following, you can just tell them to follow themselves, or for that toon to follow "off". They both do the same thing.

 

[mistahmikey]

I am not using Ogre Follow - just have following set up solely using the Ogre gui (Setup Tab and Settings Tab). I have set my tank as the "followee".

 

[Kannkor]

I am not using Ogre Follow - just have following set up solely using the Ogre gui (Setup Tab and Settings Tab). I have set my tank as the "followee".

Interesting, I will see if I can reproduce, via following, turning off auto follow mode, doing a stopfollow, then a lets go, and see what happens.

 

[Kannkor]

On a toon that has "Move To Area" and "Auto Follow Mode" checked, I set a campspot. The toon is set to follow "Me". I move away from the toon; it stays put as expected.

I then uncheck "Move To Area" and "Auto Follow Mode", then call "OgreBotAtom a_StopFollow" followed by "OgreBotAtom a_LetsGo". I would have expected the toon to not move, and be in a state that I could now move it manually without it a) trying to run back to me or b) trying to run back to the campspot. However, it runs right back to me as if it is still in the "follow" state. If I then reissue "OgreBotAtom a_StopFollow", then it stops following me. Its as if either "OgreBotAtom a_LetsGo" somehow reconstituted the "follow" state, or "OgreBotAtom a_StopFollow" was ignored while the toon was in the "campspotted" state.

Not sure if this is a bug or a feature. However, if its a feature, I really would appreciate some wisdom on what I need to do to "release" an individual toon from its "campspotted" and "follow" states simultaneously so it stays where it was when campspotted and I can then move it manually if I desire.

I just did the following:
Logged into the game with my tank and a dirge.
Dirge already had the tank as the follow. I grouped them, and immediately the dirge started following.
I hit campspot on MCP, dirge stopped.
I unchecked move to area and auto follow mode.
Copy/pasted the two commands: a_StopFollow and a_LetsGo from here and put them into the console.
The toon did not move.

Now, I'm guessing when you said:

I then uncheck "Move To Area" and "Auto Follow Mode"

You probably meant you modified the UI, which does nothing at all, other than modify the UI. (I won't list the code here, because if other people try it, it's just going to cause issues).

Assuming this is your problem, you can do the following to manage these options instead.

if ${UIElement[${OBUI_checkbox_settings_moveinfront}].Checked}
    UIElement[${OBUI_checkbox_settings_moveinfront}]:LeftClick

Left clicking will force the event that actually updates Ogrebot, rather than just modifying the UI. (Generally speaking, Ogrebot does not READ from the UI, other than when data is being inputted. This is because reading from the UI is terribly slow vs storing it under the hood).

If this happens to not be your case, then I'll need more step by step on how to reproduce it.