Contact

Checked 2026-11-08 · Site

One address, one purpose, one person reading it.

[email protected]

What to send

A correction. If a number on this site disagrees with the game, send the page and what you see. Badge counts move daily, and a screen capture of the badge in game settles it faster than anything else.

A missing mechanic. Several pages here only describe what the official material confirms. If you have found something the badges and the description do not cover — a room, an animatronic behaviour, a step in the escape — send it with how you found it and it can go on the right page with the source named.

A takedown request. If you hold rights to an asset used here and want it removed, say which file and where it appears, and it comes down. All imagery on the site is official Roblox promotional material, but a rights holder's request gets honoured without argument.

A broken page. Wrong link, image that will not load, a table that scrolls off the side of a phone. Those get fixed the same day they are read.

What not to send

Code requests. There is no code system in Closing Shift, so there is nothing to send and nothing to give. See wiki and codes.

Requests for the four-digit code. The code is generated per night and printed on the exit panel in your run. A number from another player's run yesterday is not an answer; the page that explains why is here.

Account or purchase problems. This site has no access to Roblox accounts, no ability to grant items, and no connection to the developer's store. Roblox support handles those, and the developer's own game page is the place for a bug report about the game itself.

What a good correction looks like

The corrections that get published fastest have four things in them:

1. The page. A URL or the page title is enough.
2. The claim that is wrong. Quote the sentence so there is no ambiguity about which number is in dispute.
3. What you saw instead. A number, a room name, a badge condition — whatever the game showed you.
4. When you saw it. The game ships weekly, so a correction from three weeks ago may already be fixed.

Four lines like that is a five-minute fix. A message that says "the badge numbers are wrong" with nothing else takes a week of re-reading API responses to answer, because the counts move every day and there is no way to tell which figure drifted.

How long a reply takes

A few days, usually. This is a one-person project run alongside other work, not a support desk. Corrections that arrive with evidence get prioritised, because they are quick to verify and quick to publish.

Before you write

Three things worth checking first, because they answer most of what arrives:

If your question is not in those three, it is exactly the kind worth sending.

Privacy

Nothing sent to this address is published without permission, and no address is added to any list. What the site itself collects is described on the privacy page.