Download

How should a custom 'go to' Behaviour Tree Task work?

Hey guys,

For a custom ‘go to’ style behaviour tree task, should it loop internally and give the movement data (i.e. move with force a, now with force b) until the destination is reached? Seems that the built-in one is called once and the AI can embark on its journey without additional tasks being fired, or that one being looped in the tree (i.e. via a conditional).

Any advice would be great.

Thanks!

Got this under control :slight_smile:

For anyone wondering; if you don’t return the status of a task it becomes ‘latent’ and will tick until you do so. So throw the navigation into a Tick event, and if you’re within x units of the destination return success, otherwise keep ticking!

Hope it helps.