🔥 Hot Deploy Engine
Deploy any C# code update to 100% of players—without them downloading an app update
Hot Deploy Engine is your delivery system that ensures every improvement you make reaches all your players—including the 20-30% who normally never update their apps.
Not just server config tweaks. Real gameplay transformations:
New progression systems
Game mechanics & features
Bug fixes & balance changes
UI system changes
Core feature transformations
Hot Deploy is the delivery engine. Every solution you build, every problem you solve—it reaches 100% of your players without app store friction.
The Problem Hot Deploy Solves
When you ship traditional app updates:
20-30% of active players never download them
The rest take 2-3 weeks to adopt
Your retention features miss the at-risk players who need them most
Server configs reach everyone but only let you tweak parameters.
Hot Deploy changes this: Ship actual C# code—real gameplay transformations—to all players without download barriers.
How Hot Deploy Works
Hot Deploy Engine uses a system where your main app contains the "foundation" (Unity engine, core systems, UI frameworks), while your game logic runs as interpreted code that can be updated anytime.
What Hot Deploy Engine Does
Hot Deploy Engine is designed to feel invisible during development. You work exactly like you always have—no special tools, no different workflow, no learning curve.
Your existing setup just works.
Open VS Code, make changes, hit F5 to test in Unity Play Mode. Hot Deploy Engine runs alongside your normal development without getting in the way.
Your breakpoints work. Your console logs appear normally. Your performance profiler shows accurate data.
Debugging feels natural.
When something breaks, you get the same stack traces you're used to. Whether the error comes from hot code or native code, Unity's console shows you exactly where the problem is.
Your favorite debugging techniques—Debug.Log, breakpoints, Unity's profiler—all work identically.
No context switching.
You don't need to think "is this hot code or native code?" while developing. Write your Mono Behaviours, test them in Play Mode, debug issues the same way.
The only difference is that when you're ready to ship, you can push these changes to live games instantly.
Example Work Flow
Simple example: You want to change your shop price from $9.99 to $7.99 for a flash sale. With Hot Deploy Engine, you edit the code, click deploy, and players see the new price immediately—no app update required.
Open any script you wish to edit
Let's say your script is as below
/*
* Basic Unity shop manager with purchase button and $9.99 price display.
* Handles button clicks and logs purchase events.
*/
using UnityEngine;
using UnityEngine.UI;
public class ShopManager : MonoBehaviour
{
public Button purchaseButton;
public Text priceText;
void Start()
{
priceText.text = "$9.99";
purchaseButton.onClick.AddListener(OnPurchaseClick);
}
void OnPurchaseClick()
{
Debug.Log("Purchase initiated");
// Process purchase logic
}
}Make changes to any C# script in your project using your normal editor (VS Code, Visual Studio, etc.).
What you do: Normal coding workflow—edit, save, continue working
Edit Your Script
Hot Deploy Engine monitors your project and detects when scripts are modified.
/*
* Enhanced shop manager with discount features.
* Adds 20% off label, reduces price to $7.99, and includes analytics tracking.
*/
using UnityEngine;
using UnityEngine.UI;
public class ShopManager : MonoBehaviour
{
public Button purchaseButton;
public Text priceText;
public Text discountLabel;
void Start()
{
priceText.text = "$7.99"; // Limited time offer!
discountLabel.text = "20% OFF!";
discountLabel.gameObject.SetActive(true);
purchaseButton.onClick.AddListener(OnPurchaseClick);
}
void OnPurchaseClick()
{
Debug.Log("Discounted purchase initiated");
Analytics.TrackEvent("discount_purchase_clicked");
// Process discounted purchase logic
}
}What you see in VS Code:
File marked as "Modified" in your editor
Diff view showing exactly what changed (additions, modifications)
"Changes detected - ready to deploy" status
Setting Up Your Project for Hot Deploy
Working with Assets
GameObjects and Components: Your hot scripts can attach to any GameObject using AddComponent(). Scene objects work normally.
Prefabs: Keep prefabs with hot scripts in AssetBundles rather than scenes. This prevents Unity from breaking references during builds.
ScriptableObjects: Define ScriptableObjects in hot code and they work exactly like regular ones.
Things to remember
Memory and Performance Impact
App Size
Hot Deploy Engine adds ~175 KB to your app
Hot code reduces your app size since game logic is downloaded separately
If you have 1MB+ of hot code, using Hot Deploy will keep it smaller than bundling everything together in the base app
Runtime Memory
Each hot assembly uses ~5.5-6 times its file size in memory for metadata
Each thread running hot code uses ~1MB additional memory
Objects created by hot code use identical memory to native objects
Performance
Most game logic runs at 70%-90% of native speed
UI updates, gameplay systems, and business logic show no noticeable difference
Intensive computation (physics, rendering, audio) should stay in the base build
Multiple Assembly Support
Hot Deploy Engine supports organizing your hot code into multiple assemblies when your project grows complex. This is useful for large games where different teams work on separate systems (like UI, gameplay, and monetization) that need to update on different schedules.
Each assembly operates independently—you can update your UI code without touching gameplay systems, or push monetization changes without affecting core mechanics. This gives teams flexibility to ship features at their own pace.
Enterprise Features & Custom Development
These features aren't part of our standard product since every organization has different needs. We build them custom after understanding your specific requirements:
Build Pipeline Integration: We design CI/CD integrations that fit your existing workflow.
Deployment Management: We build hosting, versioning, and rollback systems based on your infrastructure needs.
Security & Sign-in: We create signing and encryption solutions that work with your security requirements.
Enterprise Deployment: We develop staged rollouts and multi-DLL systems tailored to your deployment processes.
Last updated