Four statuses#
| Status | Meaning |
|---|---|
| Tested in game | The described behavior was confirmed in the documented scenario |
| Observation | A research finding that needs verification in another context |
| Learning example | New explanatory code without a separate completed game test |
| Reference material | A guide or overview based on listed sources |
Status applies to the specific claims. A new shortened fragment added to a tested walkthrough still needs its own learning-example label.
Data structure versus game effect#
Reading hull/@max = 1800 proves a field and initial value exist in the inspected macro. A patch setting 3600 still needs a game test; XML parsing cannot replace it. A ship needs real slots, flight, equipment and persistence checks. A UI needs clicks, closing and reopening, not only a correct appearance.
Version and conditions#
Record game version, DLC, dependencies, initial state and result readback method. Check new and existing saves separately when relevant. Automated test counts do not prove an entire game scenario, complete API coverage or compatibility with all mods.
Source snapshots#
dist/sources is refreshed during the build. Snapshots support reading, not automatic validation of every statement. Historical notes and unfinished code retain their original evidence status.