The animation sequence is controlled primarily by the first field and
goes through a strict cycle of boarding, lift shuttle, takeoff, land, lower shuttle.
All HART facilities (amenity <code>obbasemesh</code>) in a given zone are controlled by this packet.
Multiple systems are controlled by a single field during a given animation,
e.g., the boarding gantries are retracted or extended during the same part where the shuttle is raised or lowered.
Certain neutral animation states - <code>State0</code>, <code>State5</code>, and <code>State7</code> - all behave the same way
though denote different points in the sequence.
Animation subsequence states are coordinated by the second field,
though the specific purpose of the subsequence isn't always obvious,
and the field isn't always necessary to achieve the result of the primary sequence.<br>
<br>
The total time of the system is bound between two states:
whether the shuttle has left or whether it is boarding.
When separated ("has left"),
the shuttle will be lifted out of the bay to atop the building and will fly off into the horizon,
remaining despawned until it returns to view, perches atop the building again, and is lowered into the bay.
When boarding,
the shuttle is fixed in the bay and is accepting passengers via one of the boarding hallways.
Upon boarding the shuttle, the time until takeoff ("has left") is displayed to all waiting passengers
in the form of a progress bar.
This progress bar is fixed to a full time of 60 seconds (60000 milliseconds) in the client and
will start at fractions of completion for boarding times under 60 seconds.<br>
<br>
Pairs of globally unique identifiers for the shuttle facility and the shuttle
link the time fields to their function.
All facilities and shuttles in a given zone are paired and enumerated for a single packet.
If the HART facility identifier is missing or incorrect,
the absent facility will continue to undergo correct animation state transition,
but the door timer will not animate correctly and constantly display the time 10:37 and
the door lights will be neither locked closed (red) or openable (green).
If the shuttle identifier is missing or incorrect,
the absent shuttle will continue to undergo partially correct animation state transitions,
cycling between visible and invisible atop the HART facility,
and the aforementioned progress bars visible by shuttle passengers will not display during the boarding phase
if the shuttle is made available for boarding.</p></div><dlclass="paramcmts block"><dtclass="param">model_state</dt><ddclass="cmt"><p>a control code that affects the over-all state of the HART system</p></dd><dtclass="param">unk0</dt><ddclass="cmt"><p>na</p></dd><dtclass="param">arrival_time</dt><ddclass="cmt"><p>the time for the orbital shuttle to return during instances when the shuttle is away;
displayed on a related time near the shuttle boarding entryways;
in milliseconds</p></dd><dtclass="param">boarding_time</dt><ddclass="cmt"><p>the time for the orbital shuttle to depart during instances when the shuttle is boarding;
frequently <code>8000L</code> when not in use;
in milliseconds</p></dd><dtclass="param">other_time</dt><ddclass="cmt"><p>time field used for a variety of things;
in most uses, the amount of time that has passed since the start of the event,
so usually <code>0</code> (at start of event);
with respects to <code>model_state</code> and <code>unk3</code>:
full departure time when <code>5</code>-<code>3</code> (variant of <code>7</code>-<code>3</code>);
occasionally, full departure time when <code>0</code>-<code>0</code>
in milliseconds</p></dd><dtclass="param">pairs</dt><ddclass="cmt"><p>a list of entries that pair
a paired facility pad unique identifier and shuttle unique identifier
displayed on a related time near the shuttle boarding entryways;
in milliseconds</p></dd><dtclass="param">boarding_time</dt><ddclass="cmt"><p>the time for the orbital shuttle to depart during instances when the shuttle is boarding;
frequently <code>8000L</code> when not in use;
in milliseconds</p></dd><dtclass="param">other_time</dt><ddclass="cmt"><p>time field used for a variety of things;
in most uses, the amount of time that has passed since the start of the event,
so usually <code>0</code> (at start of event);
with respects to <code>model_state</code> and <code>unk3</code>:
full departure time when <code>5</code>-<code>3</code> (variant of <code>7</code>-<code>3</code>);
occasionally, full departure time when <code>0</code>-<code>0</code>
in milliseconds</p></dd><dtclass="param">pairs</dt><ddclass="cmt"><p>a list of entries that pair
a paired facility pad unique identifier and shuttle unique identifier
