Append the builder for a server object to the list of builders known to this ZoneMap
.
Append the builder for a server object to the list of builders known to this ZoneMap
.
the unique id that will be assigned to this entity
the logic that initializes the emitted entity
The guid of the building this object should belong to, if specified
The guid of the door this object (typically a lock) should be linked to, if specified
The guid of the terminal this object (typically a spawn pad) should be linked to, if specified
the current number of builders
The list of all server object builder wrappers that have been assigned to this ZoneMap
.
The list of all server object builder wrappers that have been assigned to this ZoneMap
.
the List
of all ServerObjectBuilders
known to this ZoneMap
The fixed instantiation and relation of a series of server objects.
Asides from a
List
of server objects to be built, the operation between any server objects and the connected functionality emerging from more complex data structures is codified by this object. In the former case, allTerminal
server objects for aZone
are to be defined herein. In the latter case, the arrangement of server objects into groups called facilities is also to be defined herein. Much like aBasicDefinition
to an object,ZoneMap
should not maintain mutable information for the companionZone
. Use it as a blueprint.The "training zones" are the best example of the difference between a
ZoneMap
and aZone.
("Course" will be used as an unofficial location and layout descriptor.)tzdrtr
is the Terran Republic driving course.tzdrvs
is the Vanu Sovereignty driving course. While each course can have different objects and object states, i.e., aZone
, both of these courses utilize the same basic server object layout because they are built from the same blueprint, i.e., aZoneMap
.ServerObjectBuilder
LoadMapMessage