Parkour

The parkour module (parkour) has two kinds of run: courses you build in game, and three endless modes drawn block by block around the runner. Times and scores are stored in ExyliaLib's database, so lobbies that share it share their leaderboards.

Playing

Runs start only inside the lobby, and not while another module holds the player (a fight, for example). Starting a run while running replaces it. Runners get three hotbar items: back to checkpoint, restart and leave.

Courses

A course has a start, ordered checkpoints and a finish. Stepping on the start starts or restarts a run; checkpoints must be reached in order and a run goes back to the last one reached when the runner touches a kill block, falls course-fall-depth blocks under their lowest point, or uses the back item. The finish records the time and the split at each checkpoint, and a better time replaces the old best.

Building one

All in game, from /lobbyadmin → Parkour (the editor), or by command, standing where each point goes:

/lobbyadmin parkour create <id>
/lobbyadmin parkour setstart <course>
/lobbyadmin parkour addcheckpoint <course>
/lobbyadmin parkour setfinish <course>
/lobbyadmin parkour addkill <course>
/lobbyadmin parkour medals <course> <gold> <silver> <bronze>
/lobbyadmin parkour delete <course>

A course can be run once start and finish are both placed. Ids are lower case letters, digits and dashes. addkill adds the block you look at to the course's kill blocks. Courses live in modules/parkour/courses.yml:

Endless, sprint and daily

The path is generated ahead of the runner and cleared behind them, in a box you define:

/lobbyadmin parkour endlessarea <name>

Make a selection of the box first, then stand where the run starts (the run starts where you stand). start is the block under the runner's feet and heading is where the path sets off: 0 east (+x), 1 south (+z), 2 west (-x), 3 north (-z). Keep the box empty air. A runner gets one area at random; daily always uses the first. Endless parkour needs PacketEvents.

Daily paths are seeded from the date and a secret in modules/parkour/daily-secret.txt. Lobbies that should share the daily path share that file; keep it private.

Landings are confirmed by the server. A landing it cannot confirm (off the path, out of reach or too fast) ends the run unscored.

Endless tuning

Screen

In ExyliaLib's SCREEN menu style, the parkour list opens as a full screen (screens/parkour.html), with its words in lang/<code>/screens/parkour.yml. It reads the same data and actions as the chest menu, which Bedrock and older clients still get. Put your own rules in screens/custom.css; /exylialib screens check lists anything wrong.

Anti-cheat

Under anti-cheat, all on by default:

A run ended this way records nothing and tells the runner why.

Leaderboards and holograms

A board is a course id or a mode, optionally with a period: tower, tower-weekly, endless-monthly, daily. Periods are all, monthly, weekly and daily. Courses rank fastest first; modes rank highest first.

Place a leaderboard hologram with /lobbyadmin parkour board <board> (a wizard asks you to confirm the spot). The spots are kept in boards.

Other settings

Placeholders are on the placeholders page.