What we can say with confidence
The useful part of a requirements page is not repeating a table; it is preserving the performance target attached to that table. A minimum GPU is not a promise of 60 fps at high settings, and a recommended line is not a guarantee for 1440p or 4K. 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.
What this means before you buy or launch
For Aliens, use the official statement as the baseline and then check your own platform or region for anything storefront-specific. Do not assume that a timer, entitlement, subscription note or platform badge on one store automatically applies everywhere.
If you are preparing for launch, keep the practical checklist short: update the client, confirm the correct platform edition, verify your online subscription requirements if you play on console, and re-check any time-sensitive store text on the day you play. This avoids most confusion without inventing details the publisher has not published.
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.