How to access PlayerController component

NodeCanvas Forums Custom Nodes & Tasks How to access PlayerController component

This topic contains 2 replies, has 2 voices, and was last updated by  virtualcucumber 5 months, 1 week ago.

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #13936

    virtualcucumber
    Participant

    Im switching over my actions from an old FSM I made to NodeCanvas. So this might not be the best practice for this asset but would still like to know how to do this and if theres a better way let me know.

    So i have an FSM with a couple action states, only using “Default” state for the time being to test:
    https://i.gyazo.com/df5d27a043c9c5e5d4040c7bd6fa1c67.png

    The Default state will have more than one action and I would like to access the PlayerController class on the player like so (Move action class):

    Would this be the best way about doing so, dragging over the player class into the serialized Player field every time I need an action to access the PlayerController class? Preferably would like to cache the player class once and be able to access if I had to along all the states.

    #13940

    Gavalakis
    Keymaster

    Hey,

    There are definetely easier ways to go about this 🙂
    Probably the best way (and an important feature of NodeCanvas Custom Tasks), would be to derive your Move ActionTask from the generic version of ActionTask<T>, instead of just ActionTask, with T being the Component which the task requires to work with, thus in this case:
    public class Move : ActionTask<PlayerController>.

    Doing so, and on initialization of the task, the PlayerController component will be fetched (with GetComponent) from the “agent” (The FSMOwner gameobject) and automatically be cached.

    To access the PlayerController within the task’s code, you will then need to use the .agent property, which will already be of type PlayerController since you derived the generic ActionTask version. Thus your custom task code will end up like this in the end:

    Another benefit of deriving from the generic version of ActionTask as you will see, is that within the inspector of your Move ActionTask, you will (optionally) be able to override (with the checkbox) the “target” agent, or in other words, the PlayerController in this case which you want the task to use. Most of the times though, leaving the option to the default “Use Self” is what you will need.

    Thus, deriving from the generic version of ActionTasks where T would be the the Component type you want the action to use, allows you to “not care” about caching or assigning and just use the component directly without worries, through the .agent property.

    Please let me know if the above helps and if that is indeed what your question was about.
    Thanks!

    #13941

    virtualcucumber
    Participant

    Please let me know if the above helps and if that is indeed what your question was about.
    Thanks!

    Thanks for the fast response and help! That’s exactly what I needed.

Viewing 3 posts - 1 through 3 (of 3 total)

You must be logged in to reply to this topic.