Wiki
Plane Deploy Wiki
Plane insertion, spawn routing, parachute profiles, squads, wind drift, and admin workflows for cinematic round starts.
Getting Started
Start here for first boot, the file split, and the deployment data that actually drives drops.
Deployment Stack
Follow the live player flow from plane state through drop, wind drift, parachute control, and landing.
Squad and Admin Tools
Use squads, the hotbar editor, and the admin command surface to run real drops instead of hand-editing blind.
Operations and Troubleshooting
Troubleshoot live deployments, optional integrations, and the most common reasons a drop feels wrong.
Plane Deploy has three main command surfaces:
/pdfor core plane-deploy admin tasks/squadfor player squad management/parachutefor parachute admin and tuning
/pd command surface
The current admin help includes:
/pd reload
/pd setplane
/pd deploy [doorid|spawnGroup]
/pd state [state]
/pd editor
/pd pos1
/pd pos2
/pd createzone <id> <group>
/pd creategroup <id>
/pd addspawn <group> [weight]
/pd listgroups
/pd listzonesUse /pd deploy when you want to validate a route quickly without waiting for a full live round.
Use /pd state when you are debugging the state machine and need to know whether the player is still IN_PLANE, already DEPLOYING, or fully GROUND.
/squad command surface
The squad command is player-side and currently supports:
/squad
/squad help
/squad create
/squad invite <player>
/squad accept [leader]
/squad decline [leader]
/squad list
/squad leave
/squad disband
/squad kick <player>
/squad leader <player>This command respects the squads.enabled toggle in config.
/parachute command surface
The parachute admin command currently supports:
/parachute give <player> [amount] [style]
/parachute style <player> <style>
/parachute styles
/parachute who <player>
/parachute test [style]
/parachute tune [style]
/parachute reloadThis is the fastest way to validate resource-pack styles, profile IDs, and tuning changes before you run a real drop.
Permissions
The current plugin exposes both legacy and newer alias permissions.
Core deploy permissions
mcwar.planedeploy.admin
mcwar.planedeploy.bypass
planedeploy.adminParachute permissions
imcparachute.admin
parachute.admin
parachute.useparachute.admin currently inherits the older admin node and parachute.use.
The config comment currently notes that parachute.use exists but is not fully enforced in code yet, so treat it as a future-facing node rather than a strong access boundary by itself.
Good live admin tasks
The most common safe admin tasks are:
/pd setplaneafter moving the aircraft staging point/pd deploy <doorId|spawnGroup>after editingdata.yml/pd editorfor route maintenance/parachute stylesafter editing profile content/parachute test <style>after changing custom-model-data values/squad helpwhen checking the player-side flow
Reload expectations
/pd reload and /parachute reload are useful, but do not treat reload as magic.
After major edits to:
- door geometry
- spawn layout
- parachute rig offsets
- plane visual behavior
you should still perform one real test drop and not assume a reload alone proved correctness.