This creates a profile for an event. It will need to be enabled before it will take effect.
Example:
/as event open add
Once an event profile is created you can edit it.
This deletes a profile.
Example:
/as event open del
If you only wish to temporarily stop using the profile, disable it instead. But if you intend to never use the profile again then delete it.
This will deactivate the profile until it is enabled.
Example:
/as event open disable
This is a good way to temporarily stop using a profile. To remove a profile permanently, delete it.
A profile must be enabled before it will take effect. Once enabled it will start running according to how it is set.
Example:
/as event open enable
This command will list everything that has been set for the profile.
Example:
/as event open list
This is very useful for troubleshooting events.
This will change the profile's name. You would refer to it by its new name in all future commands.
Example:
/as event open rename daytime
While the name for an event has no effect other than how you need to refer to it in commands, you may want to change a name to make it clearer what the event does. You also might want to change the name to something shorter and easier to type.
These commands set up when and how the event will run.
INTERVAL - Set how often your scripts should run
SCRIPT - Set which scripts should be run
TIME - Set when the scripts are to be run.
Examples:
/as help event set <command>
This command is the core of the event system. It links the event to a script and a time at which to run it. Scripts can be useful if you want to regularly perform certain actions. For example, if you wanted to rehash your server every day at 4 AM you could write a script to rehash. Then you would set up an event to run every day. You could set the time to start at 4AM. Then the script would keep running without further maintenance.