Creator guide
Making Custom Maps
Custom maps are this game's deepest creative outlet, and the pipeline is refreshingly official: a community-canonical Steam guide, a creator workflow run through the official Discord, and Workshop publishing. This page maps the road and adds the part nobody documents: what makes a hide-and-seek stage actually good.
The Sanctioned Pipeline, Start to Ship
Three stations, in order. First, the Steam Community guide "Making (& Publishing) a Custom Map" (sources below) — the community's canonical walkthrough of tooling, setup and the publishing flow. Second, the creator workflow linked through the official Discord (verified entry here), where the living documentation and the people who answer first-map questions live. Third, Steam Workshop publishing — which handles distribution, updates and installs so completely that your players never touch a file. Everything stays inside the Steam/Discord ecosystem; any site offering a "map editor download" outside it belongs to the economy we document elsewhere.
The Design Rubric: What Makes Hide-and-Seek Geometry Good
Here's the part tooling guides skip. A great stage for this game balances four currencies — the same four our archetype guide teaches players to read. Clutter: enough busy zones that imperfect painters have somewhere to learn, but not so much that Seeking becomes homework. Elevation: perches and trim that reward wall-stick skill without putting half the lobby on the ceiling. Flat surfaces: some pattern-rich walls for the high-skill flat hide — with lighting even enough to make paint-matching fair. Mimicry: repeated props whose "inventory" a Seeker can learn and count against. Then audit traffic: walk your map as a Seeker and check that a sensible zone order exists — stages that force backtracking make rounds drag. The official maps are the syllabus here; Mansion's density is the reference for archetype balance.
Shipping Well: Listing Hygiene and Iteration
The Workshop rewards maintainers. At publish time: honest screenshots from player height (not just glamour overviews), a description that names the map's size and intended lobby count, and known issues listed plainly — subscribers forgive bugs they were warned about and uninstall over ones they weren't. After launch: treat comments as playtest data, patch in small increments, and note changes in the listing so returning players know the map moved. And playtest against real humans early — a private lobby with friends surfaces in one evening what solo walking never will: where Hiders cluster, which sightlines are unfair, and whether your favorite room is anyone else's. Creators who do this are how the map pool stays the game's renewable resource. Two last details that punch above their weight: name your map something searchable (hosts type it into the Workshop under social pressure at game night — "Untitled_Final_v2" loses to anything memorable), and time your updates away from the game's own patch days when you can; with the developer shipping near-daily, stacking your changes on top of engine changes makes every bug report ambiguous about whose bug it is.
FAQ
Pipeline at a Glance
- DocumentationSteam guide + Discord
- DistributionWorkshop only
- Player installOne-click subscribe
- External editorsNone sanctioned
- Design referenceOfficial maps
Last checked: 2026-07-03