April was about refinement and reliability.
After the infrastructure and integration breakthroughs of March, this month we focused on stability under the hood — cleaner code execution, quieter logs, smoother UI, and more transparent network monitoring.
Let’s look back at the updates that quietly made Balancy more predictable, traceable, and developer-friendly.
New CDN Callbacks — Real-Time Download Tracking
The highlight of April was the addition of CDN callbacks in Plugin 5.0.26, giving developers visibility into how network downloads progress in real time.
You can now subscribe to two new events:
Balancy.Callbacks.OnNetworkDownloadStarted += info =>
{
Debug.LogWarning(“Download started: ” + info.Url);
};
Balancy.Callbacks.OnNetworkDownloadFinished += info =>
{
Debug.LogWarning(“Info2: ” + info.Url + ” => ” + info.Success + ” => ” + info.TimeMs);
};
These callbacks make it easy to:
- Track file download start and finish events.
- Log duration, success states, and URLs.
- Build custom monitoring or debug tools for LiveOps content delivery.
For teams operating across multiple regions or CDNs, this feature brings clear visibility into what’s happening behind the scenes — without guesswork.
Plugin Fixes & Stability Improvements
The April plugin releases (5.0.24 → 5.0.26) focused on cleaning up edge cases and developer-experience details:
- Prevented unnecessary red logs on application quit, making console output cleaner.
- Fixed a scripting issue when comparing ProfileFullPath with null.
- Improved handling of document nodes in Visual Scripting when connecting them directly after selection.
Together, these fixes reduced noise in logs and eliminated several subtle inconsistencies that could appear in complex scripting setups.
Web Platform Polish
Dozens of minor improvements helped keep the editor stable and frustration-free:
- Fixed Select Menu clipping in expanded Condition modals.
- Resolved dropdown errors that sometimes appeared when opening input lists.
- Fixed menu overflow issues and document list rendering for events.
They’re the kind of fixes you only notice when they’re missing — and now they’re not.
Why It Matters
April’s changes were small in scope but big in impact: developers gained better visibility into network operations, cleaner debugging, and a smoother web interface.
With smoother performance and clearer logs, it’s now easier to stay focused on building LiveOps systems that run reliably.