Version 0.09 – Changelog

Improved support for the Alfa [Z] and Beta auction resource crates, so the items are now recognized correctly and can be used without errors caused by avatar stack grouping.
Completed the combat statistics for planetary defense and improved their presentation in descriptions and modals, so defensive units now display the full set of data and are correctly included in combat calculations.
Clarified the descriptions of rewards related to Academy XP and added separate avatar items for XP rewards, so players can clearly see where the awarded experience is applied.
Fixed resource collection for the “Collect Own Resources” mission so that fleets correctly collect resources from colonies even when quickly switching between planets.
Improved the presentation and logic of research times so that queued levels are no longer incorrectly calculated or displayed using the time of a different technology level.
Completed the descriptions of the ship responsible for the DM mission in all languages, clearly explaining that the mission may not only bring antimatter back but may also consume part of it.
Added automatic refreshing to the Empire view and improved planet data synchronization so that buildings and resources are displayed in their current state.
Fixed espionage report logic so that the scanned player always receives information about a hostile scan and is no longer left without a warning.
Expanded the flight overview so that the overview tab now shows which fleet is flying and what resources it is carrying, without requiring the player to open the separate fleet tab.
Fixed research queue logic based on the source planet, so research time no longer changes unexpectedly after switching planets, cancelling the queue, or destroying the source moon.
Added safeguards preventing the deletion of a planet or moon from which research is currently being conducted, avoiding inconsistencies in research time and order.
Clarified the behavior of the Discovery Resort and improved expedition limit presentation so players can clearly distinguish expedition slots from the daily limit.
Fixed the phalanx so it once again correctly displays flights to scanned coordinates instead of returning an empty result despite active missions.
Protected fleet missions against cases where the target disappears during flight or no longer exists at arrival, so fleets are no longer lost and correctly return instead of disappearing.
Added fleet launch validation at the mission start stage to reduce the possibility of sending ships to nonexistent targets or using disallowed configurations.
Hardened alliance applications: a player can no longer have active applications in multiple alliances at the same time, and old pending applications can no longer later “move” the player into another alliance.
Expanded alliance application acceptance logic with an additional check of the player’s current status, eliminating cases where a player who had already joined another alliance could still be incorrectly accepted.
Restored full functionality of public battle reports from Top Battles, including support for links based on report keys rather than only numeric identifiers.
Improved battle report storage and retrieval so reports shared through the battle ranking are correctly recognized and remain accessible from public rankings.
Improved redirect security when changing language and switching planets to prevent incorrect redirects outside the service.
Strengthened the stability of resource recalculation and several backend operations to reduce the risk of inconsistent writes during simultaneous actions and refreshes.
Improved player relationship logic so that friends, player protection, and similar mechanics work more reliably even when data is in different refresh states.
Hardened the bank, chat, and shared IP reports against concurrent operations to reduce cases of duplicate processing or restriction bypasses.
Protected the lotto mechanics against issues caused by simultaneous clicks and rapid repeated actions, ensuring that each bet is always settled against a consistent resource state.
Improved the lottery: ticket purchases are now processed atomically, reducing the risk of exceeding daily limits or incorrectly charging deuterium when multiple actions occur in parallel.
Fixed the lottery draw itself so the result is actually selected from the full range instead of relying on a fixed value.
Added protection against processing the same daily lottery draw multiple times, preventing a single day from being settled again and rewards from being duplicated.
Improved lottery reward and message processing so winner payouts and system messages are stored in a more consistent and secure way.
Expanded the automated test suite for fleet, research, defense, battle reports, alliances, bank, chat, shared IP, lotto, and lottery to catch similar regressions more quickly in future deployments.