Getting started

OneJumpAllJump (short: ojaj) is a server-side plugin with one job: when a player jumps, every player on the server is launched with them. This page gets it running in under five minutes.

Requirements

• Paper or Purpur: the plugin listens on Paper's PlayerJumpEvent, which Spigot does not provide. Forks that ship the Paper API work too.
• Minecraft 26.1+: the published builds target 26.1, 26.1.1 and 26.1.2 (the plugin is compiled against the Paper 1.21 API, api-version: 1.21).
• Java 21+: the jar is compiled for Java 21; any JVM that runs your server already qualifies.
• Server-side only: players need no mod, resource pack or client change.

Install from Modrinth

1. Grab the latest .jar from the Modrinth project page (or install it straight through the Modrinth App / your panel's Modrinth integration).
2. Drop the jar into your server's plugins/ folder.
3. Restart the server. A default plugins/OneJumpAllJump/config.yml is generated on first enable.

Your first global jump

Join the server, walk into an allowed world (see the gotcha below) and jump. Everyone online gets launched, and you should see the default title, action bar and chat broadcast:

CopyGLOBAL JUMP                     <- title
<dash> made everybody jump!         <- action bar
dash triggered a global jump!    <- broadcast

As an operator you can check your personal counter and control the plugin at any time:

Copy/onejump stats    # tracked jumps for you
/onejump toggle   # flip the plugin on/off
/onejump reload   # re-read config.yml

The world-name gotcha

The default config ships with worlds.mode: whitelist and the list [world, spawn]. If your world is named anything else, nothing will happen. Either add your world to worlds.list or switch to mode: blacklist, then run /onejump reload.

Where to next

• Gameplay & mechanics: the exact trigger chain, launch math and safeguards.
• Configuration: every key in config.yml documented.
• Commands & permissions: everything /onejump can do.

OneJumpAllJump is in alpha. Expect balancing tweaks, edge-case bugs and the occasional config change between versions; feedback and testing are very welcome on GitHub Issues.