andrew208
October 8, 2017, 1:53pm
108
Bought it! Love it! (And recommend it)
The tutorials seem to assume that for every kind of actor that I want to make interactable, I’ll manually hook up all the values to the actor’s Get Data node. Then if later I wanted to change the highlight color throughout my game, I would have to load up every type of interactable actor and manually change the value.
I’m trying to streamline that so I can just hit +Add Component to drop a component into each blueprint actor, and that sets the values in the Get Data node to the component’s default values (using exposed variables so they’re still individually editable per actor, but otherwise all default to a game-wide standard.) Then when I want to make a game-wide change to my default highlight colors, I just edit that one component and all actors are on the new standard (except any that I set to not use the component value).
I created a blueprint actor component , then in the class settings of that component I added the InteractInterface , to get the Get Data node in this actor component instead of directly on the actor. This works great for creating quick drag-and-drop auto-add and auto-setup of the Get Data node with default game-wide values that can adjust all actors from one location. I set it up so I could just click the green button under “Events” and it would drop the EventInteractWithObject node into the Event Graph, it was ideal. But I think the reason it won’t actually work is that other parts of the Interact Kit are looking for an actor, so some of their nodes aren’t expecting / compatible with / able to find an actor component.
I nosed around, trying to find and adjust those nodes so they would accept a component, but I didn’t get far - I don’t really know how deep that rabbit hole goes and I’m not sure if I’m barking up the wrong tree. So I thought I’d ask around here before going on a potentially wild ride.
Thoughts? Ideas?
(I’ve dialed back the ambition of the component; now I’m using it to merely hold some variables. So it doesn’t streamline anything but at least I can have actors all pointing to a central repository of game-wide standard values)
I tried your setup with a component and it didn’t work for me either. After adding the component the actor doesn’t get the Get Data function, that’s probably why.
Here’s how I did it, without using a component.
Make an actor blueprint, add the interact interface to it, promote everything in Get Data to variables, and set their default values. I called this class ObjectWithInteraction. Then, whenever I need a new interactive object, I make a child class of that, change the default values and set the meshes references in the construction script. If I need interaction added to an existing actor I reparent it to ObjectWithInteraction. That may be difficult in some cases but I’m good with it for now. At least I have my text color and outline color held by my base class.