![]() This is done through the parser and so generates the same syntax error message if any parameters are wrongly specified for this event. We were already enforcing event names in the parser. This is only for state_entry so far as an initial test of the approach - appears to work correctly. |
||
---|---|---|
.. | ||
Application | ||
ClientStack | ||
CoreModules | ||
DataSnapshot | ||
Framework | ||
OptionalModules | ||
Physics | ||
RegionCombinerModule | ||
ReplaceableModules | ||
ScriptEngine | ||
UserStatistics |