How guides are assembled
Our current guides are assembled by checking public game references and attributed images. We organize information into requirements, actions, completion checks and troubleshooting. Conflicting accounts are distinguished from usable routes. Unless hands-on verification is explicitly stated, do not assume the editor personally completed a route.
An update date is an editing date
An article’s update date records a content edit, including route additions, corrections or restructuring. It does not automatically mean the guide was retested on the latest patch. Unconfirmed versions or conditions remain identified in the article. When reporting a difference, include your platform, game version and current journal objective.
What an image can establish
Maps, interaction targets and reward screens explain the adjacent step and retain attribution. A regional map is not a precise location, and a comparison of item names does not establish a different item’s drop location. Game assets and images belong to their respective rights holders. Use the correction channel below for attribution or usage concerns.
Report an error or missing step
Include the guide URL, the step where you are stuck, the journal text, and the expected and actual result. A screenshot identifying the same location is particularly useful. Follow the public feedback record for further discussion. Unverified reports are not treated as established game facts.
Report a guide correction · View existing feedback
The separate public GitHub feedback area requires a GitHub account, and submissions are public. Do not include email addresses, save-file secrets or other private information. Site analytics permission is not required.