"Following" Macros

[Bomberman1988]

I've tried to make my Animal Companion to follow my ally several times but it never worked, is it some kind of bug?

What does the "Toggle Following" macro do exactly? It doesn't have any visual effect so I've no idea of what's supposed to do

[Saibot393]

So, how it is supossed to work is like this: Let's say you want token A to follow token B, you select token A, hover over token B (or target token B) and either use the macro or press the toggle follow key (default F). To stop following, hover over an empty region of the map/untarget token A and use the toggle macro or key again.
You can activate the Rideable setting "Message popups" to gain more information (started/stopped following) (you might need to activate the Foundry setting "Scrolling Status text" first).
Should that not work there might be a bug. In this case, are there any erros in the console (F12) upon using the macro/key?

[Bomberman1988]

Understood, but the Following macro isn't working, at least not with Animal Companions. As I said I can't make my AC follow my ally. It says it's following, but it doesn't move. The Console seems to be ok. Could you check it out?

…

On Mon, Apr 29, 2024 at 1:14 PM Saibot393 ***@***.***> wrote: So, how it is supossed to work is like this: Let's say you want token A to follow token B, you select token A, hover over token B (or target token B) and either use the macro or press the toggle follow key (default F). To stop following, hover over an empty region of the map/untarget token A and use the toggle macro or key again. You can activate the Rideable setting "Message popups" to gain more information (started/stopped following) (you might need to activate the Foundry setting "Scrolling Status text" first). Should that not work there might be a bug. In this case, are there any erros in the console (F12) upon using the macro/key? — Reply to this email directly, view it on GitHub <#71 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AYXZHNNYV5X7ZJ3IDO3KJFDY7ZWWXAVCNFSM6AAAAABG6T5KSWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBTGE2DGMBTGI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Saibot393]

Which following algorithm are you using (Rideable setting "Following algorithm")? If it is set to "Simple path history", installing routinglib and using that instead may fix it. It could also be a module incompatibility, have you tried running Find the culprit!?
I will look into any possible bug as soon as possible.

[Saibot393]

Is this still happening with the newest versions of rideable?