Active Matter Extraction Points | Active Matter Guides

How to use this page

Start with the direct answer, then use the database snapshot to turn the conclusion into a run plan. For map topics, compare status, documented points and update pressure. For weapon topics, compare category, caliber, confirmed rate of fire, range and acquisition before thinking about attachments.

This page deliberately separates public evidence from editorial interpretation. It does not convert a patch mention into a numeric estimate. If a route or build depends on a missing value, treat that value as a research task and verify it in the live client after the current update.

The linked databases are intentionally broader than this single keyword. Use them when your objective changes: a new investigation may send you to a different map, and a new acquisition path can make a previously ignored weapon worth checking again.

Verified snapshot

Official announcements and platform pages are prioritized. Community pages are used only for clearly labeled context when official material does not cover a topic, and they do not override the pending-verification rule.

Maps database snapshot

Research workflow

1. Write down the objective: route, quest item, acquisition, progression reward or anomaly you need to handle.
2. Check the linked official source and this page's conditions table before spending raid preparation resources.
3. Open the relevant map records to compare region, release state, threats, documented points and recent changes.
4. Open weapon records for caliber, confirmed rates, range, attachments and acquisition paths rather than relying on memory.
5. In game, confirm the live rotation, objective marker, keyed access and inventory space before committing to the route.
6. After extraction, note which public values no longer matched the client. Those observations become the next items to verify, not silent estimates.

Map records to open

Condições e limites

How this page is maintained

Each revision starts from the linked official website, platform record, news post or patch note. The database records only the fields those pages actually disclose. If a source names a map, weapon, objective or acquisition path without publishing a numeric table, the narrative fact stays and the missing number remains pending rather than being inferred from a similar item.

Community material is useful for finding a behavior worth testing, but it is not treated as proof of a current value. A community page can preserve an older interface, omit a mode-specific condition, or turn an anecdote into a general rule. For that reason, this page keeps official and community evidence separate and repeats the check date on every time-sensitive claim.

After a new Active Matter update, the relevant route is to reread the official source, compare it with the records linked here, and update the affected page only when the evidence is clear. If live behavior differs from a saved public source, the wiki marks the conflict for review instead of choosing whichever description seems newer.

FAQ