2048.plyyard.com currently accepts bug reports, accessibility feedback, privacy requests, and feature suggestions by email. First remove any unnecessary personal information, then describe the mode, stage of the game, and sequence of actions involved.
Email address and suggested subject
Use “2048.plyyard.com - issue type” as the subject format; for example, “2048.plyyard.com - daily challenge will not load.” We do not currently offer support by phone or live chat.
What a useful report should include
- Page and features: The full URL and whether daily challenge, hints, or undo were involved.
- Game phase: Score, max tile, whether you reached 2048, or the board was already locked.
- Steps to reproduce: Start from a normal state and list, in order, the squares you clicked, the buttons you used, and what actually happened.
- Expected result: Explain how tiles should have merged, how the score should have changed, or what hint or undo should have done.
- Environment: Device model, operating system, browser and version, and whether the site was opened as a home-screen PWA.
- Evidence: You may attach a board screenshot, error message, and approximate time. If local best score or recent games are involved, say whether you recently cleared site data.
What to check before writing
- Merges, scoring, and end conditions: 2048 Rules.
- Corner strategy and space control: 2048 Strategy.
- Local best scores, recent games, and logs: Privacy Policy.
- Service scope and acceptable use: Terms of Use.
Privacy and attachment safety
- Do not send passwords, payment information, identity documents, a home address, or other sensitive data that is unnecessary for troubleshooting.
- Before taking a screenshot, obscure notifications, browser tabs, email addresses, and other people's names.
- Do not send executable files, macro-enabled documents, or archives from an unknown source. Ordinary screenshots and plain-text steps are sufficient.
- Clearly label a security issue as “Security report,” and do not publish exploitable details in a public community post.
How reports are handled
We classify reports by rules errors, data or security risk, site-wide outages, isolated interface issues, and feature suggestions. We cannot promise a fixed response time or that every suggestion will be implemented. Reproducible problems affecting merges, scoring, or local records receive priority.
A reply may ask for a browser version, screenshot, or more precise reproduction steps, but it will not ask for your password. For matters concerning the wider Ply Yard studio, visit Ply Yard.
