For functions in this file, we are favoring having more verbose names such as "AddFloatAction" vs simply "Add" in order to keep it easy to find the correct function in blueprints. The base class for all actions. Actions define the outputs from your agents. Action getters are marked non-pure by convention as many of them do non-trivial amounts of work that can cause performance issues when marked pure in blueprints.