Listening to Input events in node canvas

[kevynm]

I want to implement a behaviour where I have to wait for an input touch event and then my character moves to that input touch event position. However, while the character is moving, when I press and execute a touch input event again it stops the moving character and moves to the new target position. How do you do that?

I have implemented the a conditional node that listens to the touch event and moves the character, but my problem is I don’t know how to do the latter.

[Gavalakis]

Hello,

One way would be using a Parallel node and a Repeater like the image I’ve attached for you, but probably the best way, would be if you handle all this self-contained in a custom action task, which both checks for touch in it’s execute as well as in it’s update. If in it’s Execute there is no touch, it simply returns failure (with EndAction(false) ). Here is an example:

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27

public class Example : ActionTask<NavMeshAgent>{   protected override void OnExecute(){ if (Input.touches == 0){ EndAction(false); return; }   agent.SetDestination(Input.GetTouch(0).position); }   protected override void OnUpdate(){ if (Input.touches > 0){ agent.SetDestination(Input.GetTouch(0).position); }   if (!agent.hasPath || agent.remainingDistance == 0){ EndAction(true); } } }

Let me know if this works for you.

Thanks

Join us on Discord: https://discord.gg/97q2Rjh

Attachments:

You must be logged in to view attached files.

[kevynm]

It didn’t work for me. But, I found a solution that worked well. Thanks for the suggestion it gave me a better understanding of how the behaviour tree works.

Attachments:

You must be logged in to view attached files.

[kevynm]

I have an additional question though, what’s the proper way of subscribing and unsubscribing to events in Conditional Nodes? Is this right? Is it the same in Action nodes?

Attachments:

You must be logged in to view attached files.

[Gavalakis]

Hey,

Glad you found a proper solution for your case and thanks for sharing.

Regarding subscribing/unsubscribing for conditions, right now, OnEnable and OnDisable is only called for conditions in FSMs, since in Behaviour Trees, there is no clear moment where a condition is enabled or disabled apart from when the BT starts and ends.
So the best candicate for subscribing, would be OnInit, and you can use OnDisable for unsubscribing for within an FSM context.
I will make OnEnable and OnDisable be called for BTs when they start and finish as well, in the next version. Added this in the TODO list.

So prety much what you have is correct right now.

As far as actions, you can once again use OnInit for subscribing and OnStop for unsubscribing if that is something needed.
Again, I will improve the API to be more consistent between both action/condition tasks and amongst all graphs regarding enabling/disablng in the next version.

Thanks!

Join us on Discord: https://discord.gg/97q2Rjh

[Author]

Posts