# PSF-LoginServer - master - net.psforever.objects.vehicles.control
PSF - LoginServer - master - net.psforever.objects.vehicles.control
Keywords: PSF LoginServer master net.psforever.objects.vehicles.control

PSF-LoginServer - master < Back


# Packages

-  package root
  Definition Classes
    root
-  package net
  Definition Classes
    root
-  package psforever
  Definition Classes
    net
-  package objects
  Definition Classes
    psforever
-  package vehicles
  Definition Classes
    objects
-  package control
  Definition Classes
    vehicles
- AmsControl
- AntControl
- ApcControl
- CargoCarrierControl
- DeployingVehicleControl
- RouterControl
- VehicleControl

p

net.psforever.objects.vehicles

# control

#### package control


Ordering

1. Alphabetic

Visibility

1. Public
2. Protected

### Type Members

1.  class AmsControl extends DeployingVehicleControl

   A vehicle control agency exclusive to the advanced mobile spawn (AMS).

   A vehicle control agency exclusive to the advanced mobile spawn (AMS). When deployed, infantry troops may manifest nearby the vehicle as they switch from being deconstructed (or dead) to being alive.

2.  class AntControl extends DeployingVehicleControl with AntTransferBehavior

   A vehicle control agency exclusive to the advanced nanite transport (ANT).

   A vehicle control agency exclusive to the advanced nanite transport (ANT). When deployed, nanites in the package of nanite transfer units (NTU) are moved around and may be may be acquired from a Warp Gate structure or supplied to a nanite resource silo belonging to a mjaor facility.

3.  class ApcControl extends VehicleControl

   A vehicle control agency exclusive to the armored personnel carrier (APC) ground transport vehicles.

   A vehicle control agency exclusive to the armored personnel carrier (APC) ground transport vehicles. These vehicles include the Juggernaut (`apc_tr`), the Vindicator (`apc_nc`), the and Leviathan (`apc_vs`). A completely faction-neutral transport in the same sytle (`apc`) does exist but is unused. A common characteristic of this type of vehicle is the ability to discharge a defensive wide-area electromagnetic pulse.

4.  class CargoCarrierControl extends VehicleControl with CargoBehavior

   A vehicle control agency exclusive to vehicles that can physically transport other vehicles.

   A vehicle control agency exclusive to vehicles that can physically transport other vehicles. This includes the Galaxy (`dropship`) and the Lodestar.

5.  class DeployingVehicleControl extends VehicleControl with DeploymentBehavior

   A vehicle control agency exclusive to vehicles that can switch out a navigation mode and convert to a sessile mode that affords additional functionality.

   A vehicle control agency exclusive to vehicles that can switch out a navigation mode and convert to a sessile mode that affords additional functionality. This includes only the Switchblade and the Flail. Other vehicles that deploy are handled by specific instances of this control agency.

   See also

     `AmsControl`

     `AntControl`

     `RouterControl`

6.  class RouterControl extends DeployingVehicleControl

   A vehicle control agency exclusive to the router.

   A vehicle control agency exclusive to the router. When deployed, any router telepad that was acquired from this particular router and then constructed into a router telepad somewhere in the world may synchronize with the vehicle to establish a short to medium range infantry teleportation system.

7.  class VehicleControl extends Actor with Check with MountableBehavior with DamageableVehicle with RepairableVehicle with JammableMountedWeapons with ContainableBehavior with AggravatedBehavior with RespondsToZoneEnvironment

   An `Actor` that handles messages being dispatched to a specific `Vehicle`.
   Vehicle-controlling actors have two important behavioral states - responsive and "`Disabled`." The latter is applicable only when the specific vehicle is being deconstructed.

   An `Actor` that handles messages being dispatched to a specific `Vehicle`.
   Vehicle-controlling actors have two important behavioral states - responsive and "`Disabled`." The latter is applicable only when the specific vehicle is being deconstructed. Furthermore, being "ready to delete" is also a behavoral state for the end of life operations of the vehicle.

### Value Members

1.  object ApcControl
2.  object VehicleControl

### Ungrouped