Incident hub
Every entry here maps to the official 1.0.4 / 1.0.5 notes or the 14 October 2026 post. Nothing is presented as official until it is in those documents.
Result: …
What the hub covers
Every entry maps to either the official 1.0.4 / 1.0.5 patch notes or Frontier's 14 October 2026 post. If an issue is not in those documents it is listed as community-reported and marked that way, so an acknowledged bug can be told apart from a rumour before you rebuild a zoo around it.
Check order before you report
- Confirm the build number in the main menu — 1.0.4 and 1.0.5 fixed different things, and a fix that shipped in 1.0.5 will not appear on 1.0.4.
- Reproduce once in a fresh save slot: a damaged save and a server-side outage look the same on the load screen.
- Check the Franchise connectivity window before touching storage — market and storage errors usually share one cause.
- Copy the exact error wording. The official form asks for it and support matches on text, not on your description of it.
Where to report
Frontier's tracker at issues.frontierstore.net is the only channel that reaches the developers; the hub links the same tracker on each entry so you can search for an existing report before filing a duplicate. Reports in the tracker carry a status, while anything on this page is either official text or clearly labelled community reports.
What the hub will not do
It does not promise fix dates. The patch notes list what shipped, never what is queued, so any timeline on this page would be invented. Where an issue has no official statement, the entry says unknown instead of guessing.
Where the values come from
Animal values are Zoopedia records captured on 17 October 2026. Progression values are cross-checked against the tier table; Frontier said on 14 October 2026 that accreditation requirements are still under investigation, so confirm in game.