net.psforever.objects.serverobject.pad
VehicleSpawnControl
Related Docs:
object VehicleSpawnControl
| package pad
net.psforever.objects.serverobject.pad
the VehicleSpawnPad object being governed
The continent the pad recognizes as a place of installation will change as its Owner changes.
The continent the pad recognizes as a place of installation will change as its Owner changes.
Originally, it belongs to a default non-Building object that is owned by a default non-Zone object.
Eventually, it will belong to an active Building object that will belong to an active Zone object.
With respect to GetLogger(String), the active Zone object will be valid shortly after the object is registered,
but will still be separated from being owned by a valid Building object by a few validation checks.
the (current) Zone object
Implement this to add a suffix to the identifying name of the logger.
Implement this to add a suffix to the identifying name of the logger.
a special identifier that distinguishes a logger whose name is built of common features
The first chained action of the vehicle spawning process.
Act as if a variable for the logging agent.
Act as if a variable for the logging agent.
a Logger object
a reminder sent to future customers
A common manner of utilizing the logging agent such that all messages have the same logging level.
A common manner of utilizing the logging agent such that all messages have the same logging level.
The default should be trace-level comments.
No important messages should processed by this agent; only consume general vehicle spawn status.
the message
An
Actorthat handles vehicle spawning orders for aVehicleSpawnPad. The basicVehicleSpawnControlis the root of a simple tree of "spawn control" objects that chain to each other. Each object performs on (or more than one related) actions upon the vehicle order that was submitted.The purpose of the base actor is to serve as the entry point for the spawning process. A spawn pad receives vehicle orders from an attached
Terminalobject. The control object accepts orders, enqueues them, and, whenever prompted by a previous complete order or by an absence of active orders, will select the first available order to be completed. This order will be "tracked" and will be given to the first functional "spawn control" object of the process. If the process is completed, or is ever aborted by any of the subsequent tasks, control will propagate down back to this control object.