Transport routes

Transport routes carry a player along an authored curve on a configured custom boss mount. Routes live in plugins/EliteMobs/transport_routes/. The mount is an ordinary enabled YAML definition in custombosses/, where you configure its entity type, model, disguise, and powers.

Create a route in game

The editor commands are player-only and require elitemobs.transport.admin.

1. Stand at the departure point and run /em transport create guild_flight.
2. Fly to each subsequent waypoint and run /em transport add.
3. Inspect the particle preview. The faint curve includes your proposed next point.
4. Face the direction riders should face on arrival and run /em transport save.
5. Check the saved mount and route settings, then run /em transport start guild_flight to try the route.

New editor routes reference the bundled transport_cannon_seat.yml custom boss. Change transportEntity to another enabled custom-boss filename when needed.

Command	Action
/em transport create <id>	Start a new draft at your position
/em transport edit <id>	Edit an enabled existing route
/em transport add	Append your position
/em transport move <number>	Move a waypoint to your position, numbered from 1
/em transport remove	Remove the last waypoint
/em transport undo	Undo the last geometry edit, up to 32 retained edits
/em transport status	Show the current draft
/em transport ride	Try the draft without saving
/em transport save	Save geometry and arrival yaw
/em transport cancel	Discard the draft
/em transport list	List loaded routes
/em transport reload	Reload route files; active flights retain their original route
/em transport start <id>	Start a saved route
/em transport stop	Cancel your current journey

Route YAML

For guild_flight.yml:

isEnabled: true
name: Guild flight
world: my_dungeon
transportEntity: transport_cannon_seat.yml
speed: 12
acceleration: 8
countdownTicks: 60
arrivalYaw: 90
waypoints:
  - "10,70,10"
  - "20,85,20"
  - "40,70,40"

Use a lowercase route ID of 1-64 letters, digits, underscores, or hyphens. The world must match the player's current authored world. Inside an instance of that dungeon, the authored world is resolved to the player's active instance; do not hardcode generated instance names.

speed and acceleration must be positive finite values. countdownTicks is nonnegative and defaults to 60 ticks. The editor preserves existing presentation and tuning settings when saving geometry.

Stand still during the departure countdown. Changing position cancels departure; looking around without moving does not. This cancellation applies before boarding, not to the mount's movement during a flight.

The retired route fields carrier, customModel, and flightAnimation are rejected. Put appearance and behavior in the referenced custom-boss definition.

Add a travel NPC

Use the TRANSPORT NPC type and list loaded route IDs without .yml:

interactionType: TRANSPORT
transportRoutes:
  - guild_flight

Add these fields to an otherwise valid NPC definition. The menu accepts 1-54 distinct available destinations and checks that the player is still near the NPC before boarding.

Route clearance and interruptions

Map makers own route clearance. The mount follows the authored curve; it does not find a path around obstacles or repair unsafe geometry. Preview and ride the complete route with the intended mount and enough space for both mount and rider.

Transport requires native flying Mind support on the server version. An unavailable mount or rejected boarding attempt stops the journey with an error. Death, disconnect, world or instance changes, a removed mount, or leaving the vehicle also ends travel. Successful arrival places the rider at the final point with arrivalYaw. Interrupted travel removes the mount; it does not promise a return teleport.