Everything you need to build a game on Pedung, what it costs, and the rules every game follows.
How building works
The design questions
AI builds what your brief says. A one-line brief leaves most of the game to guesswork — how long a go lasts, what ends a run, which buttons exist — and guesswork is what you end up paying to fix, one change at a time. The design questions ask those things up front, so the first build already looks like the game in your head. Fewer changes, fewer credits.
Answering is completely free. Every question and every option is built into the app. Credits start when you press Build.
In a hurry? Skip the questions on Create gives you the old one-box brief, and the Review step lets you rewrite the whole idea in your own words before building.
The optional design review. On the last step you can ask AI to read the finished design and come back with two to four questions about the holes in it — each with a suggested answer you can accept or ignore. AI review costs credits. The price is on the button before you press it, and Skip — build my game sits right next to it.
Credits & what a build costs
1 credit = 1¢ paid. Credits are how you pay for AI. You buy them with a plan each month, or with a top-up whenever you want more.
What a build costs. A build costs what the AI actually used, multiplied by 2. A small game is a few dozen credits; a long, detailed brief with several photos costs more. A small change costs less than a first build.
You always see the price first. Before anything runs, Pedung quotes the worst case — the most the build could possibly cost — and holds that many credits. When the build finishes you're charged the real amount and every unused credit comes straight back. Every build shows an itemised receipt on Credits.
When your balance is short, you'll see “Your tokens need to be topped up before proceeding.” — and AI runs once your credits cover it. That's the guarantee: every build is paid for before it starts. Top up from that message, or from Pricing.
The standard controls
Every Pedung game uses the same control layout. Players swipe from one game straight into the next, so the controls carry over every time: move is always bottom-left, action is always bottom-right, pause is always top-right. AI builds your game this way automatically.
It works the same way sideways — the anchors just hug the wider screen. Buttons keep clear of notches and home bars, and are always at least a thumb wide.
On a keyboard: Move WASD or arrow keys · Action Space, or click / tap · Second action Shift · Pause Esc or P.
The full specification, with exact CSS anchors, is in docs/controls.md.
Leaderboards
A game gets a leaderboard automatically. It happens because the game reports its score to Pedung when a run ends, and AI builds that in for you.
A leaderboard appears as soon as a game reports a score. To add one, ask for the change in the studio: “report the score when the run ends”.
The message format is specified in docs/leaderboard-protocol.md.
Safety rules
Pedung is for everyone 13 and up. Every brief, photo and finished game is safety-checked before it runs, and every published game plays inside a locked-down sandbox. Requests that break the rules are refused, and repeated attempts cost you the ability to build.
The game file format
Uploads open later on, and then a game must be one self-contained HTML file. AI-built games are already held to exactly these rules.
.html are rejected on sight.data: URLs inside the file. Everything a game needs travels with it, so it plays the same way for ever after it's published.fetch, sockets, forms or iframes. That keeps a 13-year-old on Pedung, where play is supervised.eval code or large hidden blobs. Each one is a way to hide what a file really does — and the sandbox enforces this at runtime too.The full list, and the reason behind each rule, is in docs/game-format.md.
Still stuck? support@pedung.com