Skip to main content

Events

An event is a server activity controlled by EventDirector.

Events can represent many different server scenarios, such as:

  • seasonal activities;
  • tournaments;
  • staff-hosted games;
  • timed challenges;
  • reward-based tasks;
  • community celebrations;
  • special server moments.

What an event usually contains​

A typical event configuration can include:

  • a name;
  • whether it is enabled or disabled;
  • start and stop behavior;
  • messages shown to players;
  • participant rules;
  • conditions;
  • rewards;
  • commands;
  • optional GUI settings.

Enabled and disabled events​

Keep unfinished events disabled until they are tested.

A good workflow is:

  1. create the event;
  2. keep it disabled;
  3. test it with staff;
  4. create a backup;
  5. enable it when ready.

Live event safety​

Avoid editing a live event unless you know exactly what will happen.

Before changing a live event:

  • create a backup;
  • warn staff;
  • check the console;
  • test changes on a private server if possible.

Naming events​

Use clear event IDs and names.

Good examples:

summer_tournament
christmas_rewards
parkour_weekend
staff_hide_and_seek

Avoid names with spaces, strange symbols, or unclear abbreviations.

Event testing checklist​

Before using an event with real players, verify that:

  • it loads without console errors;
  • messages display correctly;
  • permissions are correct;
  • rewards are not duplicated;
  • conditions work as expected;
  • staff can stop or disable it if needed.