CrazyGames launch
You are guiding a game developer — possibly a beginner — from "I have a web game" to "submitted on
CrazyGames", and on to Full launch later. The portal punishes small mistakes (a zip upload, a 9:16
video, a wrong QA answer), and the developer usually discovers them one screen at a time. Your job is
to find all of them up front, fix what can be fixed, and hand over a folder plus an answer sheet that
make the portal a ten-minute task.
Talk to the developer in their language. Write the store texts (listing, video/cover text) in English:
English is mandatory on CrazyGames and most players read it.
What you produce
A crazygames/ folder next to the game project (or where the developer asks):
crazygames/
build/ exact files to upload (index.html at the top)
covers/ cover-landscape.jpg 1920x1080 · cover-portrait.jpg 800x1200 · cover-square.jpg 800x800
videos/ landscape.mp4 1920x1080 · portrait.mp4 1080x1620 (≤ 20 s, silent, cover as first frame)
raw/ recordings, screenshots, contact sheets (not uploaded)
check-report.md build/SDK check results and what was fixed
listing.md category, tags, description, controls (from assets/listing-template.md)
form-answers.md every portal field and QA item with its answer and the reason
Tell the developer up front that this is the plan, and keep a short to-do list as you go.
Scripts (Node 18+, no npm install; FFmpeg for media)
All in scripts/ next to this file. Run them with node <skill-dir>/scripts/<name>.
check_build.mjs <build|zip> [--launch basic|full] [--json] — static scan: index.html at root,
sizes vs limits, file count, engine guess, SDK calls found, other portal SDKs/ad networks, external
login, links out, sitelock code, absolute paths, CDN fonts, fullscreen code, and more. Extracts a zip
if given one. Heuristic: "not found" means "look", not "proven missing".
serve.mjs <build> [--port 8787] [--out crazygames/raw] [--isolate] — serves the build plus
/__cg/stage.html?w=W&h=H (game in an iframe of exactly W×H) and saves uploads from the recorder.
recorder.js (loaded by the stage) — cg.info(), cg.start(name)/cg.stop(), cg.record({seconds,name}),
cg.shot(name); records the largest canvas and saves to --out.
media.mjs — probe, video (resize/crop or pad, trim ≤ 19.5 s, strip audio, --first-frame cover),
cover (crop to size, optional --logo), zones (draws the label zone for review), sheet
(contact sheet to review a video without watching it).
If FFmpeg is missing, tell the developer how to install it (winget/brew/apt) and continue with the
non-media steps meanwhile.
Workflow
1. Understand the situation (ask only what you can't find)
Find the build (a dist/, build/, Unity/Godot export, or a zip) and figure out:
- Basic or Full launch? Default: Basic for a game not yet on CrazyGames. Full only after an invitation.
- Is the build CrazyGames-specific? If the same build also targets other portals, the CrazyGames upload
must not contain their SDKs or ads — look for a per-portal build mode before changing code.
- Mobile support, orientation, multiplayer, accounts, how progress is saved.
If there is no build at all, help produce one first (the engine's web export /
npm run build).
2. Check, then fix
Run check_build.mjs and read references/requirements.md for anything it flags. Then:
- Errors block the submission: fix them (or show the developer the exact change if the code isn't
yours to edit — e.g. a Unity project you can't build).
references/sdk.md has fix recipes:
loading/gameplay events, mute, ads that cannot freeze the game, Data-module saves with migration.
- Warnings usually matter: explain each in one line and fix or justify it.
- Rebuild and re-run the check after changes. Put the final report and the fixes in
check-report.md.
Why the strictness: reviewers reject "without feedback" for some of these (external ads, ads that break
with ads disabled), and a rejection costs weeks.
3. Prepare the upload folder
Copy the final build into crazygames/build/ with index.html at its top (no wrapper folder, no
source maps, no OS junk). The portal refuses .zip files — the developer uploads this folder with
Select folder (or drags its contents).
4. Run it and play it
Start serve.mjs and open the game in a browser (browser automation if you have it). Watch the
console for errors, play a few minutes: start, win, lose, menus, mute. With the SDK, localhost runs it
in local mode, where ads appear as overlay text. Note anything a reviewer would hit; it goes into the
report. The real test is the portal's QA preview later — the developer must also try it on a phone
through the QR code there.
5. Covers and videos
Read references/media.md before starting — it has the specs, the capture options and the review
checklist. In short:
- Record each orientation at its real size (
stage.html?w=1920&h=1080, then ?w=1080&h=1620), with the
tab visible, in a clean state (English, no ads/debug UI, a good-looking level), more than 20 s.
- Make the covers first (key art > generated art > clean in-game frames with the logo), check them with
media.mjs zones, then build the videos with --first-frame pointing at the matching cover.
- Look at the results (open the images and the contact sheets) before calling them done.
If you can't play the game well enough for a good video, say so and ask the developer for a screen
recording — then process it with
media.mjs video.
6. Listing text
Fill assets/listing-template.md into crazygames/listing.md: category, up to 5 tags, a description
(hook → features → feel, plain text, ~80–160 words, concrete, no hype or keyword stuffing) and controls
(one line per input, desktop and mobile). Base it on what the game actually contains — open the code or
play it; never invent features. The "Which tools did you use?" field is about how the game was made:
ask the developer, don't guess.
7. Form answers
Write crazygames/form-answers.md from references/form.md, field by field, each with the answer and
the reason, citing the check report. For QA checklist items you could not verify yourself (phone test,
fullscreen, the preview's Warnings tab), mark them "verify in the preview" with what to look for — the
developer signs a statement that the answers are true, so never mark an unverified item as passing.
8. Hand over
Finish with a short message in the developer's language:
- what is ready and where (the folder tree), and what was fixed in the game;
- the remaining manual steps in order (billing, upload folder, play the preview + QR, paste listing,
upload covers/videos, submit);
- what happens next: review time is not published (days to a few weeks), Basic launch runs 7–21 days
and is judged on playtime, day-1 retention, 1-minute conversion and thumbnail CTR; ads and revenue
only start in Full launch; +50% revenue for 2 months of browser exclusivity after Full launch if the
game is not on other web portals.
Full launch (when invited, or when asked to prepare it)
Re-run the check with --launch full and work through the Full column of references/requirements.md:
gameplayStart/Stop at every break, ads only at natural breaks through the SDK (midgame ≥ ~3 min apart,
rewarded optional with a video icon and a non-ad alternative, pause + mute on adStarted), Data module
for progress, user module if there are accounts, works with AdBlock, gameplay within one click.
Then Submit new version in the portal with the Full switch.
Fixing a rejection
Ask for the exact message (screenshot). Map it to references/requirements.md / references/form.md,
fix, re-check, and explain what changed. For Basic-launch results below the benchmarks, look at the
weakest metric: CTR → cover and first video seconds; conversion → load time and the first minute;
playtime/retention → difficulty curve and goals.
Gotchas learned the hard way
.zip uploads are refused — upload the folder.
- Portrait video must be 2:3 (1080x1620); 1080x1920 is refused.
- Hidden browser tabs freeze requestAnimationFrame: recordings come out frozen. Keep the tab visible.
canvas.toDataURL() on WebGL is often blank: use cg.shot().
- Record in the store language (English) and with ad offers hidden — Basic launch has no ads, so a video
showing "watch an ad" misrepresents the game.
- With ads integrated, the game must keep working when every ad fails (
adsDisabled) — no freeze
between levels, no dead rewarded buttons. Test with the preview's "Throw SDK Error".
- The Data module only saves if "save progress with the Data Module" is picked in the form.
- MediaRecorder WebM files have no duration header;
media.mjs handles it.
1---2name: crazygames-launch3description: Take any HTML5 web game (Phaser, Pixi, Three.js, Unity WebGL, Godot, Construct, GameMaker, plain JS...) through a CrazyGames submission end to end. Checks the build and the CrazyGames SDK against the current rules, prepares the upload folder (the portal refuses zips), makes the three cover images and the two preview videos at the exact sizes the portal demands (1920x1080 and 2:3 1080x1620), writes the listing text, and gives the answer to every form and QA checklist field with the reason, for Basic and Full launch. Use it whenever someone wants to publish, submit, upload or launch a game on CrazyGames, prepare CrazyGames store assets (covers, thumbnails, preview video), integrate or check the CrazyGames SDK, fill the CrazyGames developer portal form or QA checklist, fix a CrazyGames rejection, or move a game from Basic to Full launch — even if they only say "put my game on CrazyGames".4metadata:5 source: https://skillmd.com/skills/thiagoferal-ia/crazygames-launch6---78# CrazyGames launch910You are guiding a game developer — possibly a beginner — from "I have a web game" to "submitted on11CrazyGames", and on to Full launch later. The portal punishes small mistakes (a zip upload, a 9:1612video, a wrong QA answer), and the developer usually discovers them one screen at a time. Your job is13to find all of them up front, fix what can be fixed, and hand over a folder plus an answer sheet that14make the portal a ten-minute task.1516Talk to the developer in their language. Write the store texts (listing, video/cover text) in English:17English is mandatory on CrazyGames and most players read it.1819## What you produce20A `crazygames/` folder next to the game project (or where the developer asks):21```22crazygames/23 build/ exact files to upload (index.html at the top)24 covers/ cover-landscape.jpg 1920x1080 · cover-portrait.jpg 800x1200 · cover-square.jpg 800x80025 videos/ landscape.mp4 1920x1080 · portrait.mp4 1080x1620 (≤ 20 s, silent, cover as first frame)26 raw/ recordings, screenshots, contact sheets (not uploaded)27 check-report.md build/SDK check results and what was fixed28 listing.md category, tags, description, controls (from assets/listing-template.md)29 form-answers.md every portal field and QA item with its answer and the reason30```31Tell the developer up front that this is the plan, and keep a short to-do list as you go.3233## Scripts (Node 18+, no npm install; FFmpeg for media)34All in `scripts/` next to this file. Run them with `node <skill-dir>/scripts/<name>`.35- `check_build.mjs <build|zip> [--launch basic|full] [--json]` — static scan: index.html at root,36 sizes vs limits, file count, engine guess, SDK calls found, other portal SDKs/ad networks, external37 login, links out, sitelock code, absolute paths, CDN fonts, fullscreen code, and more. Extracts a zip38 if given one. Heuristic: "not found" means "look", not "proven missing".39- `serve.mjs <build> [--port 8787] [--out crazygames/raw] [--isolate]` — serves the build plus40 `/__cg/stage.html?w=W&h=H` (game in an iframe of exactly W×H) and saves uploads from the recorder.41- `recorder.js` (loaded by the stage) — `cg.info()`, `cg.start(name)`/`cg.stop()`, `cg.record({seconds,name})`,42 `cg.shot(name)`; records the largest canvas and saves to `--out`.43- `media.mjs` — `probe`, `video` (resize/crop or pad, trim ≤ 19.5 s, strip audio, `--first-frame cover`),44 `cover` (crop to size, optional `--logo`), `zones` (draws the label zone for review), `sheet`45 (contact sheet to review a video without watching it).46If FFmpeg is missing, tell the developer how to install it (winget/brew/apt) and continue with the47non-media steps meanwhile.4849## Workflow5051### 1. Understand the situation (ask only what you can't find)52Find the build (a `dist/`, `build/`, Unity/Godot export, or a zip) and figure out:53- Basic or Full launch? Default: **Basic** for a game not yet on CrazyGames. Full only after an invitation.54- Is the build CrazyGames-specific? If the same build also targets other portals, the CrazyGames upload55 must not contain their SDKs or ads — look for a per-portal build mode before changing code.56- Mobile support, orientation, multiplayer, accounts, how progress is saved.57If there is no build at all, help produce one first (the engine's web export / `npm run build`).5859### 2. Check, then fix60Run `check_build.mjs` and read `references/requirements.md` for anything it flags. Then:61- **Errors** block the submission: fix them (or show the developer the exact change if the code isn't62 yours to edit — e.g. a Unity project you can't build). `references/sdk.md` has fix recipes:63 loading/gameplay events, mute, ads that cannot freeze the game, Data-module saves with migration.64- **Warnings** usually matter: explain each in one line and fix or justify it.65- Rebuild and re-run the check after changes. Put the final report and the fixes in `check-report.md`.66Why the strictness: reviewers reject "without feedback" for some of these (external ads, ads that break67with ads disabled), and a rejection costs weeks.6869### 3. Prepare the upload folder70Copy the final build into `crazygames/build/` with `index.html` at its top (no wrapper folder, no71source maps, no OS junk). The portal refuses `.zip` files — the developer uploads this folder with72*Select folder* (or drags its contents).7374### 4. Run it and play it75Start `serve.mjs` and open the game in a browser (browser automation if you have it). Watch the76console for errors, play a few minutes: start, win, lose, menus, mute. With the SDK, `localhost` runs it77in `local` mode, where ads appear as overlay text. Note anything a reviewer would hit; it goes into the78report. The real test is the portal's QA preview later — the developer must also try it on a phone79through the QR code there.8081### 5. Covers and videos82Read `references/media.md` before starting — it has the specs, the capture options and the review83checklist. In short:84- Record each orientation at its real size (`stage.html?w=1920&h=1080`, then `?w=1080&h=1620`), with the85 tab visible, in a clean state (English, no ads/debug UI, a good-looking level), more than 20 s.86- Make the covers first (key art > generated art > clean in-game frames with the logo), check them with87 `media.mjs zones`, then build the videos with `--first-frame` pointing at the matching cover.88- **Look at the results** (open the images and the contact sheets) before calling them done.89If you can't play the game well enough for a good video, say so and ask the developer for a screen90recording — then process it with `media.mjs video`.9192### 6. Listing text93Fill `assets/listing-template.md` into `crazygames/listing.md`: category, up to 5 tags, a description94(hook → features → feel, plain text, ~80–160 words, concrete, no hype or keyword stuffing) and controls95(one line per input, desktop and mobile). Base it on what the game actually contains — open the code or96play it; never invent features. The "Which tools did you use?" field is about how the game was made:97ask the developer, don't guess.9899### 7. Form answers100Write `crazygames/form-answers.md` from `references/form.md`, field by field, each with the answer and101the reason, citing the check report. For QA checklist items you could not verify yourself (phone test,102fullscreen, the preview's Warnings tab), mark them "verify in the preview" with what to look for — the103developer signs a statement that the answers are true, so never mark an unverified item as passing.104105### 8. Hand over106Finish with a short message in the developer's language:107- what is ready and where (the folder tree), and what was fixed in the game;108- the remaining manual steps in order (billing, upload folder, play the preview + QR, paste listing,109 upload covers/videos, submit);110- what happens next: review time is not published (days to a few weeks), Basic launch runs 7–21 days111 and is judged on playtime, day-1 retention, 1-minute conversion and thumbnail CTR; ads and revenue112 only start in Full launch; +50% revenue for 2 months of browser exclusivity after Full launch if the113 game is not on other web portals.114115## Full launch (when invited, or when asked to prepare it)116Re-run the check with `--launch full` and work through the Full column of `references/requirements.md`:117gameplayStart/Stop at every break, ads only at natural breaks through the SDK (midgame ≥ ~3 min apart,118rewarded optional with a video icon and a non-ad alternative, pause + mute on `adStarted`), Data module119for progress, user module if there are accounts, works with AdBlock, gameplay within one click.120Then *Submit new version* in the portal with the Full switch.121122## Fixing a rejection123Ask for the exact message (screenshot). Map it to `references/requirements.md` / `references/form.md`,124fix, re-check, and explain what changed. For Basic-launch results below the benchmarks, look at the125weakest metric: CTR → cover and first video seconds; conversion → load time and the first minute;126playtime/retention → difficulty curve and goals.127128## Gotchas learned the hard way129- `.zip` uploads are refused — upload the folder.130- Portrait video must be **2:3 (1080x1620)**; 1080x1920 is refused.131- Hidden browser tabs freeze requestAnimationFrame: recordings come out frozen. Keep the tab visible.132- `canvas.toDataURL()` on WebGL is often blank: use `cg.shot()`.133- Record in the store language (English) and with ad offers hidden — Basic launch has no ads, so a video134 showing "watch an ad" misrepresents the game.135- With ads integrated, the game must keep working when every ad fails (`adsDisabled`) — no freeze136 between levels, no dead rewarded buttons. Test with the preview's "Throw SDK Error".137- The Data module only saves if "save progress with the Data Module" is picked in the form.138- MediaRecorder WebM files have no duration header; `media.mjs` handles it.