Event Setup rules and guides

Event Rules

The following checks must be passed during testing for an event to be considered in 'acceptable' conditions:

1. Dying in the event must remove you from the event instantly and nullify any potential score gain, as well as remove any event-provided items and/or effects.
2. Quitting in the event must do the same as above.
3. It should be impossible to enter the event with potion effects, they must be either:
   • Cleared upon entering
   • Prevented from entering if they possess potion effects
4. Entering the event should function perfectly each time
5. Exiting the event should function perfectly each time
6. Completing the event, different from exiting, should follow the event's context and assign scores only if:
   • The player's score is higher than their record
   • The event uses the assign-only-if-score-greater rule
7. Alt accounts are not permitted to gain score on the same ground as main accounts, when dealing with an alt, one of the following methods must be used
   • The alt is unable to enter (preferred)
   • The alt is unable to gain score
   • The alt's score is given to the main

The follwing are optional checks which apply on a per-event basis:

1. Entering the event with items in your inventory shouldn't be possible, it should be checked. An event may never remove items from, or clear, your inventory, unless the items were given by the event

If the event uses an 'arena' which is built either by generation or example-pasting the following should be checked:

1. The arena generates correctly,
2. All triggers within the arena function correctly
3. Any and all spawned or moved entities be placed correclty
4. Any and all spawned or moved entities function correclty
5. If the arena features a 'tick list' then the following must be check:
   • Each tick-list-entry is ticked correctly and at correct intervals
   • Any exception thrown by an entry does not stop the tick's execution
   • Any exception thrown by an entry is logged in console

Events must block the following commands: tpa, tpask, tpahere, tpaskhere, tpdeny, tpcancel, tpaccept, home, echest, ec, enderchest, wb, workbench, kit, back, workb, warp

Project rules

Any project for a Succession Event must - from here on out - follow the following naming principle: {MONTH}-{YEAR}-{NAME}Event An example would be April-2022-PrankEvent