Unreal Polish and Lighter Cloud Save: horizOn This Week
In a nutshell
Unreal SDK 1.10.5 cleans up Windows JSON and Fab packages. Server 1.75 lightens Cloud Save, and public dashboard pages survive session expiry.
Last Thursday horizOn shipped inventory, currencies, achievements, friends, groups, chat and turn-based matches in one go. This week we did the opposite of that. No new Unity or Godot build, no Simple Server bump, no MCP update. We spent the days on Unreal packaging, a few server hot paths and a dashboard detail that only shows up when a session expires at the wrong moment.
Here is what changed between October 29 and November 4.
Unreal SDK 1.10.5: Cleaner Windows Builds and Cleaner Fab Packages
If you develop with the Unreal SDK on Windows, two small fixes landed this week.
In 1.10.5, JSON outputs are initialized properly and no longer collide with inherited names. That class of bug is easy to miss in a sample project and painful once your game code starts producing real payloads. Update if you saw odd JSON behavior or name conflicts after last week's feature release.
In 1.10.4, Fab submission packages stop bundling the repository license terms. When you prepare a package for Fab, the archive should contain what Fab expects, not the extra license files that belong to the open repository. If you were stripping those by hand, you can stop.
Unity stays on 1.12, Godot on 1.11, Simple Server on 1.6 and MCP on 1.9. There is nothing to reinstall there.
Best practices after a big Unreal feature drop
- Update before you chase last week's samples. The new inventory, match and chat samples from 1.10 assume a clean plugin. Start from 1.10.5.
- Re-export Fab packages once. Old archives still contain the license terms. Build a fresh one after 1.10.4 or later.
- Keep one Windows test project. JSON init bugs tend to show up only under editor play with real data, not in a CI Linux cook.
Server 1.75.7 to 1.75.9: Less Work Per Request
The server line moved from 1.75.6 to 1.75.9. None of these releases add a new public API. They cut work that every live game pays for on every call.
Cloud Save is the clearest example. When a session has already verified the player, the server used to read the player record again before serving the save. That second read is gone. Anonymous signup no longer checks whether a token already exists on the way in. The in-game news list is cached per pod for thirty seconds, so a busy title does not hit the database for every client that opens the news panel.
You do not change your client code for any of this. The same Cloud Save, signup and news calls just do less on the backend.
Why these cuts matter more after a feature week
Last week's release added inventory, player values, achievements, friends, groups, chat and turn-based matches. Every one of those features means more reads and writes per online player. A quiet performance pass right after a feature drop is how you keep the new surface usable under real traffic instead of discovering the cost in production.
If you build the same stack yourself, you would be wiring session-aware short circuits, per-pod caches and signup path audits by hand. With horizOn those land in the hosted server without a redeploy on your side.
Practical checks for your own project
- Watch Cloud Save latency after you update. If you log round-trip times, you should see fewer spikes on verified sessions.
- Keep anonymous signup for guests only. Faster signup is not a reason to skip linking a real account before purchases or inventory that must survive a device wipe.
- Treat news as eventually consistent. A thirty-second cache means a freshly published news item can take a short moment to appear on every pod. That is fine for announcements and bad for second-sensitive live ops.
Dashboard 1.114.3: Public Pages Survive a Timed-Out Session
Dashboard 1.114.3 and 1.114.4 are mostly about the public website. The change worth calling out for developers is simple: if you are reading a public page and your session expires, you stay on that page. Only the private parts of the dashboard still ask you to sign in again.
That sounds tiny until you have lost a docs paragraph, a pricing comparison or a feature page scroll because a background session check decided you had been idle too long. Visitors who are not logged in never notice. Logged-in developers who leave a tab open overnight do.
Also Shipped
A few smaller items round out the week:
- User-limit warning mails now go out once per limit. If your project approaches a plan limit, you get one clear mail instead of a stream of repeats.
- Feature pages and legal pages are listed in the sitemap, so search engines can find the public documentation and legal texts more reliably.
What Did Not Change
To be clear about the scope: Unity SDK 1.12, Godot SDK 1.11, Simple Server 1.6 and MCP Server 1.9 are unchanged. If you want the full tour of last week's feature release, start with the weekly roundup on inventory, chat and turn-based matches.
Get Updates Faster on Discord
This post sums up a quiet polish week. If you want to hear about releases the moment they ship, join the horizOn Discord server. New versions land there live, often days before this weekly roundup, and it is the quickest place to ask questions or tell us what you need next.
If you ship on Unreal, pull SDK 1.10.5 and keep building on last week's features. For everyone else, no reinstall is needed. Reply on Discord or open an issue on GitHub. The full list of changes is on the horizOn changelog.