What you can contact us about
We welcome reports about incorrect names or values, missing relationships, broken links, map marker problems, tool calculations, translation errors, accessibility barriers, and pages that do not answer the player question they claim to address. Feature suggestions are most useful when they describe the decision or task the player is trying to complete.
Privacy questions, requests to review locally stored site data, attribution corrections, and good-faith rights-holder notices may use the same address. Each category is reviewed according to the evidence available and the scope of this independent site.
What to include
Include the exact page URL, selected language, device or browser when relevant, and a concise description of the expected and actual result. For a data correction, identify the current game version and attach a small screenshot or reproducible source if you are allowed to share it. For an accessibility issue, describe the navigation method or assistive technology involved.
Do not attach credentials, payment records, private account identifiers, or a raw save database. The save reader runs inside your browser; the project does not need your save file to answer a general support question. Redact names and identifiers from screenshots before sending them.
Requests outside this site's scope
We cannot recover a game account, purchase, character, currency, or save; reverse a ban; investigate another player; or provide publisher support. Contact the game publisher, Steam, or the relevant platform for account, transaction, enforcement, and cloud-save issues.
We also cannot promise individual build advice, drop outcomes, or future release dates. Tools report the verified data and constraints available in the current site snapshot, but live combat, random rewards, account ownership, and later balance changes remain outside the site's control.
Contact channel and response expectations
Email support@dsawakening.wiki. A clear subject such as “data correction,” “accessibility,” “privacy,” or “rights request” helps route the message. A message is not an emergency or official publisher ticket, and delivery does not guarantee a particular outcome or response time.
Actionable corrections are verified before publication so one report does not replace one unsupported claim with another. Rights and privacy notices receive priority over general feature ideas. If a report changes public content, the update may appear with the next validated data or site release.