+0 500 WORDs Experience values of starship crews
+1000 n BYTEs Ion storms: 50 records of 16 bytes each
+0 WORD X
+2 WORD Y
Note that Host sometimes (rarely) generates
storms with negative coordinates.
+4 WORD Radius
+6 WORD Voltage in MeV
0 Non-existent storm
1..49 Class 1 (harmless)
50..99 Class 2 (moderate)
100..149 Class 3 (strong)
150..199 Class 4 (dangerous)
>=200 Class 5 (very dangerous)
Only class 4/5 storms hurt ships.
+8 WORD Heading in degrees: 0=North, 90=East, ...
+10 WORD 0 weakening
1 growing
+12 2 WORDs ? (unused?)
+1800 11 WORDs Build Priority Points
--- Host 3.22.007 and later ---
+1822 11 WORDs Alliances. This field contains information on who a player
has declared an ally:
Bit 0 1=the player set the Feds as his ally
Bit 1 1=the player set the Lizards as his ally
...
Bit 10 1=the player set the Colonies as his ally
Ships of the player won't attack ships of his allies.
--- Host 3.22.027 and later ---
+1844 3 BYTEs unused (?)
+1847 500 WORDs Cheat check flags, for all planets/bases.
Bit 0 1=starbase with this Id has built a ship. Used
to prevent multiple clones at one base.
Bit 1 1=ship with this Id has moved (itself or by being
towed) and is denied chunneling. Used to prevent
"tow-drop chunnels". Note that this flag is also
set for tow pairs when the tower does not move.
There is no Host999 3.22.027 (yet?); it is unknown how it
would handle this array.
--- Host 3.22.039 and later ---
+2847 11 WORDs Level 2 Alliances ("FF allies"). For each player, whom he
has declared a level 2 ally, as a bitfield like above.
If a bit is set here, the corresponding bit at +1822 is
set, too.Ion Storms
An active storm is identified by a non-zero voltage. Storms that have disappeared are still stored but have voltage 0. There may only be as many ion storms as specified in the HConfig file (default: 5), so that normally not all fields could contain real storms.
When a new game is started, there are always some active Ion storms. It may happen that a player gets a message about a storm with 0 MeV. Due to the encoding here, that storm won't appear on the starcharts.
Storm speeds are not stored here, they are computed when they're needed. As of Host 3.22.003, the Ion storm speeds were these: * Storms with more than 250 MeV always move at warp 8 * Storms smaller than 200 ly move at warp 6. * Larger storms move at
Warp 2 (20%)
Warp 3 (48%)
Warp 4 (32%)
Use first matching rule. Older Hosts only use the last two rules.Ion storms that move outside 0 <= X <= 4000 resp. 0 <= Y <= 4000 are deleted the turn after they moved there. Thus, it is possible that a storm with negative coordinates is reported.
New storms are not subject to the usual rules. They can also have other speeds (Warp 5, Warp 7).
PHost
When PHost is being used, this file is only a dummy version. PHost creates it, but sets all fields to zero. Only the alliance data is written: PHost sets a particular alliance bit to one if and only if the player has offered all five PHost alliance levels to his ally. This file is never read by PHost, changing it won't influence the host. Use AUXDATA.HST to affect PHost.
PHost 4.0j and later also uses the Ion Storm field, using the same meaning as THost.
