
We have expanded the Kingdom Explore Mode with new difficulties, a new boss type, an updated menu, and added optional Side Quests.
The core Explore battle mechanics remains unchanged.

We have updated the Explore menu to use the Kingdom Map, matching the layout used by Quests. All Explore encounters will now appear as nodes on the Kingdom Quest Map.

The right-hand panel is now always visible at the start of an Explore Run, so players can interact with encounters immediately without first clicking a map location. Also, the number of clicks to complete an Explore battle remains unchanged.
The Wandering Merchant system has been changed so it will only trigger once per Explore Run. This is to improve the flow of battles in the run, reducing the interruptions between battles.
We have also made some changes to how the Explore opponent teams are generated to try to improve enemy variety.


Numbers shown in screenshots are from active development and may not be the same as when the update goes live.
We have added 4 new Explore difficulties – Difficulty 13, 14, 15, and 16. These difficulties are designed for players who have progressed through Astral Spire and Kingdom Prestige and are ready for tougher fights.

On Difficulties 13–16, the final boss changes from a Mythic Boss to an Eternal Dragon Boss.
Players earn Badges rather than Medal Tokens for defeating an Eternal Dragon. Reaching an Eternal Dragon Battle costs 250 Mythstones. This cost reflects the higher Mythstone yields available at the new difficulty levels.
Mythstones are now also rewarded from Side Quests, more on that later.
Defeating the Eternal Dragon Boss will still reward a Boss Chest.

Kingdom
Dragon
Adana
Eternal Rubirath
Blackhawk
Eternal Krakynos
Blighted Lands
Eternal Vizinium
Bright Forest
Eternal Emeraldrin
Broken Spire
Eternal Meteoridan
Darkstone
Eternal Nebuladryx
Dhrak-zûm
Eternal Garnetaerlin
Divinion Fields
Eternal Lunarelleon
Dragon’s Claw
Eternal Narcithus
Drifting Sands
Eternal Topasarth
Forest of Thorns
Eternal Gladius
Ghulvania
Eternal Thornaressa
Glacial Peaks
Eternal Sapphirax
Grosh-Nak
Eternal Hematrax
Hellcrag
Eternal Eklipsos
Karakoth
Eternal Vizinium
Khaziel
Eternal Garnetaerlin
Khetar
Eternal Amenhotrex
Leonis Empire
Eternal Solarithus
Maugrim Woods
Eternal Lunarelleon
Merlantis
Eternal Krakynos
Mist of Scales
Eternal Demizerius
Mydnight
Eternal Runethius
Nexus
Eternal Meteoridan
Pan’s Vale
Eternal Narcithus
Pridelands
Eternal Hematrax
Shentang
Eternal Orchidius
Silverglade
Eternal Amethialas
Sin of Maraj
Eternal Eklipsos
Stormheim
Eternal Comethalas
Suncrest
Eternal Rubirath
Sword’s Edge
Eternal Orrissea
Urskaya
Eternal Comethalas
Vulpacea
Eternal Orrissea
Whitehelm
Eternal Solarithus
Wild Plains
Eternal Nebuladryx
Zaejin
Eternal Gladius
Zhul’Kari
Eternal Belcerulea

Side Quests are a new optional feature that may appear during an Explore Run. Which you can also chose to bypass.
An Explore Run can contain 0–3 Side Quests, and the chance to encounter a Side Quest increases as you play higher difficulties.
Note: Difficulty 1 has no Side Quests, and Difficulty 16 will always have 3
Each Side Quest consists of a single battle, and the enemy teams follow the same construction rules as Explore Mini-Boss battles.

A Side Quest will appear on the map after the preceding map location has been defeated.
Once you start the next Explore battle after a Side Quest has been revealed, the Side Quest is no longer available.
So, once you pass it on the map if you have not completed it, you cannot go back to it.
As you can see in the example above, the Side Quest path will show you what reward is available for completing the Side Quest battle.
Each Side Quest will always reward Mythstones, as well as one of the following:

We have added a new Constellation Board to Astral Spire – The Jester!



Note: The last two in the list above were reported in the beta and later confirmed as working by the team. I am leaving them in the list, just in case they pop up again once live or something happens between now and when 9.3 releases, and they are not actually resolved.

A note from Jeto: As always, in the background, I am chasing up a long list of bugs and QOLs, so if it’s not mentioned above, then it has not yet been resolved. Expecting more information in 9.4 about the notification issue as well.