VEHICLE MOVEMENT
Vehicle movement controls are available only while you are actively
controlling a driver or pilot station. They are supplied by that
Vehicle control surface; they are not ordinary global Character commands.
A driver station receives ground movement controls only. A pilot station
receives the ground controls plus AV flight/altitude controls. This keeps
ordinary local commands such as object-specific CLIMB available to ground
drivers and passengers instead of being shadowed by aircraft controls.
Ground movement:
n / ne / e / se / s / sw / w / nw
drive <direction>
drv <direction>
An air-capable AV may use the same bare compass directions while grounded.
Once airborne, bare compass directions use flight movement automatically.
Air movement:
fly <direction>
takeoff
land
climb
descend
The engine/propulsion system must be running before the Vehicle can move.
Movement follows real physical world topology. The Vehicle always uses
real connected Exits; it does not teleport around blocked or missing routes.
Ground movement uses the Room's canonical physical terrain. Ordinary road
travel is physically valid without a duplicate per-Room vehicle flag.
Rough terrain may be physically traversable even when it is a poor match for
the Vehicle; Vehicle suitability and Driving resolution are separate from
basic Room occupation.
TAKEOFF moves an AV from valid ground space into connected airspace.
LAND moves an airborne AV into connected valid ground space.
CLIMB and DESCEND move between connected air-space layers. DESCEND does
not substitute for LAND when the space below is ground-only.
Passengers do not receive driver/pilot movement controls merely because
they are aboard the Vehicle.
Staff/builders:
NeoOrleans surface Rooms use canonical manifest-cell `base_terrain`
as physical ground truth. Do not add a duplicate vehicle terrain value.
`vehicle_ground_allowed` is an exceptional authored override:
True = explicitly permit ground Vehicle occupation
False = explicitly deny ground Vehicle occupation
missing = use canonical physical terrain
`vehicle_air_allowed` remains explicit:
True = valid airspace
missing/non-True = airborne Vehicle occupation denied
A terrain being physically occupiable does not mean it is safe, legal,
suitable for the current Vehicle, or automatically free of a Driving
check.
Ground Vehicle models carry an authored ground-mobility profile. Ordinary
compatible road travel does not require a Driving roll. When canonical
terrain is hazardous for the current Vehicle, movement resolves one
Driving check using the driver's effective weighted Driving Attributes,
Driving Skill, the Vehicle mobility profile, and the terrain challenge.
At the current implementation stage, an unsuccessful hazardous-terrain
Driving check stops the movement attempt. Vehicle damage, bogging,
immobilization, loss of control, speed effects, and damaged-component
consequences belong to later Vehicle damage/component integration and are
not fabricated by the movement command.
Larger AV rear-compartment rappel capability is reserved for the later
capability/equipment implementation and is not part of basic pilot
controls.