FAQ

Through WorldGuard regions you create with /rg. There is no coordinate box in AlphaEvent. You attach a region to an arena with /aevent region <key> <region>: lobby for the waiting area, arena for the play area, and more keys for events that need them (a finish line, a hill, answer areas). A player who leaves the arena region during a live round is eliminated (races and a few events respawn or ignore this instead), and nobody who is not taking part can break or place blocks inside it while a round runs.

For the moment a round needs it, the plugin opens one WorldGuard flag on the arena region and restores the previous value afterwards. See Arena setup → What the plugin does to your regions.

Not directly. WorldEdit is needed because WorldGuard's region API is built on its math and adapter classes. There is no schematic paste or undo anywhere: every block an event changes is remembered in memory (its original block data) and put back after the round.

The arena is missing something the event needs. The message lists each missing item and the command that fixes it, and /aevent check <event> shows the full list any time. In the event menu, right-click an event to run the same check.

/aevent start <event> → Announcing (two seconds, broadcast and title) → Joining (countdown, the join menu opens for everyone, /event join works) → cancelled here if there are fewer than min-players → Waiting (participants are moved to the lobby and protected) → Round starting (everyone is placed on a spawn and held still for the countdown) → Round active (the event's rules run) → Round ending (points awarded, the arena restored) → back to waiting for the next round, or Event ending (final ranking, rewards) → everyone returns to the exit or where they joined from, with their old inventory.

Open-world events skip the lobby and the teleports: players stay where they are and keep their inventory.

They switch to spectator mode with an empty event inventory and, unless spectator.teleport-to-alive-on-elimination is false, are moved to watch a player who is still in. At the end of the event their own inventory and position are restored.

Each round gives placements. Players who tie share one, and the points for that placement come from the points map. At the end the points are added up; ties are broken by the event score (kills, catches, hits, checkpoints). The same order drives the announcement, the placeholders and the rewards.

A lethal hit in a fighting event is cancelled and turned into an elimination or a respawn, so nobody sees a death screen and nobody loses items. Their own inventory is restored when the event ends.

No, and that is intentional for an emergency-only command: it stops the event and wipes the protection and block-snapshot state without replaying the restoration. If you use it mid-round the arena stays as it was. /aevent stop and /aevent nextround restore it.

Yes for config.yml, events/, lang/ and the arenas. A running event keeps the settings it started with for things it already read, such as the round count.

Yes. Set mode: snowball or mode: bow in events/spleef.yml.

Yes. Trivia Run reads its questions from events/trivia.yml, Chat Games its words and trivia from events/chatgames.yml, and every fighting event its kit from kit in its own file.

No. The plugin does not declare Folia support; run it on Paper.