Reporting a problem with a game so it actually gets fixed
What to capture, what to check first, and how to describe a fault so the reply is an answer rather than a request for more detail.
Every game page here ends with the same invitation: if anything on the page does not match what you see in the game, that is a bug and we want to know. This is the practical version of how to tell us — and what to check first, because a good proportion of faults are local and fixable in under a minute.
Check these four things first
Not to dismiss the problem, but because these resolve most of them faster than any message could.
Reload the page. Genuinely. A single failed request during load produces symptoms that look structural and are not.
Try a different browser. This one test separates “something is wrong with the game” from “something is wrong on this device”. If it works elsewhere, the fault is local — usually a stale cache, in which case clearing your cache for the site resolves it, or a browser extension.
Disable extensions temporarily. Script and privacy blockers break things silently, with no error to see. This is the most common cause of a feature that does nothing when clicked.
Check your connection. If the page loaded but behaviour is delayed rather than absent, that is likely latency rather than a fault — connection quality and lag covers how to tell.
If the problem survives all four, it is worth reporting, and you now have four useful facts to include.
What to capture, while it is happening
The single biggest difference between a report that gets resolved and one that stalls is whether it was captured at the time.
- A screenshot of the actual state, not the screen afterwards.
- The exact page URL. Every game has its own address; “the fish game” narrows it to five.
- Any error text in full, including codes that look meaningless. They are not meaningless to whoever reads them.
- What you did immediately before, in order. Faults that only appear after a specific sequence are the hardest to reproduce and the most useful to describe.
Crop screenshots before sending. They often carry more account detail than intended — the safety guide covers that habit.
How to describe it
Three sentences, in this order, beats three paragraphs in any order:
- What you expected.
- What happened instead.
- How to make it happen again, if you know.
Then the context: device, browser and version, roughly when, and what you already tried from the list above.
Compare:
“The game is broken.”
“On /games/fish/tide-hunter, the how-to-play list shows five steps but step 4 does not match what the game does — it says confirm before firing, and the game fires immediately. Chrome on Android 15, happens every time, reloaded and tried Firefox too.”
The second is actionable on arrival. The first cannot be investigated at all, and the reply will simply ask for the second.
Where to send it
Through the contact page. WhatsApp, Telegram and Messenger are listed there and those are the only support routes that exist — a support account that finds you somewhere else is not one of ours.
Which to choose barely matters for a bug report; pick whichever you already use. What does matter is keeping one thread rather than starting several, because a split conversation is slower for everyone.
Never include your password. No support process requires it, and there is no fault it would help diagnose.
What counts as worth reporting
More than people assume:
- A game page that does not match the game. Features listed that are not there, or steps in the wrong order. This is the one we ask for explicitly.
- Something visually broken — overlapping text, a control you cannot reach, content running off the screen.
- A control that does nothing, after you have ruled out extensions.
- Anything about your balance or account that looks wrong.
- A page that will not load when other pages do.
Small cosmetic issues are worth mentioning too. They are usually quick to fix and easy to miss internally, precisely because they are small.
What happens next
An honest note on expectations: no response-time commitment is published on this site, so we are not going to quote you one. Reporting something is not a guarantee of a fast fix.
What a good report does guarantee is that the first reply can be about the problem rather than about gathering information. That is most of the delay in practice.
If it is a content error on a game page, it is the kind of thing that can be corrected quickly. If it is behavioural, it will take longer, and a report that can be reproduced is the difference between a fix and a shrug.
Common questions
The game is not working — what should I try first? Reload, try another browser, disable extensions and check your connection. Those four resolve most cases of a game not working, and give you useful detail if they do not.
What should I check before reporting a bug? Reload, try another browser, disable extensions, and check your connection. Those four resolve most issues and give you useful detail if they do not.
What information should I include? The page URL, what you expected, what happened, how to reproduce it, your device and browser, and any error text in full.
Where do I report a problem? Through the channels on the contact page. Those are the only support routes that exist.
How quickly will it be fixed? There is no published response commitment, so no timeframe is promised here. A reproducible report is the thing most likely to move it along.
Should I report small visual issues? Yes. They are quick to fix and easy to miss from the inside.
Do I need to include my password? No. Never, for any report.
Related guides
Keep reading