Fill these fields before the first round
The goal is to preserve enough context to explain a miss. Use the same record for a second shot instead of relying on memory.
- Mission or operation: the exact task context.
- Target reference: landmark, map point, or mission wording used.
- Observation point and map scale: where the measurement came from.
- Range, elevation state, and shell: the inputs used for the round.
- Impact result: short, long, left, right, or target effect observed.
Make one correction visible
After the impact, write the observed error and change one input. If the next round improves, the note becomes evidence for this context; it is not automatically a universal value for every mission.
Record: original input -> observed impact -> one correction -> next result.
Publish only what you can date
When turning a private record into a public guide, include the game build, test date, mission context, and the source or video that supports the surrounding fact. Leave unknown values marked as pending rather than filling gaps with a guess.