objectcreate
A representation of the aegis shield generator deployed using an advanced adaptive construction engine.
A part of a representation of the avatar portion of ObjectCreateMessage packet data.
This partition of the data stream contains information used to represent how the player's avatar is presented.
A part of a representation of the avatar portion of ObjectCreateMessage packet data.
This partition of the data stream contains information used to represent how the player's avatar is presented.
This appearance coincides with the data available from the CharacterCreateRequestMessage packet.
the unique name of the avatar; minimum of two characters
the empire to which the avatar belongs
whether the avatar is Male or Female
the avatar's face and hair; by row and column on the character creation screen, the high nibble is the row and the low nibble is the column
the avatar's voice selection
PlanetSideEmpire
CharacterGender
A representation of the capture flag portion of ObjectCreateDetailedMessage packet data.
A representation of the capture flag portion of ObjectCreateDetailedMessage packet data.
This creates what is known as a lattice logic unit, or LLU.
It is originally spawned in the base object called the lattice link socket during certain base captures.
Players can not directly interact with the capture flag.
Whenever an applicable player is nearby, that client will rapidly fire off ItemUseMessage packets to the server.
The capture flag will be picked-up by the player and stored in a special slot that is not part of their inventory.
A special dropping keybind has been prepared to relinquish the capture flag back to the game world.
the empire whose players may interact with this capture flag
na
na
na
na
A part of a representation of the avatar portion of ObjectCreateDetailedMessage packet data.
A part of a representation of the avatar portion of ObjectCreateDetailedMessage packet data.
the player's cardinal appearance settings
common field data
-bops - this vehicle belongs to the Black Ops, regardless of the faction field;
activates the green camo and adjusts permissions
-destroyed - flagged when using a model that is not the standard player in some stance
-jammered - the player has been caught in an EMP blast recently;
creates a jammered sound effect that follows the player around and can be heard by others
-player_guid - does nothing?
the type of exo-suit the avatar will be depicted in; for Black OPs, the agile exo-suit and the reinforced exo-suit are replaced with the Black OPs exo-suits
ExoSuitType
DetailedCharacterData
CharacterData
A part of a representation of the avatar portion of ObjectCreateDetailedMessage packet data.
A part of a representation of the avatar portion of ObjectCreateDetailedMessage packet data.
the name of the outfit to which this player belongs;
if the option is selected, allies with see either "[outfit_name]" or "{No Outfit}" under the player's name
the decal seen on the player's exo-suit (and beret and cap) associated with the player's outfit; if there is a variable color for that decal, the faction-appropriate one is selected
a "pitch" angle
a "yaw" angle that represents the angle of the avatar's upper body with respect to its forward-facing direction; this number is normally 0 for forward facing; the range is limited between approximately 61 degrees of center turned to left or right
this player is looking for a squad; all allies will see the phrase "[Looking for Squad]" under the player's name
if the player has a grenade Primed;
should be GrenadeStateState.None if nothing special
avatar is cloaked by virtue of an Infiltration Suit
animation pose for both charging modules and BFR imprinting
player's model is changed into a faction-color ball of energy, as if on a zip line
http://www.planetside-universe.com/p-outfit-decals-31.htm
RibbonBars
GrenadeState
ExoSuitType
DetailedCharacterData
CharacterData
A part of a representation of the avatar portion of ObjectCreateDetailedMessage packet data.
This is a shared partition of the data used to represent how the player's avatar is presented.
A part of a representation of the avatar portion of ObjectCreateDetailedMessage packet data.
This is a shared partition of the data used to represent how the player's avatar is presented.
It is utilized by both 0x17 ObjectCreateMessage CharacterData and 0x18 ObjectCreateDetailedMessage DetailedCharacterData.
This can be considered the data that goes into creating the player's model.
Only a few changes would occur depending on which packet would deal with the data.
One example is facingYawUpper which, when depicting avatars, can be set to represent non-trivial turning angles.
When depicting other players, it is limited to a small range of angles in the direction of that model's forward-facing.
Another example is the outfit information: not usually represented for avatars; but, always represented for other players.
One way the player's model can be changed dramatically involves being depicted as "released."
In this form, their body appears as a backpack (or pumpkin or pastry) that can be looted for the equipment carried while alive.
Companion data will describe how the player is represented while he is "dead," usually a requirement for being "released."
Without that requirement here, it is possible to depicte the player as a "living backpack."
The said equipment is also defined elsewhere.
Another dramatic change replaces the player's model with a ball of plasma that masks the player while riding zip lines.
Exploration:
How do I crouch?
the four merit commendation ribbon medals
DetailedCharacterData
CharacterData
A representation of a portion of an avatar's ObjectCreateDetailedMessage packet data.
This information outlines most of the specifics required to depict some other player's character.
A representation of a portion of an avatar's ObjectCreateDetailedMessage packet data.
This information outlines most of the specifics required to depict some other player's character.
Someone else decides how that character is behaving and the server tells each client how to depict that behavior.
For that reason, the character is mostly for presentation purposes, rather than really being fleshed-out.
Of the inventory for this character, only the initial five weapon slots are defined.
In the "backend of the client," the character produced by this data is no different
from the kind of character that could be declared a given player's avatar.
In terms of equipment and complicated features common to an avatar character, however,
any user would find this character ill-equipped.
the amount of health the player has, as a percentage of a filled bar;
the bar has 85 states, with 3 points for each state;
when 0% (less than 3 of 255), the player will collapse into a death pose on the ground;
while is_backpack == true, health will always report as 0;
while is_seated == true, health will (try to) report as 100
the amount of armor the player has, as a percentage of a filled bar;
the bar has 85 states, with 3 points for each state;
while is_seated == true, armor will always report as 0
the level of upgrade to apply to the player's base uniform
the player's command rank as a number from 0 to 5; cosmetic armor associated with the command rank will be applied automatically
the effects of implants that can be seen on a player's character; the number of entries equates to the number of effects applied; the maximu number of effects is three
optional decorative features that are added to the player's head model by console/chat commands; they become available at battle rank 24, but here they require the third uniform upgrade (rank 25); these flags do not exist if they are not applicable
this player character should be depicted as a corpse; corpses are either coffins (defunct), backpacks (normal), or a pastry (festive); the alternate model bit should be flipped
this player character is seated in a vehicle or mounted to some other object; alternate format for data parsing applies
Cosmetics
DetailedCharacterData
Data that is common to a number of game object serializations.
Data that is common to a number of game object serializations.
faction affinity
NEUTRAL when not required to be any specific value
usually indicates black ops affiliation
usually indicates variance in model from default (e.g., vehicle is destroyed, player has released, etc.); when set on a tool, that tool will be rendered nonfunctional instead (though it can still be equipped)
na
na; optional data whose reading is triggered in unknown conditions; flag a weapon as "jammered"
na;
for weapons, works like alternate
na; a field used by a second encoding format for this data
na; previously considered to flag as "jammered"
usually indicates another active game object that placed/leverages/[action]s this object
Data that is common to a number of game object serializations, plus position information
Data that is common to a number of game object serializations, plus position information
the location, orientation, and potential velocity of the object
the common fields
DroppedItemData
The base type for the representation of any data used to produce objects from ObjectCreateMessage packet data.
The base type for the representation of any data used to produce objects from ObjectCreateMessage packet data.
There is no reason to instantiate this class as-is.
Children of this class are expected to be able to translate through scodec operations into packet data.
The object data is uncoupled from the object class as multiple classes use the same format for their data.
For example, both the Suppressor and the Gauss will use a "weapon data" format.
For example, both 9mm bullets and energy cells will use an "ammunition data" format.
The different cosmetics that a player can apply to their character model's head.
The player gets the ability to apply these minor modifications at battle rank twenty-four, just one rank before the third uniform upgrade.
The different cosmetics that a player can apply to their character model's head.
The player gets the ability to apply these minor modifications at battle rank twenty-four, just one rank before the third uniform upgrade.
These flags are only valid if the player has:
for DetailedCharacterData, achieved at least battle rank twenty-four (battle experience points greater than 2286230),
or, for CharacterData, achieved at least battle rank twenty-five (acquired their third uniform upgrade).
CharacterData, as suggested, will not display these options until one battle rank after they would have become available.
a value that indicates certain cosmetic features by bitwise math
PersonalStyleFeatures
UniformStyle
na
na
na
na
na
na
an
na
A representation of the charred husk of a destroyed vehicle.
This is a hand-crafted Codec and was not based on something found on Gemini Live.
A representation of the charred husk of a destroyed vehicle.
This is a hand-crafted Codec and was not based on something found on Gemini Live.
where and how the object is oriented;
pos.vel existing is fine
A representation of the ammunition portion of ObjectCreateDetailedMessage packet data.
A representation of the ammunition portion of ObjectCreateDetailedMessage packet data.
This data will help construct a "box" of that type of ammunition when standalone.
It can also be constructed directly inside a weapon as its magazine.
The maximum amount of ammunition that can be stored in a single box is 65535 units.
Regardless of the interface, however, the number will never be fully visible.
Only the first three digits or the first four digits may be represented.
na
the number of rounds available
DetailedWeaponData
A representation of a portion of an avatar's ObjectCreateDetailedMessage packet data.
A representation of a portion of an avatar's ObjectCreateDetailedMessage packet data.
the avatar's battle experience points, which determines his Battle Rank
the avatar's command experience points, which determines his Command Rank
for x / y of hitpoints, this is the avatar's y value;
range is 0-65535
for x / y of hitpoints, this is the avatar's x value;
range is 0-65535
for x / y of armor points, this is the avatar's x value;
range is 0-65535;
the avatar's y armor points is tied to their exo-suit type
for x / y of stamina points, this is the avatar's y value;
range is 0-65535
for x / y of stamina points, this is the avatar's x value;
range is 0-65535
unk; this field exists only when the player is wearing a mechanized assault exo-suit
the List of certifications
CertificationType
CharacterData
A representation of a portion of an avatar's ObjectCreateDetailedMessage packet data.
A representation of a portion of an avatar's ObjectCreateDetailedMessage packet data.
the List of implant slots currently possessed by this avatar
the list of first time events performed by this avatar; the size field is a 32-bit number; the first entry may be padded
the List of tutorials completed by this avatar;
the size field is a 32-bit number;
the first entry may be padded
optional decorative features that are added to the player's head model by console/chat commands; they become available at battle rank 24; these flags do not exist if they are not applicable
Cosmetics
CharacterData
A representation of a portion of an avatar's ObjectCreateDetailedMessage packet data.
This densely-packed information outlines most of the specifics required to depict a character as an avatar.
A representation of a portion of an avatar's ObjectCreateDetailedMessage packet data.
This densely-packed information outlines most of the specifics required to depict a character as an avatar.
It goes into depth about information related to the given character in-game career that is not revealed to other players.
To be specific, it passes more thorough data about the character that the client can display to the owner of the client.
For example, health is a full number, rather than a percentage, as is the case with CharacterData.
Just as prominent is the list of first time events and the list of completed tutorials.
Additionally, a full inventory, as opposed to the initial five weapon slots.
CharacterData
A representation of the command uplink device.
DetailedACEData - data.faction is faction affinity, data.unk1 is true
DetailedBoomerTriggerData - data.faction can be NEUTRAL, data.unk1 is true
DetailedTelepadData - data.faction can be NEUTRAL, data.jammered is the router's GUID
A representation of the inventory portion of ObjectCreateDetailedMessage packet data that contains the items in the avatar's locker space.
Although these items are technically always loaded and registered with globally unique identifiers for the current zone,
the actual container for them, in grid format, can only be accessed by interacting with locker objects in the game world.
A representation of the inventory portion of ObjectCreateDetailedMessage packet data that contains the items in the avatar's locker space.
Although these items are technically always loaded and registered with globally unique identifiers for the current zone,
the actual container for them, in grid format, can only be accessed by interacting with locker objects in the game world.
Items are generally added and removed in the same way as with any other opened inventory.
Unlike other inventories, however, locker space is personal to an avatar and can not be accessed by other players.
na
the items in this inventory
A representation of an avatar player for the ObjectCreateDetailedMessage packet.
A representation of an avatar player for the ObjectCreateDetailedMessage packet.
As an avatar, the character created by this data is expected to be controllable by the client that gets sent this data.
Divisions exist to make the data more manageable.
The first division defines the player's location within the game coordinate system.
The second division defines features of the avatar
that are shared by both the ObjectCreateDetailedMessage version of a controlled player character (this)
and the ObjectCreateMessage version of a player character.
The third field expands on the nature of the character and this avatar's campaign.
Expansive information about previous interactions, the contents of their inventory, and equipment permissions are included.
The presence or absence of position data as the first division creates a cascading effect
causing all of fields in the other two divisions to gain offsets.
These offsets exist in the form of String and List padding.
the optional position of the character in the world environment
common fields regarding the the character's appearance
the class-specific data that discusses the character
the player's full or partial (holsters-only) inventory
the holster that is depicted as exposed, or "drawn"
used to seed the state of the optional position fields
DrawnSlot
InventoryData
DetailedCharacterData
CharacterAppearanceData
A representation of the REK portion of ObjectCreateDetailedMessage packet data.
A representation of the REK portion of ObjectCreateDetailedMessage packet data.
This data will help construct the "tool" called a Remote Electronics Kit.
Of note is the first portion of the data which resembles the DetailedWeaponData format.
na
na
A representation of a class of weapons that can be created using ObjectCreateDetailedMessage packet data.
A representation of a class of weapons that can be created using ObjectCreateDetailedMessage packet data.
This data will help construct a "loaded weapon" such as a Suppressor or a Gauss.
The data for the weapons nests information for the default (current) type and number of ammunition in its magazine.
This ammunition data essentially is the weapon's magazines as numbered slots.
An "expected" number of ammunition slot data can be passed into the function.
field common to multiple game objects
the current fire mode
data regarding the currently loaded ammunition type(s) and quantity(ies)
WeaponData
DetailedAmmoBoxData
Provide information that positions a given object on the ground in the game world.
Provide information that positions a given object on the ground in the game world.
a subclass of ConstructorData that indicates what type the object is
where and how the object is oriented
the object on the ground
A representation of a droppod that is dropped from the HART shuttle and ferries the player into battle.
A representation of a droppod that is dropped from the HART shuttle and ferries the player into battle.
Droppods are also used when a player has activated Instant Action.
When the server first spawns the droppod, it will be placed at the world ceiling - 1024.0f.
It is placed under control via another packet that sends it hurtling to the ground.
Upon hitting the ground, it opens up, releasing the player, and despawns.
Although the droppod is not technically a vehicle, it is treated as such by the game.
A spawned and unoccupied droppod can be entered and exited, as expected (the seat is 0).
There is no entry animation.
The exit animation is the droppod flowering open as usual.
Even in its spread open state, the droppod can be re-entered, though it will remain spread open.
The player's character will disappear once "inside."
Upon exiting again, the droppod will snap shut and spread open.
Exploration:
When basic.player_guid is defined, the droppod will not be at the world ceiling anymore and its boosters will be activate.
Does this basic.player_guid actually represent the player who is in the pod?
data common to objects
the amount of health the object has, as a percentage of a filled bar
whether the boosters are ignited
DroppodLaunchResponseMessage
DroppodLaunchRequestMessage
A representation of a number of simplified objects that the user can hold in their hands, including:
the advanced construction engine (ace),
the field deployable unit (advanced_ace),
the boomer trigger apparatus,
the remote telepad (not deployed),
the flail laser pointer (flail_targeting_laser),
and the command uplink device (command_detonater).
A representation of a number of simplified objects that the user can hold in their hands, including:
the advanced construction engine (ace),
the field deployable unit (advanced_ace),
the boomer trigger apparatus,
the remote telepad (not deployed),
the flail laser pointer (flail_targeting_laser),
and the command uplink device (command_detonater).
fields that are common to this game object
CommonFieldData object is employed
An entry in the List of valid implant slots in DetailedCharacterData.
An entry in the List of valid implant slots in DetailedCharacterData.
the type of implant
the amount of time necessary until this implant is ready to be activated; technically, this is unconfirmed
whether this implant is turned on; technically, this is unconfirmed
ImplantType
An intermediate class for the primary fields of ObjectCreate*Message with an implicit parent-child relationship.
Any object that is contained in a "slot" of another object will use InternalSlot to hold the anchoring data.
An intermediate class for the primary fields of ObjectCreate*Message with an implicit parent-child relationship.
Any object that is contained in a "slot" of another object will use InternalSlot to hold the anchoring data.
This prior object will clarify the identity of the "parent" object that owns the given parentSlot.
As the name implies, this should never have to be used in the representation of a non-child object.
Try to avoid exposing this class in the process of implementing common object code.
Provide overrode constructors that mask the creation of InternalSlot where applicable.
the code for the type of object being constructed
the GUID this object will be assigned
a parent-defined slot identifier that explains where the child is to be attached to the parent
the data used as representation of the object to be constructed
ObjectClass.selectDataDetailedCodec
ObjectClass.selectDataCodec
A representation of the inventory portion of ObjectCreate*Message packet data for avatars.
The inventory is a temperamental thing.
A representation of the inventory portion of ObjectCreate*Message packet data for avatars.
The inventory is a temperamental thing.
Items placed into the inventory must follow their proper encoding schematics to the letter.
The slot number refers to the position occupied by the item.
In icon format, all-encompassing slots are absolute positions; and, grid-distributed icons use the upper-left corner.
No values are allowed to be misplaced and no unexpected regions of data can be discovered.
If there is even a minor failure, the remainder of the inventory will fail to translate.
Inventories are usually prefaced with a single bit value not accounted for here to switch them "on."
the items in the inventory
InventoryItemData
This class currently is unused but is based on the SmallTurretData Codec class.
A representation for a game object that can contain items.
For whatever reason, these "lockers" are typically placed at the origin coordinates.
A representation for a game object that can contain items.
For whatever reason, these "lockers" are typically placed at the origin coordinates.
the items inside this locker
The parent information of a created object.
In normal packet data order, there are two ways the parent object can be assigned.
The parent information of a created object.
In normal packet data order, there are two ways the parent object can be assigned.
The first is an implicit association between a parent object and a child object that are both created at the same time.
A player character object, for example, is initialized in the same breath as the objects in his inventory are initialized.
A weapon object is constructed with an ammunition object already included within itself.
The second is an explicit association between the child and the parent where the parent exists before the child is created.
When a new inventory object is produced, it is usually assigned to some other existing object's inventory.
That is the relationship to the role of "parent" that this object defines.
As such, only its current unique identifier needs to be provided.
If the parent can not be found, the child object is not created.
A third form of parent object to child object association involves the impromptu assignment of an existing child to an existing parent.
Since no objects are being created, that is unrelated to ObjectCreateMessage.
Refer to ObjectAttachMessage, MountVehicleMsg, and MountVehicleCargoMsg.
When associated, the child object is "attached" to the parent object at a specific location called a "slot."
"Slots" are internal to the object and are (typically) invisible to the player.
Any game object can possess any number of "slots" that serve specific purposes.
Player objects have equipment holsters and grid inventory capacity.
Weapon objects have magazine feed positions.
Vehicle objects have seating for players and trunk inventory capacity.
the GUID of the parent object
a parent-defined slot identifier that explains where the child is to be attached to the parent; encoded as the length field of a Pascal string
A representation of the player-mountable large field turrets deployed using an advanced adaptive construction engine.
Field turrets are divided into the turret base, the mounted turret weapon, and the turret's ammunition.
A representation of the player-mountable large field turrets deployed using an advanced adaptive construction engine.
Field turrets are divided into the turret base, the mounted turret weapon, and the turret's ammunition.
The ammunition is always the same regardless of which faction owns the turret.
Turret bases and turret weapons are generally paired by the faction.
If the turret has no health, it is rendered as destroyed.
If the turret has no internal weapon, it is safest rendered as destroyed.
Trying to fire a turret with no internal weapon will soft-lock the PlanetSide client.
data common to objects spawned by the (advanced) adaptive construction engine
the amount of health the object has, as a percentage of a filled bar
data regarding the mountable weapon
A representation of the high altitude rapid transport (HART) shuttle that ferries the player into battle.
A representation of the high altitude rapid transport (HART) shuttle that ferries the player into battle.
This Codec is different depending on whether the shuttle is the child of a parent or independent.
Three HART shuttles dock with the three HART buildings in the three sanctuaries for short periods on a timed schedule.
When one is landed, players may board the shuttle using designated hallways in the lobbies of the HART building.
After the shuttle leaves the sanctuary, it transports those players up into orbit above the continents.
The shuttle docks again, this time with space stations that orbit the planet.
It allows infantry to use droppods to land on the continents by pinpointing locations on that continent's tactical map.
The previous explanation is smoke and mirrors nonsense.
Lore-wise, the separation of Auraxis during the Bending rendered it impossible for the shuttle to visit all of the continents.
The orbital stations - even if they multiplied one per planet - don't really exist.
(They almost existed but all assets for them were cut from the game.)
The HART shuttle also isn't a traditional vehicle.
It isn't even tangible.
The game just treats it like a vehicle for the purpose of allowing players to access the controllable droppod system.
When accessible to the player, the shuttle has an access point called a "trunk."
Trying to access it yields the brief message "OSMustBeDockedToMount."
empire the object is affiliated with
optional; where and how the object is oriented
OrbitalShuttleTimeMsg
DroppodLaunchResponseMessage
DroppodLaunchRequestMessage
A specific location and heading in game world coordinates and game world measurements.
A specific location and heading in game world coordinates and game world measurements.
the xyz-coordinate location in the world
the ijk-orientation around the object's center
optional movement data (that occurs upon placement)
A representation of another player's character for the ObjectCreateMessage packet.
A representation of another player's character for the ObjectCreateMessage packet.
In general, this packet is used to describe other players.
Divisions exist to make the data more manageable.
The first division defines the player's location within the game coordinate system.
The second division defines features of the character
that are shared by both the ObjectCreateDetailedMessage version of a controlled player character
and the ObjectCreateMessage version of a player character (this).
The third field provides further information on the appearance of the player character, albeit condensed.
The fourth field involves the player's Equipment holsters and their inventory.
The hand that the player has exposed is last.
One of the most compact forms of a player character description is transcribed using this information.
The presence or absence of position data as the first division creates a cascading effect
causing all of fields in the other two divisions to gain offset values.
These offsets exist in the form of String and List padding.
the optional position of the character in the world environment
common fields regarding the the character's appearance
the class-specific data that explains about the character
the player's inventory; typically, only the tools and weapons in the equipment holster slots
the holster that is initially drawn
used by the Codec to seed the state of the optional pos field
CharacterData
InventoryData
DrawnSlot
na
na
na
na; defaults to 0
DetailedREKData
Enumerate the player-displayed merit commendation awards granted for excellence (or tenacity) in combat.
Enumerate the player-displayed merit commendation awards granted for excellence (or tenacity) in combat. These are the medals players wish to brandish on their left pauldron.
the "top" configurable merit ribbon
the central configurable merit ribbon
the lower configurable merit ribbon
the top-most term of service merit ribbon
DisplayedAwardMessage
MeritCommendation
A representation of the Spitfire-based small turrets deployed using an adaptive construction engine.
The turret may contain substructure defining a weapon is a turret weapon contained within the turret itself.
A representation of the Spitfire-based small turrets deployed using an adaptive construction engine.
The turret may contain substructure defining a weapon is a turret weapon contained within the turret itself.
Furthermore, that turret-like weapon is loaded with turret-like ammunition.
In other words, this outer turret can be considered a weapons platform for the inner turret weapon.
If the turret has no health, it is rendered as destroyed.
If the turret has no internal weapon, it is safest rendered as destroyed.
data common to objects spawned by the (advanced) adaptive construction engine
the amount of health the object has, as a percentage of a filled bar
data regarding the mounted weapon
A basic Trait connecting all of the vehicle data formats (excepting Normal/None).
Apply this trait to a class that needs to have its size in bits calculated.
A representation of the tactical resonance area protection unit deployed using an advanced adaptive construction engine.
A representation of the tactical resonance area protection unit deployed using an advanced adaptive construction engine. Three metal beams, erect and tangled, block passage to enemies and their vehicles.
data common to objects spawned by the (advanced) adaptive construction engine
the amount of health the object has, as a percentage of a filled bar
A representation of simple objects that are spawned by the adaptive construction engine.
A representation of simple objects that are spawned by the adaptive construction engine.
data common to game objects
na
na
A representation of a projectile that the server must intentionally convey to players other than the shooter.
A representation of a projectile that the server must intentionally convey to players other than the shooter.
na
na; data specific to the type of projectile(?)
na
The format of vehicle data for the type of vehicles that are considered "utility." The vehicles in this category are two: the advanced nanite transport, and the advanced mobile station.
The format of vehicle data for the type of vehicles that are considered "utility." The vehicles in this category are two: the advanced nanite transport, and the advanced mobile station.
na
A common format variant of vehicle data.
A common format variant of vehicle data. This category includes all flying vehicles and the ancient cavern vehicles.
na
A representation of a generic vehicle.
A representation of a generic vehicle.
where the vehicle is and how it is oriented in the game world
common vehicle field data:
-bops - this vehicle belongs to the Black Ops, regardless of the faction field;
activates the green camo and adjusts permissions
-destroyed - this vehicle has ben destroyed;
health should be less than 3/255, or 0%
-jammered - vehicles will not be jammered by setting this field
-player_guid the vehicle's (official) owner;
a living player in the game world on the same continent as the vehicle who may mount the driver seat
na
the amount of health the vehicle has, as a percentage of a filled bar (255)
na
do not display entry points for the seats
a representation for the current mobility state; various vehicles also use this field to indicate "deployment," e.g., the advanced mobile spawn
na
na
if a vehicle (that can cloak) is cloaked
extra information necessary to implement special-type vehicles;
see vehicle_type
the seats, mounted weapons, and utilities (such as terminals) that are currently included; will also include trunk contents; the driver is the only valid seat entry (more will cause the access permissions to act up)
a modifier for parsing the vehicle data format differently;
see vehicle_format_data;
defaults to Normal
A representation of a class of weapons that can be created using ObjectCreateMessage packet data.
A representation of a class of weapons that can be created using ObjectCreateMessage packet data.
This data will help construct a "loaded weapon" such as a Suppressor or a Gauss.
Common uses include items deposited on the ground and items in another player's visible inventory (holsters).
The data for the weapons nests information for the default (current) type of ammunition and number of ammunitions in its magazine(s).
This ammunition data essentially is the weapon's magazines as numbered slots.
An "expected" number of ammunition slot data can be passed into the class for the purposes of validating input.
na; commonly 8
the current mode of weapon's fire; zero-indexed
data regarding the currently loaded ammunition type(s)
AmmoBoxData
A representation of ammunition that can be created using ObjectCreateMessage packet data.
A representation of ammunition that can be created using ObjectCreateMessage packet data.
This data will help construct a "box" of that type of ammunition when standalone.
It can also be constructed directly inside a weapon as its magazine.
This ammunition object ompletely ignores the capacity field, normal to detailed ammunition objects.
Creating an object of this type directly and picking it up or observing it (in a weapon) will reveals single round.
DetailedAmmoBoxData
Values for the equipment holster slot whose contained ("held") equipment can be drawn.
Values for the equipment holster slot whose contained ("held") equipment can be drawn.
The values for these Enums match the slot number by index for Infantry weapons.
None is not a kludge.
While any "not a holster" number can be used to indicate "no weapon drawn," seven is the value PlanetSide is looking for.
Using five or six delays the first weapon draw while the client corrects its internal state.
Values for the implant effects on a character model.
Values for the implant effects on a character model.
The effects are not additive and this value is not a bitmask.
RegenEffects is a reverse-flagged item - inactive when the corresponding bit is set.
For that reason, every other effect is n + 1, while NoEffects is 1 and RegenEffects is 0.
Mask the use of InternalSlot using a fake class called an InventoryItemData.
Mask the use of InternalSlot using a fake class called a MountItem.
A reference between all object class codes and the name of the object they represent.
A reference between all object class codes and the name of the object they represent.
Object class types are defined by an 11-bit (0xB) value.
Values for the different specific customizations available as cosmetics.
NoHelmet removes the current helmet on the reinforced exo-suit and the agile exo-suit;
other cosmetics require no_helmet to be true before they can be seen;
NoHelmet does not override Beret or BrimmedCap
Beret player dons a beret
Sunglasses player dons sunglasses
Earpiece player dons an earpiece on the left
BrimmedCap player dons a cap;
the cap overrides the beret, if both are selected
A compilation of the common *Data objects that would be used for stock game objects.
A compilation of the common *Data objects that would be used for stock game objects.
Each function is named after the ObjectClass name (internal name) it creates.
No Prefab assumes empire allegiance or initial health.
This file is more useful for reference, rather than application.
A representation of an object that can be interacted with when using a variety of terminals.
A representation of an object that can be interacted with when using a variety of terminals. This object is generally invisible.
Values for the four different color designs that impact a player's uniform.
Values for the four different color designs that impact a player's uniform. Exo-suits get minor graphical updates at the following battle rank levels: seven (1), fourteen (2), and twenty-five (4). The values 3 and 5 also exist and are visually descriptive to the third upgrade.
An Enumeration of the various formats that known structures that the stream of bits for VehicleData can assume.
A representation of the aegis shield generator deployed using an advanced adaptive construction engine.
data common to objects spawned by the (advanced) adaptive construction engine
the amount of health the object has, as a percentage of a filled bar