Skip to content

Troubleshooting

If your game sent a score, an unlock or a save and something went wrong, start with the code in the gm-ack reply: every message of a known type is answered, and the code is usually the whole diagnosis. The codes are in gm-ack.

SymptomGo to
My game was rejectedPublishing: submitting
My game left the review queuePublishing: builds
Tips are switched on and no tip button showsPublishing: money
A script or stylesheet is refused, with a MIME type error in the consolePublishing: the build, file extensions
A file 404sRuntime: where your build lives, and zero-byte files in the build
A request from my game is blockedRuntime: network

My score is not on the leaderboard

Read the ack first. It names the reason, and the reasons are not interchangeable.

  • UNAUTHENTICATED: the player is signed out. Nothing was stored and there is nothing to recover later. Ask for sign-in before a run starts.
  • VALIDATION_ERROR: the score is not an integer of zero or more, or metadata is nested or over a limit. One bad key fails the whole submission. Nothing but a malformed submission gets this code, so read your own payload.
  • RATE_LIMITED: the score was refused and not stored. Submit once per run, when the run ends, behind a flag your game loop cannot clear twice. Scores accepted earlier are untouched. Never resubmit in a loop.
  • SCORE_ABOVE_MAXIMUM: the score is over the maximum on the game's Scores tab, and was not stored. Check the number your game sends, or raise or remove the maximum. Owner Preview refuses it the same way.
  • NETWORK_ERROR and INTERNAL_ERROR: neither proves that nothing was stored. Treat them as unknown, not as failed: a resubmitted run is a second score.

If the ack said ok: true and the score is not shown: the leaderboard has one row per player, their personal best, and a tie does not replace it, so a second score lower than the first never appears. It counts only live games, and a new score can take a few minutes to show.

My unlock does nothing

Read the ack. Three codes, three unrelated problems.

  • UNAUTHENTICATED: the player is signed out. A signed-out unlock is never NOT_FOUND. If you are looking at a NOT_FOUND, sign-in is not your problem.
  • RATE_LIMITED: too many attempts. Fire an unlock when its condition is met, never on a timer or every frame. Re-firing a badge the player already holds counts as an attempt.
  • NOT_FOUND: one code for several causes, deliberately. Work through the list below.

When an unlock comes back NOT_FOUND, it is one of these:

  1. The reference does not resolve. Copy the exact call from the game's Achievements tab. The slug is stable and safe to hard-code; editing a title never changes it. The ULID also resolves.
  2. The achievement is not a manual one. Score and play-count achievements are awarded by the platform and cannot be unlocked from inside a game.
  3. It is not published yet and you are neither its author nor the owner of the game. A draft is testable by you and invisible to everyone else.
  4. It is retired. Nobody can unlock it, including you.
  5. The player has not started the game recently. Preview does not count. A draft you authored is exempt, but a published achievement tested from Preview needs you to have played the public game page first.

My upload was refused

The archive is checked before anything is stored, and every refusal carries a stable code you can switch on. The limits are in Publishing.

CodeStatusCause
UPLOAD_INVALID_TYPE400The filename does not end in .zip, in lower case.
UPLOAD_TOO_LARGE413The archive is over 30MB compressed, or extracts to more than 200MB.
UPLOAD_INVALID_CONTENT422The archive would not extract, holds more than 2000 files, has no index.html at its root, or holds a path containing .. or a leading slash.
VALIDATION_ERROR422The gameId is missing from the query string, or is not a 26-character id.
NOT_FOUND404The game is not one of yours. Another developer's game answers 404, never 403.
FORBIDDEN403The game is suspended or unpublished, or the token does not carry the builds:write scope.
UPLOAD_FAILED500Storage refused a write. No build is recorded: upload again.

index.html must sit at the archive root, spelled exactly that way. Index.html, or an archive whose files sit one folder down, fails the same check with the same message, so the message cannot tell you which of the two mistakes you made: check both.

My CI upload fails

Two failures a script sees are plain text, not JSON, so a script that parses every non-200 body as { success, error, code } breaks on exactly the two it most needs to read. Switch on the status first, then the code. The upload codes are in the table above.

StatusCodeCause
403plain text, no codeAn upload (a multipart POST) whose token is missing, malformed, expired or revoked, or whose account is suspended. It is refused before the route runs.
429plain text, no codeThe token's own rate limit. Pace the loop.
401UNAUTHENTICATEDA JSON request or an export sent with no token.
401UNAUTHORIZEDA JSON request or an export whose token is expired, revoked or unrecognised. The message says which of expired and revoked.
403FORBIDDENThe token is valid but lacks the scope the route needs, and the message names it; or the account is suspended.
404NOT_FOUNDThe game belongs to another developer, or does not exist.
Reading the status before the body, in CI
# Read the status first, then the body. A bad token and a rate limit both
# answer plain text, not JSON.
status=$(curl -sS -o response.json -w '%{http_code}' \
  -H "Authorization: Bearer $GAMEMOOR_TOKEN" \
  -F "file=@build.zip" \
  "https://gamemoor.com/api/developer/upload-game?gameId=$GAME_ID")

case "$status" in
  200) # { "success": true, "data": { ... } }. Read data.activated and
       # data.withdrawnFromReview before calling this a successful deploy.
       ;;
  403) # JSON with code FORBIDDEN: the token lacks builds:write.
       # Plain text: the token is missing, expired or revoked, or the account is suspended.
       cat response.json; exit 1 ;;
  429) echo "rate limited: back off, then retry"; exit 1 ;;
  *)   cat response.json; exit 1 ;;
esac

A pipeline that stopped on a particular day with nothing else changed: check the token's expiry first. The limits on tokens are in Scripts and CI.