Use this page for reports about pool.plyyard.com , accessibility feedback, privacy requests and content suggestions. Ply Yard handles these messages. You need not finish troubleshooting first; if an issue is not repeatable, describe what happened.
Email and Subject Line
Feedback is handled by email, not phone or live chat. The button opens your email app with report fields filled in; you review and send the message yourself.
Suggested subject: pool.plyyard.com - issue type and specific result
Example: American 8-ball first-contact ruling.
Write a ReportNo email app configured? Write directly from your usual email service.
Six Details to Include
These help establish the game state, actions and environment.
- Page and mode: Send the page URL with invite, host and recovery credentials removed. Specify AI, local two-player or online play.
- Rules and game state: Name the ruleset, current player and stage of play. For 8-ball, say whether groups were assigned; for 9-ball or 10-ball, identify the lowest ball.
- Steps taken: List actions and buttons in order before the issue. You do not need to restart the game to report it.
- Actual and expected result: Separate what the page displayed from what you expected. Keep any status or error message in its original wording.
- Device and browser: Include device model, operating system, browser and version, and whether you opened it in a browser or from the home screen or Dock.
- Time and evidence: Include the date, time and time zone. Attach a shot log or a screenshot with private information redacted if available.
Evidence for Each Issue Type
Pot or Foul Ruling
Identify the first object ball hit, pocketed balls, any scratch and rail contact after first contact. For the 8, say whether your group was clear. In 9-ball or 10-ball, identify whether first contact was legal.
A screenshot after the shot may not establish rail or collision order. Attach an existing recording if you have one; otherwise describe what you actually saw without guessing unseen events.
Aim, Power or Strike Point
Say whether you used mouse or touch, which drags or taps you made, whether charging started and whether balls were still moving. For unexpected cue-ball motion, include the starting layout, strike-point setting and result if available.
Room Entry, Seats or Reconnection
Specify public or private, host or guest, displayed connection status and whether the opponent was connected. Include the order of any browser changes, new tabs, screen locking or network changes.
To identify a room, email its code and the time. Do not send full invite, host or seat-recovery credentials, and do not publish private room codes in public posts.
Display, Sound or Installation
For obscured text, unusable buttons or layout issues, attach the relevant area and include orientation, zoom and theme. For sound or installation, include permissions, mute state and how you opened the site.
Safe Attachments and Privacy Requests
Redact notifications, email addresses, other people's names and access credentials in the address bar. Do not send passwords, identity documents, payment details, addresses or unrelated sensitive information.
Use ordinary screenshots, necessary screen recordings and plain-text logs. Do not send executables, macro-enabled documents or archives from unknown sources.
Put 'Security report' in the subject for a security issue. Email details privately; do not publish exploit instructions, test someone else's room or send attack traffic to reproduce it.
For access, correction or deletion requests, specify the data category, relevant time range and requested action. The privacy policy explains how reports and attachments are used and retained.
How Reports Are Handled
Data and room-access risks, rulings that affect play and unavailable features are prioritized for checking. We may ask for versions, a shot log or steps, but not passwords or full access credentials.
There is no guaranteed reply time or promise to implement every suggestion. Reply in the same email thread with new findings or changes to preserve the report history.
For a feature suggestion, describe the specific difficulty and the outcome you want. For unclear existing behavior, point to the page and wording involved.
Before Sending
- Separate actual and expected.
- Include device, browser and time.
- Redact private data and tokens.
Mark uncertain details as uncertain. Do not repeat risky actions just to complete a report.
Write a Report