# Environments Learn how to use environments to safely test and deploy your game builds across different stages. *** ## What are Environments? **Environments** are isolated deployment stages that allow you to test builds before releasing them to all players. {% hint style="info" %} **Think of it as**: Different "servers" or "channels" for your game, each serving a specific purpose in your deployment pipeline. {% endhint %} *** {% hint style="success" %} **Beta Programs**: Great way to reward early supporters with early access! {% endhint %} ### How Players Switch Environments For **public** custom environments (like Staging[^1], Closed-Beta), players can switch in the launcher:

Player switching environment in Launcher Desktop

## Default Environments

Every application comes with two pre-configured environments: **Production** * Live environment accessible to all players. Stable, tested builds only. **Staging** * Private testing environment for internal use only. Perfect for debugging and testing new features. *** ## Creating Custom Environments {% hint style="success" %} **Pro Tip**: Use clear, descriptive alias like "Beta-Testing" or "QA-Team" to avoid confusion. {% endhint %} Need more control? Create custom environments for specific purposes. **Example:** "Closed Beta" hidden environment with Access Code

*** ## Best Practices ### ✅ Recommended Workflow **Professional Pipeline** **1. Development** → Internal testing, rapid iteration **2. Staging** → QA testing, performance checks **3. Beta (optional)** → Community testing, feedback **4. Production** → Stable release to all players *** ### 🎯 Do's * ✅ Always test in Dev before Staging * ✅ Use Staging for final QA * ✅ Keep Production stable * ✅ Document environment purpose * ✅ Use clear naming conventions * ✅ Monitor each environment separately *** ### ❌ Don'ts * ❌ Skip testing in Dev * ❌ Upload untested builds to Production * ❌ Mix environment purposes * ❌ Give Production access to everyone * ❌ Forget to update environment docs * ❌ Create too many environments (keep it simple) *** ## Troubleshooting **Problem**: Build uploaded but not showing in environment **Solutions:** * ✅ Make sure the Build is "Completed" * ✅ Refresh the page **Problem**: Players can't switch to Beta/Staging **Solutions:** * ✅ Ensure environment is not **Hidden** * ✅ If the environment is **Hidden**, user needs to unlock the environment with the access code **Problem**: Launcher downloads wrong build **Solutions:** * ✅ Check launcher environment setting * ✅ Verify correct build is set as active * ✅ Click refresh button to fetch the latest changes * ✅ Restart launcher completely *** ## Next Steps


📦 Manage Builds	Upload builds to environments	https://github.com/GameLauncherCloud/GameLauncherCloud-Gitbook/blob/main/docs/apps/broken-reference/README.md
⚙️ App Settings	Configure application settings	/pages/R9GcUrYO2GcAmi9barJy
🚀 Create Launcher	Build your custom launcher	/pages/1cNgvv5uy79qCeQbdGPa

*** {% hint style="success" %} **Questions?** Contact or join our [Discord community](https://discord.com/invite/FpWvUQ2CJP)! {% endhint %} [^1]: Staging is an environment to test your game before placing it in your public Production environment. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://gamelauncher.cloud/help/applications/environments.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.