Contact and corrections

What to include

• The page URL.
• The exact claim or section.
• The current game version and platform.
• An official source or reproducible observation.
• A short explanation of the proposed correction.

Do not send sensitive or copyrighted files

Do not send passwords, one-time codes, API keys, payment details, private crash logs, game binaries, cracked files or copyrighted video archives. A public source link and concise reproduction path are enough.

Security reports

Describe the affected URL, expected behavior, observed behavior and a non-destructive reproduction. Do not access data that is not yours or publish an active exploit before there is time to investigate.