History
| Date | Author | Commit Message | ||
|---|---|---|---|---|
|
|
|
2026-09-15 13:59:50 d8c845 | Anonymous | Integrate the moving scan, growth, bridge reuse and explicit placement costs |
|
|
|
2026-09-15 13:23:31 95459a | Anonymous | Clarify the player journey, current growth rules and onward reading |
|
|
|
2026-09-15 12:04:57 f2d2c1 | Anonymous | Align expedition renewal and regular combat growth references |
|
|
|
2026-09-14 19:12:45 b22d9b | Anonymous | Remove text slop: disclaimers, process metadata, restatements and hedge tags; no rule changes (owner readability review, 14 Sep) |
|
|
|
2026-09-10 13:43:50 bcd1e4 | Anonymous | Outcome 53 response 665: reconcile horde-build mechanics |
|
|
|
2026-09-10 13:11:39 3ae784 | Anonymous | Outcome 53: define three finite horde-scale build experiences and adverse R25 check |
|
|
|
2026-09-10 12:49:11 b4cb27 | Anonymous | Clarify the player benefit of closing a horde source before release |
|
|
|
2026-09-10 12:33:03 fbf654 | Anonymous | Align the three build examples with actual equipment and retain crowd-scale payoff targets |
|
|
|
2026-09-10 10:26:54 d729e4 | Anonymous | Record owner choice: expedition upgrades reset on every return home |
|
|
|
2026-09-09 19:06:42 e419c3 | Anonymous | Clarify horde stakes, actionable discovery and expedition growth lifecycle |
|
|
|
2026-09-09 18:44:20 6d3879 | Anonymous | Propose ordinary horde rhythm and three spectacular connected builds |