Skip to main content
Part of the multiplayer-publish skill. The skill links here when your agent needs the detail.
Reference for multiplayer-publish. The messages are the summer.games exporter’s own, word for word; %s stands for the value it names. Headless, the checks that run before exporting follow Cannot export project with preset "summer.games" due to configuration errors:, and server pack messages start with Server pack (<preset>):.

Result messages

Two warnings also matter: summer.build.json declares &lt;platform>, but this pack is not for it. … (tick that platform), and The pack starts &lt;scene>, but the Build's mainScene is &lt;scene>. Set application/run/main_scene, or its summer_client override, to the Build's scene.

Upload probe rejection codes

On failure the probe writes rejection.json next to the report instead:

Export errors and fixes

The exporter uses the source graph only to keep server files out of client.pck and to stop when the client needs one of them. It does not run the full source graph analyzer (step 4b of multiplayer-publish), the queue rules, or the other summer.build.json rules (multiplayer-project). Summer checks those when you upload, so follow them exactly.
Source: library/skills/multiplayer-publish/export-errors.md, rendered from summer-engine@4.3.0 on npm.