Command Library
Introduction
Part of the Command System of the UX Foundation and UX Compelete assets
A scriptable object referencing a set of commands and details about how those commands are to be parsed. A command is simply a GameEvent that can be looked up by name. Your game can then listen for these game events to know when a command was ran. This system also handles paramiterizezd commands, that is the arguments following a command can be parsed and sent along with it.
This might be parsed to invoke a Game Event named emote and pass a string argument of wave you can then handle this event and use the argument to determin what animation to play in the case of an emote system.
Fields and Attributes
useCaseSinsativeCommandNames
When parsing should case be respected
commandStartString
What token should be watched for when searching strings for commands
developerCommands
Commands identified as "developer" commands, when parsing you can filter out developers commands. When used these are usually commands that are not restrectied from player access but require an additional layer of effort on the player's part similar to "console commands" in games like Elder Scrolls or Fallout.
If you want to prevent players from running a command, do not innclude it in your released game. If you do include a command in your game your players will find a way to run it.
userCommands
Commands identified as "user" commands, when parsing. User commands are always searched when parsing and are in constrast to "developer" commands.