I have 2 questions regarding the signals available on states

[SamDevelopsCode]

1. Can you have both an _update() and _physics_update() on the same state at the same time?

2. Can you hook into the func _input() or func _unhandled_input on each state that I missed?

[limbonaut]

1. We only have a single update method, the timing of which depends on update_mode property.
2. You can hook _input() which is enabled and disabled as the state gets entered/exited. I don't think we do the same for unhandled_input, but a simple change if needed. EDIT: Toggle unhandled_input processing in HSM #290

[SamDevelopsCode]

1. We only have a single update method, the timing of which depends on update_mode property.

   2. You can hook _input() which is enabled and disabled as the state gets entered/exited. I don't think we do the same for unhandled_input, but a simple change if needed. EDIT: Toggle unhandled_input processing in HSM #290

Thanks for the response! Is there any plans for allowing multiple update methods? Or is there a design decision made around only having one? Just curious, love the addon, would just love more flexibility.

[limbonaut]

Currently, there are some design problems with supporting two updates. The first one is that we support manual updates and it doesn't make sense to have two update functions in such case. It's used, for instance, to update state machine at lower rate (for offscreen/faraway agents). And the second is that it doesn't work well with behavior trees.

[SamDevelopsCode]

Makes sense, much appreciated!

[andynguyen1103]

Hi, I'm fiddling around with using LimboAI mainly for character control. Currently with the support of one update mode like this, and with most implementation of FSM include 2 modes of update at once, how do you suggest we can implement this with MANUAL mode or should I implement the FSM myself?

[Secretmapper]

Is it possible to hook into_input/_unhandled_input on a single file hsm setup @limbonaut ?