Safer API Key Regenerate and Server-Side AI Translation: horizOn This Week
In a nutshell
API key regenerate now keeps all project data, news translations run through the server, and cloud saves can be found by player ID in horizOn.
This was a week without SDK releases. Unity stays on 1.12, Godot on 1.11, Unreal on 1.10.5, Simple Server on 1.6 and MCP Server on 1.9, so there is nothing to reinstall in your engine. All the work happened on the hosted server and in the dashboard, in places you rarely think about until you need them: replacing an API key, finding one player's save and translating in-game news with AI.
Here is what changed between November 5 and November 11.
Server 1.75.11: Regenerate an API Key Without Losing Your Project
Every game on horizOn talks to the backend with an API key. Sooner or later you will want to replace one. Maybe the key ended up in a public repository, in a screenshot or in a build you shared with testers. The obvious fix is to hit Regenerate in the dashboard.
Since Server 1.75.11 and Dashboard 1.114.6, Regenerate swaps only the secret. The key keeps its identity, and everything that belongs to the project stays attached to it: players and their sessions, cloud saves, leaderboards, remote config, news, localization, gift codes, crash reports, feedback and the multiplayer data behind friends, groups, chat and matches. Before this release, Regenerate created a new key record, and the project data stayed behind with the old one. The dashboard now says clearly that regenerating keeps players and project data.
How to rotate a key safely
- Regenerate in the dashboard. The old value stops working, so copy the new one right away and store it somewhere safe.
- Ship the new key with your next build. Clients that still use the old value will be rejected, so plan the switch together with a release.
- Keep keys out of version control. Put the key in a config file that your build pipeline injects, not in a committed scene or script. A rotation is easy now, but not needing one is still better.
Server 1.75.12: AI News Translation Runs Through the Server
horizOn lets you publish news inside your game and translate each entry with an AI provider of your choice. Until now the dashboard called that provider straight from your browser.
With Server 1.75.12 and Dashboard 1.114.7, translations with OpenAI and Gemini go through the horizOn server instead. The dashboard sends the translation request, and the server forwards it with the API key you saved in your news settings. That key is stored encrypted and the dashboard only ever sees a masked version of it. Your provider key no longer has to travel through the browser at all.
There is a second, quieter benefit. If your provider rejects the key, for example because it expired or ran out of credit, you get an error message for that translation. You are no longer logged out of the dashboard because of somebody else's 401.
Local models work too
If you prefer to keep translations on your own machine, Dashboard 1.114.7 now allows Ollama and LM Studio on localhost. These two still run directly from your browser, because the server cannot reach a computer on your desk. Two settings make it work:
- Ollama needs the environment variable
OLLAMA_ORIGINS=https://horizon.pm. - LM Studio needs its CORS switch turned on.
Addresses in your local network, such as another machine on your LAN, stay blocked. The help text in the settings form explains both setups.
Server 1.75.10: Find a Player's Cloud Save by ID
Support requests often start with one sentence: "My save is gone." To answer that, you need to see the saves of exactly that player.
Server 1.75.10 lets the cloud save list in the dashboard filter by player ID. Before, the list ignored the search and only showed the newest 20 saves of a key, which is useless once a game has more than a handful of players. Dashboard 1.114.5 goes one step further. When you open a player record and follow the link to their cloud save, the search is already filled in with that player's ID.
A quick support routine
- Open the record of the player who reported the problem.
- Follow the link to their cloud save.
- Look at the latest save before you change anything.
That turns a support ticket from a database hunt into a two-click check.
Also Shipped
A few smaller changes round out the week:
- Leaderboard resets. The archive box in the reset dialog now starts unchecked. A reset without it deletes the old season, so tick it if you want to keep a record of past rankings. The admin API still archives by default.
- Plan cards. When you are signed in, the plan cards on the home and pricing pages take you to your account settings and mark the plan you already have.
- horizon.pm on phones. The public website does less work on mobile, the hero section no longer jumps while the page loads, and pages got cleaner titles, descriptions and image alt texts.
What Did Not Change
To keep the scope clear: Unity SDK 1.12, Godot SDK 1.11, Unreal SDK 1.10.5, Simple Server 1.6 and MCP Server 1.9 are unchanged. If you missed the last two weeks, read the roundup on Unreal polish and lighter Cloud Save and the big feature week with inventory, chat and turn-based matches.
Get Updates Faster on Discord
This post sums up the 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 translate your news with AI or run a local model, try the new flow and let us know how it works for you. Reply on Discord or open an issue on GitHub. The full list of changes is on the horizOn changelog.