chinesecheckers.plyyard.com currently accepts issue reports, accessibility feedback, privacy requests, and feature suggestions by email. Remove any unnecessary personal information first, then describe the mode, stage of the game, and sequence of actions involved.
Contact address and email subject
We suggest the subject format “chinesecheckers.plyyard.com - issue type,” for example, “chinesecheckers.plyyard.com - online room will not reconnect.” The site does not currently offer support by phone or live chat.
What an effective issue report should include
- Page and mode: The full URL and whether you were playing against AI, sharing one device, or using an online room.
- Game phase: Whose turn it was, how many marbles had already entered camp, and whether the opponent's camp was already full.
- Steps to reproduce: Start from a normal state and list, in order, the holes you tapped, the buttons you used, and what actually happened.
- Expected result: Explain which move you believe should have been legal, which cue should have appeared, or what state the room should have been in.
- 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, move record, error message, and approximate time. For room issues, a room code is useful; the complete private invitation link is not necessary.
What you can check first
- Legal steps, hop chains, and filling the opposite camp: Chinese Checkers Rules.
- Leaving home, hop ladders, and review methods: Chinese Checkers Strategy.
- Local storage, reconnect tokens, and room data: Privacy Policy.
- Online rooms, service limits, 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, private room links, 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 room or community post.
How reports are handled and what replies cover
We classify reports as rules errors, data or security risks, site-wide outages, isolated interface problems, or feature suggestions. We cannot promise a fixed response time or that every suggestion will be implemented. Reproducible problems affecting legal moves, data, or room permissions receive priority.
A reply may ask for your browser version, a move record, or more precise reproduction steps, but it will not ask for your password. For matters concerning the Ply Yard studio as a whole, visit Ply Yard.
