Quicker actions and clearer feedback
Quest creation moved directly into the fixed Quest header, keeping the existing details, reward preview, reminder and persistence flow within easy reach. Character level gains also received a global overlay, so a level-up is visible whether the reward arrives on a main screen or inside a submenu.
Starting an Adventure now returns the player to the top of the Realm Map with the Active Adventure shown first. These changes reduce unnecessary navigation while keeping the core loop — real-world Quest, character growth, Adventure — easy to follow.
A beginning for the Chronicle
A six-part illustrated prologue now introduces the Realm and the idea behind Ascendant before the main journey begins. Existing characters keep their saved progress and see the introduction once when the completion marker is absent, then return to the character they already built.
The migration needed several internal-build corrections because an earlier marker could not distinguish a genuine completion from an automatic upgrade value. Version 1.0.6 repaired that path conservatively rather than deleting or resetting player data.
Steps can complete a Quest
A Quest can optionally use a daily walking target. Ascendant records a safe on-device baseline, handles the configured Quest reset time and automatically grants the Quest's standard difficulty-based rewards when the target is reached.
Step goals are opt-in and old Quest saves load with them disabled. They are another way for real activity to drive character progression, not a separate source of bonus rewards.
Merchant refreshes and equipment identity
The General, Traveling and Legendary Merchants can refresh their stock early after a confirmation and an in-game Gold payment. The operation is persisted defensively so an interruption cannot charge the player twice.
Every named piece across the current equipment sets also received its own icon, with a generic slot image retained as a fallback for unknown older items. At the same time, the art pipeline was resized and converted carefully enough to reduce the Play download dramatically without changing the composition of the artwork.
Two internal releases, more work to verify
Version 1.0.5 brought the progression and asset work to Google Play internal testing, followed by 1.0.6 with notification and introduction fixes. Automated analysis, tests and signed release builds passed for these milestones, while upgrade behaviour and device-specific notification flows remained explicit targets for physical Pixel testing.