Uploading your Game Build
Builds in Elixir Platform are used for version control. Every new Build represents a new version of the Game. Creating a build is a simple task:
Choose your own version naming
Have control of which build you have active to perform new releases and rollbacks
Do not forget to activate the Build once everything is ready. Also, you can always de-activate it when you want to close the access to the game. Or perform a roll-back by activating older builds just by using the toggles:
Now that you have created a Game Build. Let upload the file so you can start playing it. For this you will need to configure the Depot: A configuration file that will include information about the Game File and how to execute it.
Installation Path: Do not modify this path. We are planning on removing it from here for the next version.
Launch Command: It should follow a structure like "<InstallationPath>/<route to the executable file>".
See Recommendations
The Master Branch is used for public release. Once a new version of the game has been approved and a new release is on the way. Users must create a new build on Master and upload there the Game Build in a new Depot.
This branch is used for closed beta access using Beta Codes. Publishers can upload every new version of the game to test it internally or with the community before making it public.
This branch is also used for the pre-alpha versions when a game is not released yet.
Upload your build for internal testing. Check out the SDK integration and make the last adjustments before releasing the game with your audience.
Only whitelisted developer accounts will have access to this build.
Every new Build represents a new version of the Game. So every time that a publisher wants to release a new version of the game, it is needed to create a new build, and then activate it. When users launch Elixir, it will detect a new version is available and will prompt users to download the update before playing.