Forge answers what a game costs, what the last patch changed, whether anything is down, and what a signed-in player owns — live on this page tonight, and shown here exactly as it reads in the studio's #support channel.
Three releases, every price and build number current. Forge answers from exactly this list — including the one that is not finished yet.
Atmospheric puzzle-platformer · about 9 hours
Carry the last light down through a drowned cave system. No combat and no timer — the light is the puzzle, and it burns down as you use it.
Turn-based tactics · runs of 40–90 minutes
Six squads, one dying forest, permanent losses. Every run reshuffles the map and the enemy doctrine, so no two campaigns rhyme.
Arcade rally racer · weekly leaderboards
Eleven desert stages, one car you rebuild between runs, and a sun that sets while you drive. Stages 12–16 and the replay editor are still to come.
Pixelforge Games is three people above a seaside arcade: one designer, one engineer, one who does art and everything else. There is no publisher and no support tier — a bug report goes into the same weekly triage the next build comes out of.
The last five releases. Ask about any line of it and Forge searches these notes rather than guessing at what an update "probably" fixed.
Sundog Rally weekly boards have been recalculating since 08:20 UTC. Times are being recorded, they are just slow to appear.
Pixelforge Games' community server is not connected yet — so this is neither a recording nor a mock-up. The window below wraps the exact live assistant in the chrome of a Discord channel, so you can read the conversation the way a player would after typing in #support.
Everything in this window runs on Forge's real brain, the same three games, the same patch notes and the same tools as the sections above — only the wrapper is a channel's. Ask what changed in a build, report a bug, or ask for a person, right here.
This becomes a real invite soonThe "Join our Discord" button above does the same thing until the server is connected — it scrolls here. No invite link is invented in the meantime.
The same brain, knowledge and tools as the window above — just reached the way a community app actually delivers a message.
Someone writes in #support, or mentions the studio's bot. The player always opens the conversation; the studio never posts into a thread unasked.
The message arrives over the app's own gateway, its signature is checked, and it becomes a visitor turn with the same tool floor as the chat on this page — no platform tool ever reaches a player.
A patch note, a status line, a bug card or a hand-off — posted as a threaded reply, so the channel stays readable and a developer can pick the thread up where it stopped.
What this page really does, block by block, and the exact doc for putting the same on your own site.
The bubble in the corner and the channel window above are one live product on a workspace of its own; a single line of HTML put it here.
The games, the patch notes and the refund policy above were published to the workspace as text. Answers quote them; anything outside gets an honest "I don't know".
Five actions are registered on this page over WebMCP — list the games, search the notes, check the services, read a signed-in library, open the bug form. Ask for one and watch it run.
Pixelforge runs a small MCP server of its own, connected to the workspace. The catalogue, the notes and the status board come from there over HTTPS — the same answer in a channel as in this tab.
How to add this to your site →Say something broke and a form opens inside the chat — which game, which platform, what happened, an email, one button — instead of four questions in a row.
Sign in as the demo player below and Forge can read that player's own library, the build they are behind on, and start a refund — for them and nobody else.
Ask for a person and the thread lands in the studio's inbox mid-conversation — the same hand-off works in a channel once one is connected, no restart and no ticket number.
Signed out, the catalogue, the prices, every patch note, the service board and a bug report all still work — for a player and for any agent. Only a library and a refund wait for a signed-in proof of who's asking.
An agent that never renders this page can still work with it: a plain-text brief, a tool manifest, the whole corpus in one request, and the live schema behind every action.
The six layers, checked →The window above is labelled for exactly what it is at any moment: the real assistant in a faithful frame, and a real invite only once a server is actually connected — never an invented link.
See every channel's real status →Two checkers grade any address, this page included: one scores how ready a site is for AI agents, the other lists the tools a page publishes.
A throwaway demo player is provided — no password, no real person, no real purchase.
Demo player: Kai Moreno, tag kaim#4471 — owns Lumen Drift (receipt PF-40271), Ironroot Tactics (PF-41188, one build behind) and Sundog Rally (PF-41903, bought three days ago, 0.6 hours played, so it is still inside the refund window). A throwaway public demo identity, not a real person.
"Reported a save bug on a Sunday, got a build number back in the same thread and the fix two weeks later. That never happens."
"Asked whether the campaign reroll was in yet and it quoted me the actual patch line instead of telling me to read the notes."
"Bought the rally game, decided it was too early for me, refund started from the chat in under a minute. No form, no ticket."
Forge answers first, at any hour, and hands over to whoever is at the desk the moment you ask for a person — in the same conversation, with everything you already said still there.
Pixelforge Games#support, previewed above