What we can say with confidence
Combat Rating is best treated as a readiness summary, not proof that a build is good. A high rating can indicate more progression invested, while actual performance still depends on role, synergy, damage type, positioning and player execution. 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.
How to apply the system in real missions
For Combat Rating Explained, mechanics only become useful when they change a decision. Ask what the system tells you to do differently: switch damage type, protect a firing lane, save ammunition, improve a weak loadout slot, or reposition before friendly fire becomes a problem.
The sequel’s four-player structure increases the value of coordination. The strongest individual choice can be the wrong squad choice if everyone brings the same answer and nobody covers the threats that punish it. This is why live testing should record team context as well as individual performance.
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.