Environments
Configure and manage deployment 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.
Think of it as: Different "servers" or "channels" for your game, each serving a specific purpose in your deployment pipeline.
Default Environments
Every application comes with two pre-configured environments:
🔬 Development
Private testing environment for internal use only. Perfect for debugging and testing new features.
🚀 Production
Live environment accessible to all players. Stable, tested builds only.
Environment Details
🔬 Development Environment
Purpose: Internal testing and development
Characteristics:
🔒 Private: Not accessible to end users
⚡ Fast: Upload and test immediately
🔄 Flexible: Unlimited uploads and changes
🐛 Debug: Test features before release
Use Cases:
Testing new game mechanics
Debugging crashes or bugs
Trying experimental features
Performance testing
Integration testing
Who Has Access?
✅ You (application owner)
✅ Team members with Developer role or higher
❌ End users / players
🚀 Production Environment
Purpose: Live releases for all players
Characteristics:
🌐 Public: Accessible to all launcher users
✅ Stable: Only thoroughly tested builds
📊 Monitored: Analytics and metrics tracked
🔄 Auto-Update: Players automatically notified
Use Cases:
Stable game releases
Official updates
Hotfixes for critical issues
New content deployments
Who Has Access?
✅ All players with your launcher
✅ Team members (for management)
Important: Always test in Development before deploying to Production!
Creating Custom Environments
Need more control? Create custom environments for specific purposes.
Common Custom Environments
🎯 Staging Environment
Pre-production environment for final testing
Use For:
Final QA testing
User acceptance testing (UAT)
Performance testing at scale
Load testing
Client review
Access:
QA team
Beta testers
Stakeholders
🧪 Beta Environment
Early access for select players
Use For:
Beta testing program
Early access releases
Community feedback
Bug hunting
Feature testing
Access:
Beta testers
Community moderators
Early supporters
✅ QA Environment
Dedicated testing environment
Use For:
Automated testing
Manual QA processes
Regression testing
Integration testing
Access:
QA team only
Automated test runners
🚨 Hotfix Environment
Emergency fixes
Use For:
Critical bug fixes
Game-breaking issues
Security patches
Access:
Senior developers
Admins only
Environment Configuration
Steps:
Navigate to Application
Go to your application
Click Settings tab
Open Environments
Find Environments section
Click + Add Environment
Configure Environment
Name: e.g., "Staging", "Beta", "QA"
Description: Purpose of this environment
Access Control: Public or Private
Save Configuration
Click Create
Environment is ready to use
Pro Tip: Use clear, descriptive names like "Beta-Testing" or "QA-Team" to avoid confusion.
Environment Properties
Configuration Options
Name
Environment identifier
Text (e.g., "Staging")
Description
Purpose and details
Text, supports markdown
Visibility
Who can access
Public / Private
Auto-Update
Notify launchers
Enabled / Disabled
Rollback
Allow version rollback
Enabled / Disabled
Access Control
Public Environment:
✅ Visible to all players
✅ Auto-update notifications sent
✅ Analytics tracked
✅ Listed in launcher
Private Environment:
✅ Hidden from public
✅ Access via invitation only
✅ Manual update checks
✅ Separate analytics
Environment Workflow
Promoting Builds Between Environments
Option 1: Manual Promotion
Steps:
Test in Development
Click Promote to [Environment]
Select target environment
Confirm promotion
Build copied to new environment
Option 2: Re-upload to Each Environment
Upload the same build to each environment separately:
Upload to Development → Test
Upload to Staging → QA Test
Upload to Production → Release
Flexibility: Choose the workflow that fits your team's process!
Environment Switching in Launcher
How Players Switch Environments
For public custom environments (like Beta), players can switch in the launcher:
Player Steps:
Open launcher settings (⚙️)
Find Environment dropdown
Select desired environment
Launcher downloads correct build
Beta Programs: Great way to reward early supporters with early access!
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:
✅ Verify correct environment selected
✅ Set build as "Active"
✅ Wait 1-2 minutes for propagation
✅ Check environment visibility settings
✅ Refresh launcher
Problem: Players can't switch to Beta/Staging
Solutions:
✅ Ensure environment is set to "Public"
✅ Verify builds exist in target environment
✅ Check player has necessary permissions
✅ Update launcher to latest version
Problem: Launcher downloads wrong environment build
Solutions:
✅ Check launcher environment setting
✅ Verify correct build is set as active
✅ Clear launcher cache
✅ Restart launcher completely
Environment Limits
By Subscription Plan
Free
2 (Dev + Prod)
Starter
10
Pro
10
Enterprise
Custom
Next Steps
Questions? Contact [email protected] or join our Discord community!
Last updated
Was this helpful?