2026.09.14 - Universal Tracker Fix

Fixed

• Universal Tracker support (added in 2026.09.13) was making the server silently reject real progress: Universal Tracker's context class identifies its connections as tracker-only, and this client was inheriting that identity unchanged. Location checks and goal completion now go through correctly whether or not Universal Tracker is installed.

Changed

• Shortened the /savedir and /conquest in-client help text for readability.

Full Changelog: 2026.09.13...2026.09.14

2026.09.13 - Universal Tracker Support

Added

• Optional Universal Tracker support: if you have the Universal Tracker apworld installed, the client now shows a tracker tab with in-logic location/item state, derived directly from this world's own logic. No effect on the client if Universal Tracker isn't installed.

Full Changelog: 2026.09.08...2026.09.13

2026.09.08 - New Useful/Filler Items

Added

• New Useful/Filler items: Resources (Krowns, Food, Wood, Lore/Faith, Stone, Iron, Military Experience/Hunting Trophies). Each one comes as two item types:
  • A filler item like "100 Food" gives you that amount instantly the moment you receive it, but only while you're online and playing. It's forfeited if you're not around to catch it.
  • A "Starting X" item like "50 Starting Food" is a permanent, one-time bonus: once you get it, you'll start with that extra amount at the beginning of every battle you play from then on, whether you were online to receive it or not.

Full Changelog: 2026.09.04...2026.09.08

2026.09.04 - Non-Linear Chapter 7 Requirement Logic Fix

Fixed

• Non-Linear Mode: the chapter7_requirement option now also gates the genration logic, not just with the Chapter lock enforcement in-game.

Full Changelog: 2026.09.02...2026.09.04

2026.09.02 - Fix Stale Backup Re-Patch & Room-Switch Reconnect

Fixed

• Reconnecting the client to a different room could fail with "The server is running a different multiworld than your client is. (invalid seed_name)" and silently not log in. It should now be fixed by clearing the stale seed_name before each new connection attempt.
• After a Northgard update, applying the patch could silently re-patch the stale pre-update backup and overwrite the freshly-updated game with a repatched OLD build, instead of patching the new one. It should now be fixed by re-checking whether the live install is fresh and vanilla before deciding what to patch.

Full Changelog: 2026.08.27...2026.09.02

2026.08.27 - Patch Should Survive Game Updates

Fixed

• Northgard's updates shuffled its internal function numbers, breaking chapter-lock enforcement. It's should now be fixed by having the patcher find functions by name instead of a fixed number, so it survives future updates.
• The "already patched?" check just compared file bytes, so it falsely said "patched" right after the update and auto-heal never kicked in. It should now be fixed by checking the actual patched code directly instead, so it can't give that false positive again.

Full Changelog: 2026.08.16...2026.08.27

2026.08.16 - More Polishing Fixes

Fixed

• Winning the second same-Chapter battle (top/bottom) wasn't sending the proper checks.
• Non-Linear Mode: the Conquest map could get permanently stuck (no nodes clickable, Escape not working) after winning a battle out of the usual order.

Full Changelog: 2026.08.15.2...2026.08.16

2026.08.15.2 - Non-Linear Mode Logic Fix

Fixed

• Non-Linear Progression Mode: the region/location logic itself was still enforcing Linear Mode's ancestor-adjacency rule, so generation and trackers required an adjacent Chapter to be reached first before a later one counted as logically accessible -- even though the in-game client already unlocked Chapters correctly out of order. A Chapter's location is now logically reachable the moment its own item is received, matching the in-game behavior.

Full Changelog: 2026.08.15...2026.08.15.2

2026.08.15 - Code Cleanup

Changed

• Removed unused internal save-reading helper functions and other minor code cleanup in the client. No user-facing behavior change.

Full Changelog: 2026.08.04...2026.08.15

2026.08.04 - Fixed Left Over Markers

Fixed

• Stale Chapter-unlock markers left over from a previous Conquest save or room could falsely unlock an unrelated node in a brand-new save whenever Northgard's random battle-name pool reused the same name (e.g. a fresh save's Chapter 06 - Top could appear unlocked before ever being earned). The client now continuously reconciles unlock markers against whichever save is actually pinned, removing any that don't belong to it.

Changed

• Simplified the setup guide's connection order: you no longer need to create a Conquest save before connecting the client for the first time -- the in-game lock-enforcement patch applies on connect regardless of whether a save exists yet. You just need to make sure Northgard itself is closed before opening the client.

Full Changelog: 2026.08.03...2026.08.04