Skip to content


Game builds can be a combination of one or more repositories containing files. In other words, the process to manage the files your users will need is: Create repositories => Upload files to repositories => Assemble a build using the repositories

Ultra lets you create different types of file repositories in which you’ll upload different parts of your game files:

  • Core game files: Contains the game executable and most of the game files.
  • Game DLC: additional content you want to distribute separately such as new maps, skins, music, etc.
  • Core demo game files: Contains all the files necessary to download and play a demo of your game.
  • Game language packs: files related to a specific language such as sounds, movies and textures you believe is unnecessary to send to users who don’t talk the language (Coming soon).
  • Game dedicated server: Files necessary to run a dedicated server of your game. This allows anyone, even if they don’t own the game, to download and run a dedicated server (Coming soon).

Assembling a Game Build

In order to assemble any kind of build, you will first need to have created a repository of the corresponding type, and uploaded files to it.

Before we can assemble a game build version, we first need to create a game build.

  1. Click on Create new game build
  2. Select the OS you want your game built on (Linux and MacOS support planned)
  3. Set the Internal Game build name.
  4. Select a repository and one of its versions.


  1. Specify the executable file to run the game, whether it’s for 32 bits, 64 bits, or both.


  1. If there are additional sets of files, such as DLCs, you can select which of them should be compatible with the build you're assemnbling.
  2. Create the game build.


Now you should be done with assembling the game build, you can determine whether this build version is a Master branch (intended for public release) or Beta branch (as mentioned before, this is still not available).

Congratulations! Your build is now created and ready to be delivered to users.

Important things to know

  • Whenever you run Filebeam and upload files, the repositories receiving files will have their repository version number incremented. At the same time, whenever you assemble a new version of your game build, its version number will increase. These increments are not linked, as illustrated in the following image image

  • On the topic of branches, below is an example of how they might be used. On the left, the build V1 is promoted as master branch of My Game Standard Edition, on the right the build V2 is promoted to the master branch. Beta branches coming Soonimage

  • Following the example above, as soon as build V2 is promoted as the master branch, all users who had V1 installed will see an update button on their library and will not be able to launch it until it's updated. In addition, anyone who installs the game will directly get V2 files from here on.

  • Including a DLC repository in a build doesn’t mean the buyer of the game will receive this DLC. It only means the files contained in the DLC repository version you associated with this build are compatible with it. The buyer will still have to separately buy the DLC to get it, and when they buy it, Ultra’s file distribution system will know what DLC repository version to download for this particular game build version.

  • In the future you’ll be able to “bundle” DLCs tokens with Game tokens, allowing you to sell your game containing DLCs. In the meantime, if you want gamers to get DLCs as part of the game they buy, upload DLC files in your core game files repository.

  • When you include a Language pack version in a build, the buyer of this build will have the ability to download it if they wish. If you want to separately sell a language pack you need to upload the language pack in a DLC repository and sell it as a DLC.