Contact this site

Unlike most contact pages, this one will not promise a reply within one business day, because there is no support team on a rota. What it will do is tell you honestly what happens after you press send, what belongs in a message and what does not, so that your email reaches the right place on the first attempt.

What to write about

This address is for the site: the pages you are reading, not the game they describe. The most valuable messages fall into four groups.

• Corrections. A guide that says a key does one thing when it does another, or a page whose steps no longer match what happens on screen.
• Unclear guides. A paragraph you had to read three times, or a step that assumes knowledge you did not have. Knowing where a page loses a reader is as useful as knowing where it is wrong.
• Bugs on this site. A broken layout, a link that goes nowhere, a tool that will not load, a language switch that sends you to the wrong page, or a page that is hard to read with a screen reader.
• Questions the site has not answered. If you looked for something and could not find it, that gap is worth reporting even if you eventually worked it out yourself.

What to include

A useful report usually contains four things, and they are all quick to gather. Without them, a bug can be impossible to reproduce and a correction can be impossible to verify.

1. The page address. The full URL, including the part after the domain, so there is no guessing about which page and which language you mean.
2. Your browser and device. Chrome on Android, Safari on an iPhone, Firefox on a laptop — the description of a bug often only makes sense once this is known.
3. What you expected and what you saw. Two short sentences are enough: the behaviour you assumed and the behaviour you got instead.
4. A screenshot if you have one. For anything visual, a single image saves several rounds of clarifying email.

What this address cannot help with

This site embeds and documents the game; it does not publish or control it. That means some requests have nowhere to go here, however politely they are written.

• Game bugs and crashes. Only the game's own creators can change the game. We can document a behaviour, but we cannot patch it.
• Account problems. There are no accounts here, so there is nothing to recover, reset or delete. If a game asked you to sign in, that is the game's own system, not this site's.
• Advertising or payment questions. This site has no paid products and does not sell anything, so there is no purchase to refund.
• Requests to remove the game from this site. The playable build is served by its own origin and embedded; ownership questions belong with the game's creators.

How long a reply takes

Honestly: longer than a large site, and inconsistently. This is a small independent project, not a company with a support rota, so messages are read in batches and answered when the person who knows the relevant page has time. A report that will not wait for a reply, such as a broken link, is still worth sending — it will be read even if the answer arrives after you have moved on. A question that does need an answer may take a few days, and occasionally longer around holidays. If you have not heard back, that is not a judgement on your message; it is just the pace of a site this size. Nothing is ever promised within a set window, and there is no escalation path to ask for one.

For questions about how the site handles data, the privacy policy already answers most of them. For what is and is not allowed on the site, the terms cover acceptable use. And if your question is simply about the game, the FAQ is faster than an email.

Frequently asked questions

Is there a contact form?

No. This site has no form and no chat widget; email to [email protected] is the only channel. It is a forwarding address read by a person.

How fast is a reply?

There is no fixed window and no support rota. Messages are read in batches, so routine questions can take a few days, and game bugs cannot be fixed here at all.

Should I report a bug in the game?

This site only embeds and documents the game, so it cannot patch it. It can, however, record and explain a behaviour worth knowing about.

What information should I include?

The page URL, your browser and device, what you expected, what you saw, and a screenshot if the issue is visual.