baseball.plyyard.com takes bug reports, accessibility feedback, privacy requests, and feature ideas by email only. There is no account system and we cannot pull your personal game from a server—so the URL, mode, and step-by-step actions in your message often decide whether we can fix it quickly. Redact personal info from screenshots and the body before you send.
Contact address and email subject
Support inbox: contact@plyyard.com
Use a subject like “baseball.plyyard.com - issue type,” for example “baseball.plyyard.com - career stars gone after clearing data” or “baseball.plyyard.com - party score stuck after half inning.” We do not offer phone or live chat support.
What an effective issue report should include
- Page and mode: The full browser URL and whether you were in career, the daily derby, practice, an AI exhibition on the match and party page, or same-screen party play.
- Game phase: The current score, the inning, and whether you were pitching, batting, or at the end of a half-inning.
- Steps to reproduce: Start from a normal state and list, in order, the swipes, buttons, and what actually happened.
- What you expected: For example “should have been a base hit but counted foul,” “derby multiplier did not stack,” or “replay button stayed gray”—as specific as one pitch or one level.
- Environment: Device model, operating system, browser and version, graphics preset, and whether the site was opened as a home-screen PWA.
- Evidence: You may attach a field screenshot, error message, and approximate time. For career issues, include the level number if you can.
What you can check first
- Scoring, strikes, and outs: Baseball Rules.
- Reading the ball and replay: Match Tips.
- Local storage and progress: Privacy Policy.
- Mode differences, AI limits, and no cross-device rooms: Terms of Use and About.
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 and what replies cover
Mail is sorted into rules bugs, local save issues, site outages, 3D performance or UI glitches, accessibility, and product ideas. We cannot promise a fixed reply time or that every idea ships; reproducible issues that break scoring, career stars, or data safety get priority.
Follow-up may ask for browser version, graphics preset, or tighter steps, but never a password—there is no login here. For other Ply Yard games or partnerships, visit the Ply Yard hub; for this baseball game, use the inbox above.