Record observations that survive a patch
A useful observation identifies the save, settings, mods and installed version. Measurements from a modified or older save should remain separate from default-game facts and later versions.
Quick facts
- Documented answer
- A useful observation identifies the save, settings, mods and installed version. Measurements from a modified or older save should remain separate from default-game facts and later versions. ↗
Procedure
Save the initial scenario and record its settings. For each observation, note the action, relevant window values and the interval used. After an update, repeat the same scenario and preserve both results rather than silently replacing the earlier measurement.
Diagnose the result
If results change, compare game version and settings first. If a field was never observed, leave it Unknown. Keep screenshots and notes tied to the specific save so that a future reader can reproduce the comparison.
Common mistake
Combining measurements from different saves into one apparently exact vehicle statistic.
Evidence and version scope
The cited official manual supports the documented interface and mechanics. The procedure above is editorial guidance for inspecting your own save; it is not a claim of a tested speedrun or a guaranteed outcome. Record your installed version, gameplay settings and mods when comparing results. Release-build version: Unknown.
Connected operations
Parent: Guides for every stage of your network ↗
Next action: Guides for every stage of your network ↗
Planning tool: Network Checklist ↗
Version and changes: Update desk ↗
Sources and verification
Facts are attributed to official post-launch documentation. Procedures are editorial inspection advice; they do not claim a tested save or release-build benchmark.
Last checked: 2026-10-02 · Evidence before estimates · Corrections