Skip to content

Steam ​

What the game's Steam store page and its Steamworks settings need to say about the platform, for whoever submits them. How players sign in through Steam and what an owner may do is in Platform; switching the live platform to the owners is in Operations, and creation on OpenRouter or on Claude in Operations.

The Content Survey: AI-generated content ​

Steamworks' Content Survey asks a game that uses AI to say how, in two parts: pre-generated content (made with AI during development and shipped) and live-generated content (made by AI while the game runs), with the guardrails that keep live-generated content within the rules. Five On It has both. The text below is written to be pasted into the survey as it is; check the facts each part marks first, as only the developer and the live platform's settings can confirm them.

Pre-generated content ​

Five On It ships with one curated game, "Smart City Pilot" on the city of Riverbend (four missions), and the building blocks players make games from. The game's code, its procedural city and level generators, its mission texts and the scripts that model its low-poly cars, people and buildings were written with the help of AI coding assistants (Anthropic's Claude), and every part of it was reviewed and tested by the developer before it shipped. The city, its buildings and its vehicles are generated by the developer's own scripts from flat-coloured shapes; no image, texture, voice or music in the game was generated by an AI model.

Check before submitting: that no art, sound or music from an AI model was added since (the placeholder sounds are synthesized by the game's own code, apps/client/audio/), and that the bundled game's texts are still the reviewed ones.

Live-generated content ​

Owners of the game can describe a game in a few sentences on the in-game creation page ("Create"), and the platform makes it on its servers with a large language model: Anthropic's Claude, or one of Google's, OpenAI's, DeepSeek's or Alibaba's models reached through OpenRouter, as the platform chooses. The model can only call the game's own creation tools: it picks a level from the game's closed catalogue (the city of Riverbend, or a small town or a countryside region generated from the game's own building blocks) and writes missions in the game's mission language. Everything it makes is data (titles, texts, missions, the layout of a town or a region), checked against fixed schemas and the closed catalogue before it can be built and played: it cannot write code, make images, sounds, 3D models or any other asset, and it cannot reach the internet. The result is a private draft its owner can play, share by link or publish. Each owner may make five games a day, within the platform's fixed monthly budget for the model; players never give a key of their own.

Guardrails ​

  • Briefs are moderated before any model runs. A word list, then a classifier model, checks every brief; a refused brief is turned away with the reason and costs the player nothing.
  • The model has tools, not freedom. It acts with a session limited to the one draft it makes: it cannot publish, open rooms, chat, read other players' data or call anything but the creation tools.
  • Its output is data, validated. Missions and levels are checked against fixed schemas and a closed catalogue of the game's own assets; nothing it writes runs as code.
  • Its output is moderated before anyone sees it. Every text the model wrote is checked when it finishes, before its owner sees it; a game whose texts are refused is never shown, and the attempt is not given back. A game made by the model is checked again when it is shared by link or published, and public games and the chat of public rooms are always moderated.
  • Players report, moderators decide. Any published game can be reported from its page and any player from the game; moderators decide the reports and take games down, every decision kept in an audit log; a room's players can vote a player out, and an account the publisher banned on Steam is refused. Players can also report through the Steam overlay.
  • Transcripts for the moderators. The conversation of every creation (the brief, the model's words and its tool calls) is kept 30 days for the moderators, then deleted.
  • Privacy. Briefs go to the model without the player's name or account, and only to providers that do not keep them for training.

Check before submitting: that the live platform runs with a classifier as well as the word list (FOI_MODERATION=openrouter or chain; the stack refuses creation on OpenRouter or Claude with no moderation at all) and with moderators named (FOI_MODERATORS), that the creation page is open to owners only (FOI_ENTITLEMENT=steam), and that the Steam overlay opens in the desktop app.

The store page ​

The store page should say what a player can expect of creation, in a line: "Describe a game and the platform makes it for you: five creations a day, while the month's creation budget lasts." The platform says when creation resumes when the budget is spent for the day; the cap is FOI_CREATOR_MONTHLY_USD (Operations).