Evidence Standards

Know how sure we are

A useful guide should tell you what the evidence proves and what is still uncertain. That means naming the source, explaining the test and being honest about its limits.

Verified mechanic

A verified mechanic is directly documented in the game or repeatedly observed under controlled conditions. It can still change after an update, so the relevant game version and review date remain important.

Controlled test

A controlled test changes one meaningful variable while keeping the rest of the setup as stable as possible. Record squad composition, positions, relevant bonuses, opponent and repeated outcomes.

Community insight

Player experience can reveal patterns and useful questions before formal testing is complete. Label it clearly, look for independent confirmation and avoid presenting a promising pattern as a settled formula.

Research checklist

1. Write the question before running the test.
2. Record the complete starting conditions.
3. Change one variable and repeat the comparison.
4. Save screenshots or battle reports.
5. State limitations and confidence alongside the result.

Confidence labels are not hesitation. They let commanders use strong evidence quickly without disguising uncertainty.

Minimum evidence for numerical claims

• Record date, server age, season and game version where visible.
• Capture the whole screen containing the number and label.
• Separate base attributes from titles, decorations, alliance technology and temporary buffs.
• Repeat combat tests to expose critical-hit and targeting variation.
• Label translated, datamined or community-supplied values until independently confirmed.

Corrections

When a live screen contradicts an article, preserve the evidence, update the recommendation and revise the review date. A documented correction is more useful than defending an outdated answer.