Before every release
Games with a server
- Your server starts its server scene. See check 1.
- Online join works with the version you release. See check 2.
Games with online play
- Players can find online play without changing a setting, or you decided on purpose that they can’t. See check 3.
- Online progress is saved by your server, not only on the player’s device. See check 4.
- Players can get back to the title from inside the game. See check 5.
Every game that uses Summer
- Your game doesn’t hard-code its Game ID. See check 6.
- You exported with a released Summer editor, and your scripts compile on the Summer that players get. See check 7.
- Your build includes the files and fonts the game uses. The title and menus are readable on every platform you ship. See check 8.
- You exported with the Summer version the Summer Games apps run. See check 9.
- A signed-in player keeps playing for 3 minutes on each Summer Games app, and stays signed in. See check 10.
The checks
Run the checks on the file you upload: your summer.games.zip. Export it
as usual, in the editor (Project → Export, the summer.games preset) or
with your agent. Use the path your export printed; build/my-game.summer.zip
below is an example. Then unpack it and name the Summer Engine executable,
once per terminal. Every check below uses both.
Run-Summer
starts it with --log-file, stops it after the given seconds, and each check
then searches that file.
A server pack you export on its own with your server preset is not the same
file. It can pass a check that the uploaded .zip fails.
1. Your server starts its server scene
Summer starts your game’s server with no scene named. The server pack’s own main scene decides what runs. Your server preset carries the custom featuresummer_authority, and project.godot sets that feature’s main scene to
your server scene:
project.godot
export_presets.cfg (your server preset)
summer_authority, the server starts your
players’ main scene instead, usually the title screen. That scene never
tells Summer the server is ready, so every online join fails.
Check it. Start the server from your .zip the way Summer does, with no
scene named:
Completed load for: 'res://…tscn' line. It
must be your server scene, such as res://authority/main.tscn. If it shows
your title or client scene, add summer_authority to the server preset’s
Custom Features and export again.
Local Play always starts your server scene by name, so a game can work
there and still fail this check.
2. Join online with the version you release
The check above runs on your computer. Players use a hosted server, so also test there: right after a new version goes live, open your game in a Summer Games app, join online and play until you’re in the game. Do it before you tell players about the update. If the join fails, see Players can’t join online.3. Players can find online play
A new player should reach online play without changing a setting. If online play is off by default, for example behind a grown-ups setting, make that a deliberate choice. Then join online yourself before every release, because no player will find it broken for you.4. Your server saves online progress
In online play, your server saves each player’s progress with player progress and loads it when they join. Progress kept only on the player’s device is lost when they reinstall or switch device, and players can edit it. To test, play online, earn something, leave, then join from another device.5. Players can get back to the title
Inside a game, players need a way back to the title screen, such as a pause menu or a Leave button, online and offline. Without one, the only way out is to close the app.6. Your game doesn’t hard-code its Game ID
Start Summer with no Game ID:.zip is
portable, so its summer.build.json has no gameId. If your code reads
gameId from that file and falls back to a made-up ID such as
"game.my-game", the hosted server refuses it with
game_identity_mismatch. Your server then stops before it is ready, and
players’ online joins fail. The Summer Games app refuses it the same way.
Check it. Search your project for Summer.initialize. Every call passes
no ID, or an ID your game received from Summer, never a fixed string or a
fallback. Then join online with the released version (check 2). Local Play
and a local run of server.pck don’t run under a hosted identity, so they
can’t catch this.
7. Export with a released Summer editor
Use the released Summer editor from the download page, not a development build. After you update Summer, export again before you upload. Your export records which Summer made it, and players’ apps run your game on the released Summer of that version. A development build can call itself a version that is already released while it has features that version lacks. Your scripts then use something that isn’t there on players’ devices. They fail to load, and the game opens to an empty window for every player. Summer doesn’t compile your scripts when you upload, so the upload still passes. Check it. Read which Summer made your.zip:
"export", summerVersion must be a released Summer version, and
engineSha must match the engineSha that Summer publishes for that version
at https://downloads.summer.games/engine-templates/<summerVersion>/manifest.json
(Summer 0.7.1 and later). If it differs, a development build made the export.
If that address has nothing for your version, update Summer and export again.
Then run your game on that released Summer and look for scripts that fail to
load:
8. Every file your game reads is in the pack
Summer packs your scenes, scripts and imported assets for you. A file that your game opens itself at run time, withFileAccess or another call that
reads a res:// path, is different. If Summer doesn’t import the file, for
example a .bin, .json or .txt, it goes into the pack only when your
export preset’s Resources → Filters to export non-resource files/folders
matches it. Each preset has its own filters, so set them on the
summer.games preset that makes your .zip. A file the filters leave out
is not an export error: your game just can’t find it on players’ devices.
Fonts are where this shows first. On iPhone your game can’t use the
phone’s own fonts, so a SystemFont draws every letter as a box there. On
your Mac or PC the same game looks fine, because SystemFont finds a font
on your computer.
Check it.
-
Search your scripts for files they read by path:
Note every
res://file or folder those lines read. Skipuser://paths; those are saves. -
List what is in your pack. Save this script outside your project, for
example as
list_pack.gdin your home folder:Then run it on thelist_pack.gdclient.pckfrom your.zip:Every file from step 1 must have its ownPACK res://…line. If one is missing, add it to the summer.games preset’s non-resource filter, for examplefonts/*.bin, export again and check again. -
Check the fonts used by your theme, individual labels, rich text and
scripts. Include bold and italic faces and any fallback used for another
language or symbol. Import custom fonts such as
.ttfor.otfinto the game and reference them from the UI. If your code picks a font by name at run time, include its resource in the client export preset. For an imported font, pass its original path to the listing script after--, for example-- res://fonts/Title.ttf. View the full output and look for aFONTline for each face. Summer may store the imported data under a different name in the pack. - Before release, open that build on each platform you ship, on a device or clean environment without your development fonts. Read the title, menu buttons and a sample from each writing system your game supports. Check the actual Summer Games app for iPhone releases. Save a screenshot or note the build, platform and text you read. If a letter appears as a box, fix the font and repeat the check on the new export.
9. Export with the Summer version the apps run
The Summer Games apps for iPhone and Android carry Summer inside them. An app runs a game exported with the same Summer version line, the first two numbers such as0.7, at the app’s patch number or lower. A game exported
with 0.6.x doesn’t start in an app that carries 0.7, and players see
The game could not start. The desktop app gets the right Summer for each
game, so your game can work on Mac and Windows and still fail on every
phone.
Check it. Read which Summer made your .zip, as in check 7:
"export", the first two numbers of summerVersion must match the
current Summer release on the
download page. When Summer moves to a
new version line, for example from 0.6 to 0.7, update Summer, export your
game again, upload it as a new version and take it live. Then open it on a
phone, as in check 2.
10. Play for three minutes while signed in
While your game runs, it uses Summer services for the signed-in player, such as analytics, player progress and the store. A short test can end before the first of those calls. Play long enough to reach them. Check it. Sign in to a Summer Games app on a phone, open the version you release and play it for at least 3 minutes. Do something that sends one of your analytics events. The game must not close, and you must still be signed in afterwards. Do this in each Summer Games app your game targets. If the game closes or you are signed out, the fault is Summer’s, not your game’s. See The game closes after about a minute.Troubleshooting
Players can’t join online
Every online join waits and then fails withworld_start_timeout, while the
game works in Local Play.
Most likely causes:
- Your server pack starts the wrong scene. Run
check 1. If it loads your title or
client scene, add
summer_authorityto your server preset’s Custom Features, export a new version, upload it and take it live. - Your game passes a fixed Game ID. Run
check 6. Call
Summer.initialize()with no ID, export a new version, upload it and take it live.
Game opens to a blank window
Your game opens to an empty or black window for every player, while it works in your editor. Running your.zip as in
check 7 prints lines such as
Parse Error: Static function "…" not found and
Failed to load script "res://…".
Most likely cause: a development build of Summer exported the game, and
your scripts use something the released version doesn’t have. Re-export with
the current Summer release from the
download page, upload the new version
and take it live. Run check 7 on the new .zip before you upload it.
Text shows as boxes in the exported game
A box with digits inside is a missing character. This can happen on any platform when a font is missing from the export, a label uses a font installed only on your computer, or the font lacks that character. Check the face assigned to the affected label. Bundle that face and a fallback that covers the affected text, then export again and read the same label in the player build. Check 8The game could not start
The Summer Games app on iPhone or Android says The game could not start, while the game works on desktop. Your.zip most likely comes from a Summer
version line the app doesn’t carry. Run
check 9: update Summer,
export again, upload the new version and take it live. If the versions match
and it still fails, ask on Discord with
your game’s name and the time you tried.
The game closes after about a minute
A Summer Games app closes your game after 20 to 60 seconds of play with Play paused or That link can’t be opened, and the player finds they are signed out. This happens when a Summer service refuses the player’s sign-in while your game plays. It is Summer’s fault, and you don’t need to change your game. Report it on Discord with your game’s name, the app and the time it happened.Ask your agent
Check my game is ready to release. Your agent runs every check on this page and tells you what fails.
Does this not help you? Reach out on Discord!

