Needs testingLast reviewed / 2026-08-30
Game Basics
What must a new player recognize before using a calculator, event board, or guide?
Current claimWOS101 can reliably route a player by task—Learn, Plan, Events, or Evidence. Exact game-screen labels and the glossary still require dated in-game screenshots before they are treated as verified current terminology.
- Source / version
- WOS101 information architecture and current Start Here curriculum; no complete primary game-screen source set is attached.
- Conditions
- General orientation only. This record does not establish a game mechanic, upgrade value, or event rule.
- Uncertainty
- City/account, world, hero, troop, alliance, and event labels still need current dated screenshots.
- What would confirm it
- A reviewed screenshot set with game version, language, region, and exact screen context.
What this means: Start Here is safe as a route map, but unverified labels should remain visibly provisional.
Open learning route →Needs testingLast reviewed / 2026-08-30
Account Data Status
Which calculator checks confirm the implementation, and which game-data claims still lack current proof?
Current claimTested arithmetic can be correct while its hard-coded cost table, gate, label, or mechanic still needs evidence. Treat implementation status and game-data truth as separate fields.
| Surface | Implementation | Game-data boundary |
|---|
| Hero Gear | Tested cumulative arithmetic | Cost table and gates need testing |
| Chief Gear & Charms | Tested cumulative arithmetic | Material table and exact target names need testing |
| Troop Camp | Tested sum and time behavior | Stage table and Agnes adjustment need testing |
| War Academy | Data shape and tested sample sum | Nodes, costs, gates, and zero-time meaning need testing |
| Bear Ratio | Frozen / not reassessed | Requires separate explicit reopening |
- Source / version
- Current local implementations and WOS101 evidence ledger; several data files are marked 2026-08-18 without a complete primary-source record.
- Conditions
- Each result applies only to the selected target, starting point, inputs, and assumptions displayed by that calculator.
- Uncertainty
- Incomplete source dates, the unresolved Agnes adjustment, exact tier names, gate tables, and zero-value meanings can change interpretation.
- What would confirm it
- Dated in-game screenshots for every table, gate, tier, node, skill, and affected account state.
What this means: Use calculator totals as model outputs within their stated boundary—not as proof that every underlying game value is current.
Choose a calculator →Needs testingLast reviewed / 2026-08-30
Event Mechanics
Which parts of the event surfaces work locally, and which rules still need current game evidence?
Current claimThe operational pages render and respond locally. Rally Sync’s tested formula behavior is distinct from its scenario-specific tactic conditions; map geometry, scoring, timing, roles, and recommendations still need versioned evidence.
| Surface | Working behavior | Evidence boundary |
|---|
| Rally Sync | Formula implementation independently rechecked | Real tactic, lag, and buffer conditions remain scenario-specific |
| Bear Layout | Local planning interactions; estimated march model | Territory legality and radii need testing |
| Foundry / Canyon | 3D rendering, route and assignment interactions | Map facts, scoring, timing, and tactics need testing |
| Sunfire | 3D selection, local calls, and timer interface | Timer, roles, hold rules, and tactics need testing |
- Source / version
- Current local event pages and evidence ledger; no complete event-version record is attached to the map claims.
- Conditions
- The event version, rules, current phase, player roles, selected target, live timer, and alliance plan must match the board being used.
- Uncertainty
- Local geometry and recommendations are not independently confirmed game truth, while Rally Sync tactic conditions remain scenario-specific.
- What would confirm it
- Current in-game maps, rules, scoring, timing, role definitions, and repeatable scenario evidence.
What this means: Use the boards to prepare and coordinate, then verify the live event state before issuing the call.
Open Event Command →Needs testingLast reviewed / 2026-08-30
Bear Trap Experiment
When are two recorded Bear rallies comparable enough to support a useful conclusion?
Current claimThe implemented averaging logic works for accepted positive-value runs. The experiment method remains incomplete until rally or troop count, buffs, participant context, and repeatability are captured consistently.
- Source / version
- Current Bear Trap Experiment implementation and tested valid-row behavior; no complete reproducible experiment protocol yet.
- Conditions
- Formation ratios, rally or troop count, participants, troop tiers, heroes, buffs, context, and the control variable must be named.
- Uncertainty
- A higher average may reflect changed conditions rather than the formation or hero being tested.
- What would confirm it
- Repeated comparable runs with the same conditions, explicit control, and enough observations to review spread and exceptions.
What this means: The experiment records evidence; it does not automatically turn correlation into a recommendation.
Open Bear experiment →Needs testingLast reviewed / 2026-08-30
War Academy Research
What does a War Academy result prove, and what must be verified before spending?
Current claimThe current data shape and a tested T12 sample sum are internally consistent. This does not confirm every node, cost, prerequisite, FC gate, or the meaning of a recorded zero-time value.
- Source / version
- Current War Academy dataset marked 2026-08-18 and tested local samples; no dated primary-source ledger for every node.
- Conditions
- Tree, current state, target, prerequisite path, buffs, and War Academy FC level must match the planned account.
- Uncertainty
- A zero time may mean missing data rather than instant research. Every hard-coded cost and gate still needs proof.
- What would confirm it
- Dated node screenshots showing prerequisites, cost, time, power, SvS value, and unlock conditions.
What this means: Read the output as a planning model and verify the target nodes in game before committing resources.
Open War Academy →Needs testingLast reviewed / 2026-08-30
Battle Tactics
When can a general Opening, Hold, Break Hold, or Reset framework guide an event call?
Current claimThe four interface modes and their ordered calls work locally. The recommendations are a command framework—not confirmed rules for every event, opponent, phase, or alliance.
- Source / version
- Current local Battle Tactics framework; no complete scenario and source record exists for each recommendation.
- Conditions
- Event rules, current objective state, caller, arrival window, stop condition, opponent response, and reserve state must be known.
- Uncertainty
- A call that works in one event or phase can fail when scoring, ownership, timing, or reinforcement rules differ.
- What would confirm it
- Versioned event rules plus scenario results, failure conditions, and after-action review for each recommendation.
What this means: Read the event rules first, then use the framework to make one repeatable call.
Open Battle Tactics →