Publishing Projects

Development containers should be used to verify your game works as expected, with your team. You can generate a development container using the studio start command.

When you're happy with your changes, pushing them to your github repository will

This environment generally functions identically to the Production environment, with several key differences:

• There is an in-game override for free Crowns which can be used for testing in-game purchases
• The underlying hardware has additional limitations including lower network bandwidth and smaller compute resources
• Crown purchases to game modes (whether they are made with free or paid Crowns) are not paid out to developers, but can be manually refunded at any time
• Staging is intended for game development and testing, and is monitored regularly for misuse

When you push code changes to your project's GitHub repository, the Studio GitHub Publisher action will automatically build your project into a TAR file, upload it to the Studio, and upload your purchase definition files and game configuration to Mineplex. You can then launch your game mode within the Studio Staging environment identically to the Production environment, with the restrictions listed above.

Once your game is ready for publishing, you must initiate a Game Review. During a Game Review, we perform static analysis and gameplay testing on your code (through both manual and automated means) to ensure that your game complies with the Mineplex terms of service and Studio guidelines. Submissions are processed on a first-come, first-serve basis, and reviews may take up to one week. In the event that your game is rejected, you can make the necessary adjustments and re-submit as soon as you are ready for an additional review.

You can read more information about our review process on this handy information page.