We are about to start a Closed Beta of our game and plan to use the DEV Sandbox for internal testing and the STAGE Sandbox for Beta Testing with Players. In order to be able to test both of them separately we use Sandbox-specific access keys so we have 1 entry for the game for each Sandbox in our Libraries. The idea was to use one or the other depending on which one we want to test, but we encountered some issues.
After some investigation we found that both Sandboxes were overlapping because the default installation folder is the same (and the option to change the default folder is disabled for the Offer on STAGE, as if they are always meant to be the same across all Sandboxes). Is there a way to solve this problem? Maybe I’m approaching the setup in the wrong way. How can we have separate access to the DEV and STAGE Sandboxes in the Library with the builds not overwriting each other?
Thank you for reaching out for support! I understand that you’re trying to configure two separate betas: one using the Dev Sandbox while the other uses the Stage Sandbox. The problem you’re running into is that in order to push a build to either deployment, you essentially have to overwrite the previous build.
The best recommendation I can make is to set up a beta as a Demo Offer. This way, you can upload a separate artifact or binary for the Demo Offer from the Base Game, and you don’t risk overwriting one build for another. Here are a couple of articles on how to set up such an offer: