Hypercade Docs

Managing Games

3 min read

Managing Games

Adding your first game

In the Studio Portal, click “Add Game.” Fill in:

  • Game name - the title of your game (e.g., “Wandering Sorrow” or “Project Comet”)
  • Game repo URL - the full URL to your game’s Git repository
  • Game repo credentials - username and personal access token (or app password)
  • Engine - Unreal 5.x or Unity (2021.3+)

The repo URL and credentials are how Hypercade pulls your code for builds. We only use these to fetch code during the CI/CD pipeline. We never store your code or access it outside of builds.

For credentials:

  • GitHub - create a personal access token (Settings > Developer Settings > Personal Access Tokens) with repo scope
  • GitLab - create a project access token with api scope
  • Bitbucket - create an app password with repo scope
  • Perforce - provide a Perforce user and API token

Once you submit, Hypercade configures the CI/CD pipeline and triggers your first build. This takes 5-10 minutes. You’ll see the build appear in your game’s build history.

Viewing builds

Click on any game to see its build history. You’ll see:

  • Status - success, failure, or running
  • Build number - sequential identifier
  • Commit - which Git commit triggered the build
  • Branch - which branch was built
  • Duration - how long the build took
  • Triggered by - who pushed the code or what triggered it

Click a build to see details: logs, artifacts, test results, and any errors.

Build logs and troubleshooting

If a build fails, click into the build details to see the log. The log shows every step of the build process, from dependency fetching to compilation to artifact generation.

Most failures are caught early in the log. Look for the first red error message and scroll up a bit for context.

Common failures:

  • Missing dependencies - your .gitignore is too aggressive, or a dependency is stale
  • Compilation errors - you have uncommitted breaking changes
  • Test failures - something broke that your test suite caught
  • Asset processing - your asset pipeline failed (usually an asset corruption issue)

If you’re stuck, email the build log to hello@hypercade.io and we can help debug.

Branch builds

By default, Hypercade builds your main branch on every commit. You can also set up builds for feature branches and QA branches.

In your game’s settings, you can specify which branches trigger automatic builds. Common setup:

  • main - always build
  • release/* - build release candidates
  • qa - build for QA testing

Builds on secondary branches appear in the build history with their branch name.

Monitoring build health

The portal’s main view shows your latest build status at a glance. If it’s red, something broke. Click in and check the logs.

Enable push notifications to get alerts when builds fail. This helps catch breaking changes before the team notices.

Most studios aim for 95%+ build success rate. If you’re below 80%, there’s something systematically wrong. Reach out to us.

Changing repo credentials

If you rotate your Git credentials, update them in the game’s settings. Hypercade will use the new credentials for the next build.

Disabling a game

If you’re archiving a project, you can disable it. Disabled games don’t trigger builds, but their build history remains in the portal.

Questions?

See FAQ for common build questions. Email hello@hypercade.io if something isn’t working.

Backlinks