What we can say with confidence
Horde is likely to be the site’s most replayable strategy topic because the right answer changes with enemy faction, squad composition, unlocks and appetite for risk. A responsible guide explains the decision loop first and adds exact reward efficiency only after repeated live runs. The line this guide will not cross is equally important: if a value, drop, location, unlock threshold or balance conclusion is not supported by the current evidence, it is described as unknown or provisional rather than filled in from the first game.
That matters especially during launch week, when search results can mix official information, preview builds and copied speculation. The Last verified date and evidence badges at the top are part of the answer, not decoration.
Official facts versus hands-on evidence
Official-confirmed information comes from the publisher’s site or first-party storefronts. Hands-on tested means a previewer or developer-guided session visibly demonstrated the behavior before release. Neither label means the live game can never change: patches can alter balance and a preview build can differ from release.
When the page discusses a recommendation, read it as a decision framework. A recommendation becomes stronger only when the live build supports it across more than one encounter or difficulty. That is why this site avoids unsupported precision and records sources below the article.
Why Horde needs its own strategy
For Horde Mode Guide, a short campaign encounter is not enough evidence. Horde asks whether a setup remains stable across repeated waves, changing threats and the decision to keep risking accumulated rewards. Consistency, recovery and resource economy matter more the longer a run continues.
A launch-quality Horde guide should record the enemy faction, round, difficulty, team makeup and reason a run ended. That evidence makes build comparisons useful instead of reducing the mode to a generic “highest damage wins” list.
Patch #2 (September 17, 2026): Horde rewards that are now official
The September 17 notes are the first official source that publishes Horde numbers. Use these instead of launch-week guesses.
| What changed | Official note |
|---|---|
| Rewards after wave 50 | Reward tables now grant after wave 50. Wave 50 itself should give both the helmet and the outfit, not one of the two. |
| XP and credits | Extra XP and credits every 5 waves through 100: +500 on waves 5–25, +1000 on waves 30–100. |
| Missed unlocks | On load, the game checks whether you should already have a weapon, class or rank reward and tries to grant it. The developers say some cases may still fail. |
| Queen missions | Dying and losing rewards after the Queen is already dead was fixed. She also freezes less easily and thaws faster. |
Ammo-box and med-kit pickups were a Horde problem too: clients often could not interact until they reloaded. Interact is now prioritized over reload when both are available.
Launch verification checklist
- Confirm the wording and values in the live UI before copying numbers.
- Reproduce an interaction more than once when it affects a recommendation.
- Note difficulty, class, weapon and relevant modifiers for balance-sensitive tests.
- Keep regional storefront facts separate from universal game mechanics.
- Mark player reports as player reports until they are independently reproduced.
This approach makes the guide slower to overclaim and faster to correct. If the final build contradicts a preview, the live build wins and the evidence label should change with it.
On September 29, 2026 the developer posted the third hotfix and used it to set expectations: the next major update is planned for late October, and Horde Mode plus a detailed roadmap are what follow. No date is published for either, so treat any specific Horde Mode launch date you see elsewhere as unofficial until the roadmap lands.