What goes in a game ZIP?
A Hugame package is a ZIP with your whole game inside. Your coding helper can make it for you.
1. Put three files at the top
index.html starts the game. hugame.json tells Hugame its title, rules, and controls. cover.png or cover.webp is the picture on the game card. Include exactly one cover.
2. Keep extra files in folders
Use assets for pictures and sounds, scripts for code, and styles for the look. All links must stay inside the package. Do not include secrets, hidden files, server programs, or node_modules.
3. Keep it small
The ZIP can be at most 50 MiB, with at most 500 files. Unpacked files can total 100 MiB, and each file can be at most 25 MiB. Smaller games load faster. The cover must be 16:10, at least 640 by 400 pixels, and no more than 2 MiB.
4. Use the shared rules
Your helper can read the full JSON Schema and the skill’s package reference. The CLI and server use the same file validator. Games run in a protected frame with no outside network access.
5. Choose the game’s shape
A tall game can use a tall frame; a wide game can use a wide one. Ask your helper to set display in hugame.json. Fixed games shrink to fit without stretching. Responsive games rearrange themselves. Keep every control inside the frame, with no scrollbars.
6. Remember progress and celebrate milestones
Want players to return to the same level or earn a badge for collecting 100 coins? Ask your helper to enable progress and achievements. Account progress follows signed-in players; guest progress stays in that browser. Private previews use practice data that resets when you restart. Keep save formats and achievement IDs compatible when updating your game.
Ready?
- My ZIP has the right top-level files.
- All assets are local.
- My package passes validation.