Common questions and solutions for issues you might run into.

CLI guidance on this page is for invited publishers.

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”#

Your game already has the maximum number of releases and there may be no inactive release to remove. Keep up to 10 releases. Delete an inactive one with puls releases delete my-game v0.1.0, then try again. --prune removes the oldest inactive release before deployment when one exists.

My hosted game shows a blank page#

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

• Your exported game includes an index.html entry point
• Your build exported correctly from your game engine
• You published the staged release with puls releases publish <slug> <version>

My game loads but assets are broken#

Asset paths might be wrong. Check the browser’s network errors and confirm that image, script, and sound URLs point to files included in your build. Relative paths such as ./assets/image.png are a portable choice.

I need the CLI#

CLI access is currently invite only. Contact Puls for access and installation instructions. There is no public installer yet.

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: Your Game Profile