Skip to main content
Plane Deploy wiki

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.

Squad and Admin Tools

Door and Spawn Editor Admin Workflow

Use the hotbar editor to create and maintain door zones and spawn groups without fighting the legacy pos1 and pos2 flow.

The newer hotbar editor exists so admins can maintain door zones and spawn groups without relying entirely on the older pos1 and pos2 workflow.

Opening the editor

Use:

TEXT
/pd editor

When the editor opens, it:

  • backs up the player's inventory
  • swaps in hotbar tools
  • shows marker guidance for placement tools
  • runs particle and marker visuals while the session is active

Door mode hotbar

The current door-mode tools are:

  • slot 1: exit editor
  • slot 2: switch mode
  • slot 3: set corner A
  • slot 4: set corner B
  • slot 5: set door ID and spawn group through chat
  • slot 6: save or update door
  • slot 7: select door by looking into a zone
  • slot 8: delete selected door
  • slot 9: toggle visualization

The door tools use an in-air marker block so you can place the cuboid cleanly instead of guessing where the click landed.

Spawn mode hotbar

The current spawn-mode tools are:

  • slot 1: exit editor
  • slot 2: switch mode
  • slot 3: set spawn group through chat
  • slot 4: add spawn at the marker
  • slot 5: teleport or cycle through spawns
  • slot 6: move selected spawn to your location
  • slot 7: delete selected spawn
  • slot 8: set spawn weight through chat
  • slot 9: toggle visualization

This mode also shows spawn particles, selected-spawn highlighting, and a small yaw-direction arrow for the selected spawn.

Why this editor is safer than blind YAML edits

The editor helps with the hardest parts of deployment geography:

  • seeing door volume in world space
  • placing spawns in air instead of on a random clicked block
  • cycling through all saved spawns in a group
  • checking yaw direction visually
  • updating data.yml and runtime caches together

When to still use legacy commands

The older /pd pos1, /pd pos2, /pd createzone, /pd creategroup, and /pd addspawn flow is still useful when:

  • you are doing quick one-off fixes
  • you are scripting an admin workflow around commands
  • you need a very small edit and do not want to enter editor mode

For general maintenance, the hotbar editor is the better daily tool.

Safe editing habits

When using the editor:

  1. confirm the correct world first
  2. switch to the correct mode before typing IDs in chat
  3. cycle through saved spawns after edits
  4. verify selected spawn yaw before you leave
  5. do one manual /pd deploy test after large route changes

That short loop catches most bad edits before players ever see them.