See a map correction report example
Map correction report: a worked draft
This example shows how to organize a question about an access condition. It is a writing example, not an observed error in the game. Replace each part with your own evidence before sharing it. A useful draft makes uncertainty visible instead of presenting an untested assumption as a fact.
- Location name
- Copy the exact name from the card you want reviewed.
- Observation
- The card and its linked guide appear to describe different entry conditions. I cannot tell whether they refer to the same visit or entrance. Please check the requirement against the linked section before changing the note. I have not measured a replacement map position.
- Public reference
- Paste the relevant guide URL or public recording link. Include the section name or timestamp in the observation so a reviewer can find the evidence without searching the whole source.
Keep platform and version details in the observation when they affect the issue. After downloading this map correction report, read the TXT file and confirm it contains the intended entry and reference. A downloaded draft is not a submitted ticket. Save the file somewhere you control, then use an available contact channel separately if you decide to send it.
Writing a map correction report that can be checked
What makes a map correction report useful?
Start with the record as it appears in the atlas. The exact marker name distinguishes it from similarly named places and helps a reviewer find the same card. Quote only the short statement you are questioning, then describe the difference. A report about an access requirement is different from a report about spelling, source attribution or schematic placement.
For example, a useful draft might say that a card mentions a key requirement, but the linked guide appears to discuss a different entrance. This is a reporting example, not a claim that a particular game entry is wrong. Include the relevant section of the source so the reviewer can examine the context before changing the note.
Make observations reproducible
Add platform, game version and progression conditions when you know them. If your reference is a public recording, include the moment where the relevant landmark or requirement appears. Do not replace missing evidence with certainty. It is fine to say that you could not confirm a condition or that two sources appear to disagree.
Keep unrelated map corrections in separate drafts. A single report that mixes several regions, spelling changes and interface problems is harder to review. Small reports also make it easier to explain which part was checked and which remains uncertain. The helper does not assign ticket numbers or promise a response time.
Distinguish reference notes from map positions
The source ledger explains that every current coordinate is illustrative. Reporting that a drawing is not geographically exact does not by itself establish a replacement position. A usable coordinate correction needs an identified base map, a consistent scale and evidence connecting the point to that map.
For a note or requirement, consult the publication linked from the card. The PowerPyx reference and Mobalytics reference are two sources already used in the atlas. Read their own coverage statements before comparing the visit, count or condition described.
Keep control of your report
Download saves a plain text draft locally. Your typing is not added to the progress backup and is not kept after a full page reload. Review the file before sharing it, especially if you pasted text from another document. Sending it through email or another channel is a separate action under that service’s practices.
The privacy policy describes this local workflow. For checklist loss, filter behavior or imports, first consult Help. You can also review free access, the editorial status or return to the regional map. Map corrections do not require a game login or payment.