Updates

A Little Age August 2026 Patch Notes

Quick answer

Reviewed September 4, 2026: launch-window updates added late-game upgrades, fixed reservation values and several launch issues, and Patch 1.0.5 restored Save/Load for games played from that version onward.

Guide details
Published: Last reviewed: Practical guide for the current public build

Last Reviewed

This page summarizes the public Steam announcement state reviewed on September 4, 2026. Use the official Steam community hub as the final source when exact patch timing or fixed status matters, because the game is receiving rapid launch-window updates.

The important player takeaway is narrow: several hotfixes and the August 29 small patch improved achievements, upgrade behavior, UI readability, tutorial timing, and resource reservation values. Patch 1.0.5 then restored Save/Load and made it accessible in the UI, with the developer noting that it works for games played from that version onward.

Current Patch Timeline

UpdatePlayer-facing changeStatus to remember
Hotfix 1.00.2Addressed a broken load state and temporarily hid the Load buttonLoading was not fully restored in that note
Hotfix v1.00.3Fixed achievement and upgrade-level issues, plus several localization textsDeveloper notes still referenced save/load work
August 29 Small PatchAdded six late-game upgrades, improved several UI/readability details, and fixed reserving resources fetching incorrect valuesDeveloper notes still described the save/load fix as ongoing
Patch 1.0.5Re-enabled Saving and Loading and made it accessible in the UIRestoration applies to games played from this version onward; report remaining save/load problems

If your problem is a missing Load button or a save that does not return after reopening the game, read the save/load after Patch 1.0.5 page before changing local files.

Late-Game Upgrades

The August 29 small patch added six upgrades focused on late-game play. That does not make every upgrade an automatic pick, and the reviewed public notes do not provide a reliable cost table or fixed best order. Use the current interface to identify what each new option changes, then choose only upgrades that solve an active constraint: production, Materials pressure, Gold pressure, route capacity, or a Great Temple dependency.

For a decision framework, use the buildings and upgrades guide. The safest approach after a patch is to make one upgrade, resume, and verify whether the intended bottleneck improves before spending the next reserve.

Achievement and Progression Fixes

Recent hotfix notes mention achievement problems such as building three settlements and winning with a food-less settlement. They also mention upgrade-level behavior after level 12. If an achievement did not trigger before the hotfix, update the game completely, launch the current build, and test the condition again only after checking the official note that names your symptom.

Do not assume every older save will retroactively resolve every achievement edge case. If the condition matters to you, use a fresh controlled attempt when possible.

UI and Readability Changes

The small patch improved visual clarity in several interface areas, including building upgrade buttons, destination names on sender instructions, overview cards, victory settlement cards, and info panels. These are useful changes for logistics diagnosis because resource movement is easier to read when source, destination, and upgrade state are visually clearer.

If resources are still not reaching a settlement after the patch, treat it as a normal supply-chain diagnosis unless the announcement specifically names a bug. Follow producer, stock, reservation, delivery, route, and destination demand in order.

Reservation Fix

The August 29 small patch also fixed resource reservation fetching incorrect values. If a route looked broken before that update because available stock and reserved stock did not line up, update the game first and then repeat the logistics check in the current build.

Do not assume the fix means every delivery problem is a bug. Confirm production, available unreserved stock, sender instruction, route continuity, and destination demand before changing buildings or roads.

Save and Load After Patch 1.0.5

Patch 1.0.5 supports telling players that Save/Load has been restored in the current reviewed full-game build. It does not justify promising that every older save is recovered, because the developer note says the restored behavior works for games played from that version onward.

Use a short throwaway session to test save behavior after updating. If the Load button is still missing, Steam may not have applied the update or you may be checking the wrong app. If a specific save still fails, preserve the files and check the latest official discussion before manual cleanup.

References