sots-engine/src/game
alex e7e2bd6f62 ai: the gather order decides fleet names too, and not only ours
Lane BT found it while building the comparison: FtName is an id-attached label
minted by the same pass as the id, and its counter is per player and shared with
the server's fleets. In the original, a run that minted two client fleets named
an unrelated server fleet differently from a run that minted three. So a gather
that visits groups in a different order renames fleets the AI never touched.
2026-09-09 04:13:34 -04:00
..
ai ai: the gather order decides fleet names too, and not only ours 2026-09-09 04:13:34 -04:00
combat B5: the post-battle retreat rules as a pure planner (game/combat) 2026-09-08 11:52:57 -04:00
config m2: manifest/id dictionary hooks + manifest_loader; thiscall support in Hook template; struct sizes pinned (+0x14 word) 2026-09-07 22:41:42 -04:00
data lane D2: hull size + the defence-platform flag; the ship census reproduces 480/480 2026-09-08 12:44:41 -04:00
design lane D2: aggregate hull size in the record's MEMORY slot order, not its wire order 2026-09-08 12:47:14 -04:00
effects b2: OnTechResearched hook + 10 effects-table corrections (float32, xenotech block size, no already-researched guard, sticky mask, AI bonus values) 2026-09-08 00:01:04 -04:00
events lane P: post the research events from ours (count-only), declare ObservedTech 2026-09-08 04:16:22 -04:00
nav lane P2: fleet path planning (game/nav) 2026-09-08 12:43:11 -04:00
sim L5: the interest literals verified live at a boundary, with a control that fails 2026-09-08 17:48:42 -04:00