Difference between revisions of "EEvent Resource"
From Armagetron
(New page: {{Blueprint|events-resource}} One of the main goals in eEvent is to have the user have full control on customization. An user should be able to have a red message popping up all over ...) |
|||
| Line 19: | Line 19: | ||
<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?> | <?xml version="1.0" encoding="ISO-8859-1" standalone="no"?> | ||
TODO :) | TODO :) | ||
| + | |||
| + | [[Category:Development]] | ||
Latest revision as of 22:35, 22 August 2021
This wiki page has an associated Blueprint on launchpad.
One of the main goals in eEvent is to have the user have full control on customization. An user should be able to have a red message popping up all over his HUD whenever someone turns as well as he should be able to be told when he is the last alive player on his team.
A server should be able to suggest events handlers. A client can fully(and only fully) ignore them and use it's own settings. See [eEvent] for details.
Goals
- Basic scripting
- Logical structures
- if, else if, else
- need more?
- Comparisons: ==, !=, <, >, <=, >=
- Data access(how??)
- Logical structures
- Server and client event handler support
- New event creation support
- Macro support(needed?)
Imaginary example
<?xml version="1.0" encoding="ISO-8859-1" standalone="no"?> TODO :)
