What we can say with confidence
This system rewards experimentation because leveling a weapon can expand options for another favorite later. That makes “which weapon should I level?” a progression question as much as a damage question. Exact trait numbers should be copied only from the live build or a verified source. 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 evaluate weapons instead of chasing one DPS number
For Aliens, compare more than paper damage. Track damage type, ammunition behavior, handling, unlock timing, available traits and augments, and the enemies you expect to fight. A weapon can be excellent because it solves a matchup or unlocks a transferable trait even if another gun has a larger headline number.
On higher difficulties, resource pressure also changes value. A loadout that is comfortable on Standard can become awkward if it burns scarce ammunition or forces risky positioning. The launch version of this guide should therefore pair every “best” label with the use case that makes it best.
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.