What makes a mission report useful

EvidenceWhy record itWeak alternative
Game versionSeparates current behavior from older balance and loot rulesSaying only that it happened recently
Mission and stationConnects the report to generated context and category evidenceNaming a planet without the station type
Faction and opponentReveals which content pool and Technology may have matteredAssuming every enemy on the floor was identical
Container and floorMakes the physical discovery reproducibleSaying the item dropped somewhere
Outcome and extractionSeparates an observed spawn from a successfully recovered itemTreating inventory memory as confirmed extraction
Mods activeFlags a major source of non-vanilla behaviorLeaving mod status unknown
Quasimorph mercenary moving through a neon-lit corporate facility during a contractOFFICIAL GAMEPLAY
Official gameplay: corporate facilities mix narrow sightlines, patrols, loot rooms, and extraction routes.

Record locally, then decide whether to publish

  1. 01

    Complete the context first

    Copy values from the mission and result screens while the run is fresh. Exact names and locations are more useful than long narrative speculation.

  2. 02

    Save the local record

    Validation catches missing version/item fields and impossible numeric ranges. The newest 50 normalized records remain on this browser.

  3. 03

    Copy or download JSON

    Use structured export for a personal archive, comparison, or attachment. Export does not publish anything.

  4. 04

    Review the public issue

    Open the prefilled GitHub Issue only when you want to contribute. Read the title, summary, notes, and JSON before pressing GitHub's final submit button.

A report starts as evidence, not a site fact

One player result can show that an event occurred under stated conditions, but it cannot establish a universal guaranteed drop. Multiple consistent reports, a current official source, or reproducible game data are needed before recommendations should become stronger.

The public issue queue preserves discussion and correction history. Review can compare patch, station, category, faction, container, floor, mods, and contradictions before changing Item Finder language. This protects the main database from confident but unrepeatable anecdotes.

FAQ

Frequently asked questions

Does saving a result publish it?

No. Save writes only to local browser history. Copy and download remain local actions; public submission begins only when you explicitly open and submit the prefilled GitHub Issue.

Will one report change the Item Finder?

No. Reports are reviewable evidence, not automatic truth. Recommendations should change only after the version and context can be checked against other evidence.

Research trail

Sources and further reading