The early-game New Player Guide is still being improved. If you need help, please join one of the following communities:
QQ Group: 1098841891
Telegram: https://t.me/+KkKgOeeWXbM0NmM1
Discord: https://discord.gg/2g6mZfAPq
The Battle and Farm client protocols have been upgraded to V0.033. To prevent runtime data from different versions from being mixed, please update the client before entering battle or operating the Farm. Older clients may be unable to access these features.
1. Improved current Battle activity recovery. When entering the Battle Hall or preparation screen, the client now asks the server to identify the player's current room, manual battle, Auto Battle, or settlement state and resumes the correct page. If a battle is already active, the client will not mistakenly create a new room or enter another runtime.
2. Fixed first-battle handoff and reconnection ownership for Auto Battle. After Auto Battle starts, the client can immediately query the same session's server state instead of waiting for a complete battle payload before the first transition. Account changes, session changes, and older requests cannot route the player into the wrong Auto Battle session.
3. Strengthened containment and exit protection for invalid Battle runtimes. Deterministically corrupted states now receive bounded server handling instead of unlimited background retries, and the same error can no longer block a player's active abandon request. Cancellation and abandonment continue through the formal settlement path, preserving evidence and safely returning eligible assets.
4. Fixed crop maturity refresh while remaining on the Farm page. Every planted or watered plot continues to redraw with time progression. When a crop crosses its maturity time, the page automatically reloads the authoritative server state, so leaving and re-entering the Farm is no longer required.
5. Strengthened Farm freshness and concurrency protection. Batch actions, tools, resources, and plot confirmation are paused together until authoritative maturity is confirmed, preventing harvest requests based only on local display progress. Older responses cannot overwrite newer state, and retired patch history now recovers through a complete refresh, reducing deadlocks and inconsistent page state.
1. Please conduct trades through the Market. The Market does not charge any transaction fees. Issues arising from private trades will not be handled.
2. If you encounter a bug with the Steam Community Market, please contact the developers through the QQ Group, Telegram, or Discord.
1. Continue improving the Main Quest and Side Quest features.
2. Add a Thank You feature.
3. Update the Leaderboard feature.