Common questions and solutions for issues you might run into.

Deploy fails with “game not found”#

Your API key might not have access to this game. Make sure:

• You’re logged in with the correct account (puls auth status)
• The slug you’re using matches exactly what’s in the dashboard

Deploy fails with “release limit reached”#

You have too many versions stored. You can keep up to 10 versions. Either:

• Delete an old version: puls releases delete my-game --version v0.1.0
• Use --prune to auto-remove the oldest: puls deploy my-game --prune

My game shows a blank page after deploy#

The index.html file might be missing or in the wrong place. Check that:

• There’s an index.html at the root of your build folder (not in a subfolder)
• Your build exported correctly from your game engine

My game loads but assets are broken#

Asset paths might be wrong. Make sure your game uses relative paths for all assets (images, scripts, sounds). Avoid absolute paths like /assets/... — use ./assets/... instead.

The CLI won’t install#

Try installing manually. If the install script doesn’t work on your system, you can build from source:

go install github.com/puls-games/puls-platform/cmd/puls@latest

This requires Go 1.22 or later.

I lost my API key#

Create a new one. API keys can’t be retrieved after creation. Go to Settings → API Keys in your dashboard, revoke the old key, and create a new one.

My game isn’t appearing in the catalog#

It may still be under review. New games go through a review process before appearing publicly. Check the status in your publisher dashboard.

Next: CLI Quick Reference