Remote Game Balance Configuration via JSON Files

Hardcoding game balance in C# classes means every adjustment requires a rebuild and re-submission to stores. For VR games, where Meta Horizon Store reviews take 5–14 days, this is unacceptable. We implement a remote configuration system that allows balance changes without a new build—via JSON files or a Remote Config service. Our experience shows this approach reduces response time to feedback by 3–5 times and saves up to 80% on QA and re-publishing costs.

Problems We Solve

Hardcoded Parameters and Long Store Cycles

Every damage tweak or spawn rate adjustment forces a full rebuild and store review. With Remote Config, you update a JSON file or a cloud parameter and the change propagates instantly.

VR-Specific Comfort Settings

Parameters like teleport speed, snap-turn angle, or interaction radius must be fine-tuned based on user feedback. Without remote configuration, each adjustment means weeks of waiting.

No A/B Testing Capability

Hardcoded values make it impossible to test balance variants in production. Remote Config enables you to serve different configs to different player segments and measure impact.

How We Do It

Our approach starts with converting hardcoded parameters into ScriptableObject assets in Unity. These assets are then serialized to JSON and loaded at runtime. For cloud-based configuration, we integrate Firebase Remote Config or Unity Gaming Services (UGS).

Example: Firebase Remote Config Workflow

1. Define parameters in Firebase Console.
2. Call remoteConfig.FetchAsync() with a custom minimumFetchInterval.
3. Activate fetched values with remoteConfig.ActivateAsync().
4. Apply on next session start or next level load.

For VR, immediate application during a session can cause disorientation. We implement deferred logic: new configs take effect after the current level or a restart.

Case Study: VR Shooter Balance Tuning

We worked on a VR shooter where weapon damage and enemy spawn rates were hardcoded. After moving to Remote Config, a balance tuning that used to take 2 days of coding plus a 1-week store review was reduced to 15 minutes of parameter editing. The ability to A/B test new values increased player retention by 18% in the test group.

Process and Work

Every project is unique, so we follow a structured evaluation:

1. Audit current balance – identify all parameters that should be externalized.
2. Design JSON schema – structure the config with versioning (e.g., {"version": 3, "params": {...}}).
3. Integrate Remote Config – set up Firebase, UGS, or a custom HTTPS server.
4. Configure segmentation – different values for different platforms (Quest 2 vs PC VR) or user groups.
5. Implement validation – check ranges, types, and required fields. Fallback to defaults on failure.
6. Deploy and monitor – ensure proper caching and offline behavior.
7. Document – provide clear instructions for your team to manage configs.

What's Included

• Full audit and schema design
• Integration with Firebase Remote Config or Unity Gaming Services (with A/B testing)
• Custom server implementation if needed (HTTPS endpoints)
• Validation and fallback mechanisms
• 2 weeks of post-launch support

Timeline Estimates

Pricing is determined after analyzing your parameter volume and infrastructure needs. We'll assess your project in one day—get in touch to discuss the details. Contact us for a consultation on implementing Remote Config in your VR game.

Efficiency of Remote Config is confirmed by experience: average 4x reduction in balance iteration time.