CARDED: Groups to Glory · public · first seen
Update 1.3.1 is now live for CARDED: Groups to Glory.
This update focuses on performance, save reliability, progression integrity and making longer tournament runs significantly smoother behind the scenes.
Update 1.3.1 improves squad responsiveness, reduces unnecessary saving and repeated processing, strengthens recovery across Match, Training and Press systems, fixes several duplicate-application issues and corrects an important group-stage progression inconsistency.
A major focus of Update 1.3.1 has been reducing unnecessary work throughout a run.
Several systems that previously performed repeated calculations, rebuilt interface elements or wrote profile data more often than necessary have been streamlined.
Squad refreshes have been substantially improved.
Previously, many refreshes destroyed and recreated the entire set of PlayerCards even when the same squad remained on the pitch.
PlayerCards can now be reused and refreshed from the latest authoritative player data instead.
This improves responsiveness across:
Player information, Fitness, Form, Attributes, portraits, Training Card effects and pitch positioning continue to update normally.
The change is focused entirely on reducing unnecessary reconstruction rather than changing the appearance or behaviour of the squad screen.
Training Card profile updates are now grouped into one durable profile commit per logical assignment operation.
This applies to:
Previously, a single Training Card could trigger several separate profile writes for lifetime assignment, usage, player upgrades and best-score tracking.
Large bulk operations could therefore create a significant amount of unnecessary profile-save activity.
These updates are now committed together while preserving the same lifetime statistics and recovery guarantees.
Best-score tracking no longer writes the profile when the submitted score does not exceed the existing record.
The score is still checked normally, but an unchanged result now avoids an unnecessary profile save.
Several tournament systems now avoid repeated calculations where the result would be unchanged.
Provisional tournament awards are now refreshed once after relevant batches of AI fixtures rather than rebuilding after every individual result.
Frequently used authored data also now uses indexed lookups for systems including:
The authoritative data and fallback behaviour remain unchanged.
Longer tournament runs can accumulate a large amount of match, player, Form, statistics and tournament-history data.
Update 1.3.1 includes a major optimisation pass on current-run saving.
Current-run saves now use compact JSON formatting.
This reduces unnecessary whitespace in the save file without removing any gameplay data or changing the save schema.
Existing v1.3 saves using the previous formatted JSON remain fully load-compatible.
The current-run save pipeline has also been streamlined while preserving its durability protections.
Redundant validation work has been removed from the successful save path.
The game still:
Several expensive validation steps that were processing the same already-validated data more than once have been replaced with cheaper equivalent checks.
The result is substantially improved late-run save performance without weakening the existing recovery process.
Match resolution has received additional protection against duplicate callbacks, interrupted transitions and partial saves.
Each player Match now uses a stable transaction identity tied to the run and fixture.
Once the authoritative result has been committed, recovery can continue from that stored result rather than recalculating the fixture.
This prevents interrupted Match flow from:
The committed Match result remains the authoritative outcome.
Match lifetime statistics also use persistent duplicate protection so failed profile writes can be retried safely without counting the same fixture twice.
Training sessions now preserve more of their transaction state across saving and loading.
A Training session records a stable occurrence identity together with the generated results needed to resume safely.
This includes:
Interrupted Training can therefore continue from the already-generated outcome rather than rerunning randomisation or applying the same effects again.
Regular Press answers now use stronger occurrence and transaction protection.
The game validates the authoritative offered answer before applying its effects and prevents stale or duplicate callbacks from processing the same question twice.
Press transaction state now protects:
Reloading during Press no longer allows the same committed answer to apply its effects multiple times.
The new Training Card batching system also includes cross-file recovery protection.
Each logical Training Card operation creates a persistent profile-sync obligation before the profile update is attempted.
The profile then records a stable committed-operation identity.
This means interrupted saves can recover without:
If the profile save fails, the pending operation remains available for retry.
If the profile update was already completed before an interruption, the committed identity prevents it from being applied again.
Run-end profile persistence has received additional protection.
Terminal career progression now distinguishes between:
A failed profile write no longer causes the game to treat the terminal transaction as permanently complete.
The save can instead be retried without recalculating or duplicating the underlying terminal rewards.
This protects systems including:
Fixed an inconsistency where some group-stage progression paths could treat three points as sufficient for knockout qualification.
CARDED’s group-stage qualification target is 4 points.
The four-point requirement is now applied consistently across:
RunState now remains the single authority for determining whether the player has qualified from the group.
Affected legacy v1.3 saves containing contradictory progression state are reconciled conservatively while preserving the visible points already earned.
Update 1.3.1 continues the reliability work introduced in previous updates.
Improved recovery handling now covers:
The general recovery principle remains the same:
Once an authoritative result has been committed, the game should recover from that result rather than rerolling, recalculating or applying the same effect twice.
Existing v1.3 profiles and current runs remain supported.
Several smaller release and interface improvements are also included.
The official Discord can still be accessed directly from the main menu.
Thank you to everyone who has continued to report issues and share feedback.
A few recent community reports have been particularly helpful in identifying areas that need attention.
The official Discord link available through the main menu was no longer working correctly.
Thank you to the community members who pointed this out.
The in-game Discord buttons have now been updated to use the current official invite link, so both the main-menu DISCORD button and the developer-note JOIN THE DISCORD button should once again take players to the correct community server.
If you notice another broken link, bug or strange piece of behaviour, please keep reporting it. Even small reports can help identify issues that would otherwise be easy to miss.
We have also seen and heard feedback around UI readability, particularly around the amount of information presented on some screens and how easily that information can be understood at a glance.
This is something we are actively looking at.
CARDED has grown significantly since its original release, and some interfaces are now presenting far more information than they were originally designed to handle.
Rather than making rushed visual changes as part of a reliability-focused patch, we want to improve readability carefully without removing useful information or making important tournament data harder to access.
Future updates will continue looking at areas such as:
Update 1.3.1 is primarily focused on the technical foundation underneath the game, but UI presentation and readability remain an important area we intend to continue improving.
Thank you to everyone who has raised this feedback constructively.
Update 1.3.1 does not intentionally rebalance teams, match formulas, rewards, odds or tournament difficulty.
The focus of this update is reliability, performance and ensuring that existing systems behave consistently across longer runs, interruptions and reloads.
Existing v1.3 profiles and current-run saves remain supported.
Update 1.3.1 is primarily a foundation update.
A large amount of the work in this release is designed to make the tournament simulation more reliable, responsive and easier to build upon in future updates.
The underlying tournament now has stronger authority over Match results, player statistics, progression, recovery and persistent run history.
This gives future updates a much stronger base for expanding how CARDED interprets and presents the story of each tournament.
Thank you to everyone who has played, tested, reported issues and shared feedback.
Reports around broken links, UI readability, progression behaviour and save reliability have all helped shape the work going into CARDED.
Update 1.3.1 is focused on making every run smoother and more dependable from the opening fixtures through qualification, the group stage, the knockout rounds and the final tournament result.
There is still plenty more planned, including continued work on how CARDED presents information and tells the story of each tournament.
Community feedback will continue to shape those improvements.
— William
Spartanwilly Studios
| Depot | New manifest | Previous manifest |
|---|---|---|
| 4785221 | 6557663882314520771 | 6233616090516715338 |