Manage games

The Developer Console allows you to create and manage your Jest games.

After creating a game, you can control how it appears on the platform, upload and manage builds, configure in-game products, manage images, and access analytics and security credentials.

Create a game

To create a new game:

1. Open the Jest Developer Console and log in.
2. Select Games from the left-hand navigation and click Create New Game.
3. Enter a Game Name and a Game Slug. The slug determines your game’s URL: https://jest.com/g/<game-slug>. The game slug cannot be changed after creation.
4. (Optional) Provide additional properties:
   • Description – A short summary of your game.
   • Card Color – The color of your game card in the Explore and Library sections.
5. Set the Visibility:
   • Hidden – The game is not visible to users.
   • Visible – The game can appear on the platform.
6. Click Create Game.

Create Game screen in the Jest Developer Console

Configuring game properties

You can edit your game’s properties at any time from the Overview tab.

These properties determine how your game appears across the Jest platform. Providing clear descriptions, consistent branding, and strong visuals helps present your game professionally, improves discoverability, and builds trust with players.

Available properties include:

• Game name
• Description – Displayed in the Explore section
• Logo – A square image that represents your game across the platform.
• Hero image – A wide banner image that represents the game on the platform.
• Support email – The address that receives player support requests for your game. See Support email below.
• Loading Screen Mode – Controls the loading overlay shown when players enter your game:
  • Auto (default) – A brief loading animation is shown and automatically dismissed.
  • Manual – The overlay is shown automatically but your game controls the progress and dismissal via the SDK. See the Loading Screen SDK documentation for integration details.
  • Off – No loading overlay is shown.

Support email

A support email is required when publishing a game. Players can contact your studio by tapping Contact Support on the game info popup, which opens their mail client with a message pre-addressed to this address.

The Contact Support action on the game info popup

The subject line is pre-populated with the game name and the player's ID for your game, for example:

Support Request - Dragon Candy (Ref: c0fe0ac8-5e2b-418d-abd3-d87a316d9328)

The value after Ref: is the player's playerId for your game. Paste it into the Players tab to inspect that player's current game state when responding to the request.

Submit a game for review

Before your game can go live on the Jest platform, it must be submitted for review and approved.

Before you submit

You must upload and activate at least one build in the Versions tab before submitting your game for review.

Submit for review

1. Navigate to Games > Manage Game.
2. Open the Overview tab.
3. Click Edit.
4. Scroll to the bottom of the page.
5. Select Submit for Review.

Once submitted, the game status changes to In Review.

Review outcome

After review:

• Approved – Your game goes live on the Jest platform.
• Rejected – Your game remains unpublished, and a reason for the decision is provided.

A game is displayed on the Jest platform only when it is both approved and marked as Public. If your game is approved but still set to Hidden, it will not appear on the platform.

If rejected, you can make the necessary updates and resubmit for review.

Updating a live game

After your game has been approved and is live, future updates (such as new builds or game property changes) are subject to ongoing review.

These reviews are non-blocking - you can continue updating and deploying builds without waiting for additional approval.

Events

The Events tab provides visibility into moderation actions and runtime errors related to your game.

This section helps you diagnose issues that may affect notifications or user-facing behavior.

Moderation

The Moderation view lists notifications that were blocked due to content policy violations.

A common example is user-supplied text (such as a username) that does not comply with Jest's acceptable use policy. If a notification includes non-compliant content, it may be prevented from being delivered.

Use this section to:

• Identify blocked notifications
• Understand why they were blocked
• Adjust your content or validation logic accordingly

Errors

The Errors view lists error-related events for your game.

Errors may appear at the notification level when validating the imageReference parameter. Possible error types include:

• The provided reference does not exist.
• The referenced image has not passed review.
• The referenced image has been archived.

Review these errors to diagnose issues preventing notifications from being scheduled successfully.

Secrets

The Secrets tab provides access to your game’s credentials:

• Shared Secret – Used to authenticate your game server with the Jest API and verify requests. You can regenerate this value if needed.
• Upload Token – Used to upload builds programmatically via the upload API.

Keep these credentials secure and never expose them in client-side code.

Players

The Players tab lets you look up an individual player's state by their player ID. This is useful for customer support, allowing you to inspect a player's current game data when troubleshooting issues.

To look up a player:

1. Navigate to Games > Manage Game > Players.
2. Enter the player's Player ID (UUID).
3. Click Look Up.

If the player exists for this game, their details and full game state JSON are displayed. You can copy the JSON to your clipboard for further analysis.

Access to this tab requires at least a Viewer role on the game's team.

Analytics

The Analytics tab provides high-level performance insights for your game. To access it, navigate to Games > Manage Game > Analytics.

You can view metrics such as daily active users (DAU), new users, and retention.