| Name | clientizen event |
| Event Lines | clientizen event |
| Triggers | When the server receives an event from a clientizen client, this requires config option 'Clientizen.process events' in the Depenizen config. |
| Example |
on clientizen event id:my_id:
- narrate "Hello! you sent an event with the id '<context.id>'"
|
| Has Player | Always. - this adds switches 'flagged:<flag name>' + 'permission:<node>', in addition to the '<player>' link. |
| Switches | id:<id> to only process the event if the identifier received from the client matches the specified matcher. |
| Contexts | <context.id> returns an ElementTag of the event identifier received from the client.
<context.data> returns the context MapTag received from the client as a map of keys to ElementTags.
<context.(key)> returns the ElementTag value of the input key in the context map, if available.
|
| Group | Clientizen |
| Warning(s) | The client can send any data it wants, so should very carefully verify any input before using it. |
| Source | https://github.com/DenizenScript/Depenizen/blob/master/src/main/java/com/denizenscript/depenizen/bukkit/clientizen/ClientizenEventScriptEvent.java#L15 |