Okay so Ive seen in alot of cases where people want to set then immediately want to use a getter for that same variable. This lead me to thinking why not have the option to pass along that variable, using a var in a branch/if typically you want the option to pass it into the branch so its just a more natural flow.
The above example is passing along TempAirSpeed to AirSpeed, so we can still access and modify the variable separately with a getter but only when we really need a new getter.
I dont see any major optimization issues as the variable is readily available anyway, this doesnt need to be a get and set for something like AirSpeed, its pretty universal. As in this example:
Heres some typical blueprint usage, a dodging function. You can see most of the flow gets broken at the setters, that I can pass along these from the setter in alot of cases and it matches the execution flow.
Thank you for your feedback. I have investigated the database and can confirm that a developer has added a request for this feature. Please let us know if there is anything else that would help with improving workflow.
Beware, I am a total noob and can only manage to utilize blueprint from trial and error and looking at other completed blueprints.
Heres my problem. I have tried to duplicate this out of pure nostalgia from dodging in UT, but the nodes after the “Event Do Dodge” confuse me. How do I even create the input “DoubleTap Left” and “DoubleTap Right” to connect to “Dodge Dir”? How could they even correspond to my left movement key and my right movement key?