* modifications to ProximityUnit and related classes to internalize the effect control for the terminal, removing the flywheel functiuonality from WSA
* proximity operations for medical terminals (the one in the Anguta lobby, specifically) is functional; some entities besides Player now keep track of the continent they possess, a necessary compromise for proximity ops
* repair rearm silos (Anguta courtyard East) demonstrate operational behavior when lattice benefits are active
* proximity terminals may now juggle multiple targets that move in and out of range and change validity over time
* previous rebase; preparing for special location + offset calculations for utilities
* working location-based proximity repair terminals for the lodestar, utilizing new fields in the vehicle definition, new configuration method in the utilities, and new calculations for Vector3 entities; some comments and tests
* separated ProximityTarget; updated existing terminals; restored defaults; preparing to fix tests
* tests involving the proximity unit workflow
* dismantling a portion of the proximity terminal machinery that is no longer necessary and only poses risk to the system; removing temporary code used to quickly test vehicle silo repairs
* functions for certifcation ui updates (that don't work)
* initialization of combat engineering deployables ui on load and certification change
* representation classes for ACE and FDU; ability to pull ACE and FDU from equipment terminals
* ammo change functionality and fire mode change functionality for ConstructionItems refactored from Tool operations and supported properly (switch between deployable options)
* zone-specific structure for keeping track of deployables; abaility to dismiss deployables from the map screen (previous functionality); local client creation of explosive-type deployables
* refactored MannedTurret into FacilityTurret and lesser traits to be used in the deployable spitfires and the OMFT's; all ACE deployables are available for placement; partial management of the construction items after the deployable is placed; boomers create boomer triggers
* Avatar-specific storage for deployables and for updating UI elements
* refactored quite a bit of code in WSA for the benefit of deployable management; refinements to deployable creation; server messages about deployable quantities; corrected the FDU encoding pattern; lots of work dedicated just to synchronizing BoomerTrigger objects
* added RemoverActor for deployables and redistributed deconstruction functionality away from WSA to new DeployableRemover; added events to facilitate activities not inheritable with this model
* refactored and distributed Deployables classes; copious amounts of testing and document-writing
* boomers now explode from trigger; support for deployables being destroyed by weapon discharge, including individual health, soure identification, and damage model; shuffled deployable classes to build different hierarchy
* sensor_shield was skipped by accident
* identified stray object in Hanish, Ishundar, and added Irkalla, Ishundar's capture console; fixed issue with Warp command and 'Irkalla'; modified building amenity setup and setup testing in Zone; players load and die properly when seated in an omft; reserve ammunition in omft properly registered
* added local service channel, capture consoles, fixed tests as much as posible
* fixed LocalService tests by booting the ServiceManager; added avatar and local tests
* a simple attempt to refactor Actor messages in a way that is acceptable to Travis CI
* making the explosive deployables vanish upon explosion; sensor health bars are now supported
Vehicles can now be pulled from assigned and initialized terminals. The vehicle's chosen spawn pad controls (or paces) all aspects of the spawning process. Support Actors ensure that a fully-realized Vehicle will be unloaded and unregistered if left alone, either right after spawning on the pad or after an extended period of time. The latter half of the procedure used for spawning vehicles is a temporary workaround until future analysis and functionality of the server vehicle override packet is incorporated.
Weapons:
Weapons will now construct their own default magazines thanks to a switch from Ammo.Value to AmmoBoxDefinition in the ToolDefinition.
GenericObjectActionMessage :
The only thing this packet does, at the moment, is obscure the player when he is being promoted into the owner of a vehicle.
