·9/2/2026
fromPlayer Community Lead
Weekly Updates on Last Shelter (36th @2026)
--
This week, several feedback topics involved situations where it wasn't immediately clear whether something was broken or whether an unlock condition simply hadn't been met yet.
The Cube Energizer was fully built but showed an "unknown error" every time players tapped in. Players who placed Top 10 in Guardian couldn't find their reward chests in their bags. Dragging across the world map caused the game to crash on some devices. And alliances that had completed Eden registration still saw "not registered" on the leaderboard.
Here's what we've confirmed: the Cube Energizer doesn't open until a server enters the Season 12 Registration phase, and the current "unknown error" message is indeed unclear. Guardian Top 10 rewards were sent via system mail, and every account we've checked has a corresponding record. Crashes on certain iPhone devices when dragging the world map are still being optimized. And during Eden sign-ups, status displays on some pages were out of sync — they returned to normal once the matching phase began.
Thank you to @Chucky2909, @B@Luu, and @D-Man007 for sharing server info and screenshots of the Cube Energizer screen; @good.girl and @SkyBlueArmy for providing Guardian rankings and mail screenshots; @RNOF20 and @クワトロ市場 for recording device models and steps leading up to crashes; and @⭐⭕black_ncunha⭕⭐ and @-Tree for describing the inconsistent status displays across pages after Eden registration.
Below is a breakdown of what we've confirmed and where things stand.
--
Cube Energizer: Opens When Season 12 Registration Begins
Some Commanders reported that even after upgrading the Energy Control Hub to level 54 and placing a Charging Core, opening the Cube Energizer still showed an "unknown error." Reinstalling the game or switching networks didn't change anything, leading many players to suspect a building or account issue.
@xiaoyu and @fricardo checked the season progress on the affected servers and confirmed that the Cube Energizer does not become available immediately after meeting building requirements — it also requires the server to enter the Season 12 Registration phase.
Until that point, even if the building level and core requirements are met, the Cube Energizer cannot be used normally.
What's genuinely misleading is the current error message. When the feature isn't yet open, the page simply shows "unknown error" without telling players that a season condition hasn't been met, which can easily be mistaken for a technical malfunction. We'll be improving this message in a future update.
If your server has already entered Season 12 Registration and the Cube Energizer still isn't working, please submit your server number, current season phase, and a screenshot of the page through Support so we can look into it further.
--
Guardian Rewards: Top 10 Chests Distributed via System Mail
After the Guardian event ended, some Top 10 finishers noticed that their reward chests didn't appear directly in their bags, which led them to worry that their ranking rewards hadn't been distributed properly.
@yimu checked the reward distribution records and confirmed that the Guardian Top 10 decoration chests were distributed via in-game system mail on August 21 at 10:14 (Beijing Time), not sent directly to inventory.
Among the accounts we've checked so far, every one has a corresponding reward mail. Some players haven't claimed the mail yet, while others have claimed it but still haven't opened the chest from their bags.
So if you don't see the reward directly in your bag after the event settles, we recommend first checking your system mailbox for unread or unclaimed mail.
If you placed in the Top 10 and still can't find the reward, please submit your server number, event ranking screenshot, and mail page through Support, and we'll continue checking on a per-account basis.
--
Client Crashes: Ongoing Optimization for Some iPhone Devices
Some Commanders reported that the game suddenly closes when dragging the view on the world map. Even after updating the client, clearing cache, switching networks, or reinstalling, the issue can recur. When crashes happen frequently, they directly disrupt gathering, marching, and combat operations on the map.
@jiuyan investigated and confirmed that this issue is more noticeable on certain devices, including the iPhone XR. Dragging across the world map loads a large number of decorations and map elements simultaneously, which can cause high memory usage on some devices and lead the system to close the game.
As a temporary measure, you can tap "Hide Decorations" on the left side of the screen to reduce the map's rendering load, which can lower crash frequency on some devices.
We're continuing to optimize this issue, and future versions will further improve memory performance on the world map for these devices.
Our checks so far haven't found any account data loss or missing battle rewards caused by these crashes, but the frequent shutdowns themselves do interfere with normal gameplay.
If you're using a device other than iPhone XR, or if crashes still happen frequently even after hiding decorations, please submit your device model, OS version, client version, time of occurrence, and what you were doing right before the crash through Support — this will help us identify other trigger scenarios.
--
Eden Alliance Registration: Status Display Out of Sync During Sign-Up Phase
Some alliances reported that after completing Eden registration, pages like the alliance leaderboard still showed "not registered." Relogging or updating the client didn't immediately change the status, which made it hard for alliance officers to confirm whether their registration had actually gone through.
@yimu checked the relevant server and alliance records and confirmed that during the sign-up phase, some pages didn't sync the actual registration status in real time, causing already-registered alliances to still display as "not registered."
Once the official matching phase began, the status of successfully registered alliances returned to normal.
Additionally, a smaller number of reports turned out to be cases where the registration flow hadn't actually been completed. Eden registration requires alliance officers to complete all confirmation steps within the designated time window — if the process is interrupted midway or the connection drops, it's possible to have partially completed the steps without successfully submitting the registration.
So if you encounter "registered but showing not registered" again in the future, we recommend first saving a screenshot of the completed registration page and noting the time. After submitting your alliance name, server number, and relevant screenshots through Support, we can check the actual registration records directly — there's no need to repeatedly attempt registration.
--
Thank you to every Commander who has shared server details, device models, and step-by-step accounts of what happened. What looks like simply "won't open" or a "display error" can actually stem from season phases, event unlock conditions, reward delivery methods, or client issues. The more complete the information, the faster we can pinpoint the cause and address it directly.
Going forward, we'll continue following up on the issues above and use your feedback to keep improving event rule explanations, page prompts, and client stability.
Thank you again for your patience and support.
LS Operations Team
--
This week, several feedback topics involved situations where it wasn't immediately clear whether something was broken or whether an unlock condition simply hadn't been met yet.
The Cube Energizer was fully built but showed an "unknown error" every time players tapped in. Players who placed Top 10 in Guardian couldn't find their reward chests in their bags. Dragging across the world map caused the game to crash on some devices. And alliances that had completed Eden registration still saw "not registered" on the leaderboard.
Here's what we've confirmed: the Cube Energizer doesn't open until a server enters the Season 12 Registration phase, and the current "unknown error" message is indeed unclear. Guardian Top 10 rewards were sent via system mail, and every account we've checked has a corresponding record. Crashes on certain iPhone devices when dragging the world map are still being optimized. And during Eden sign-ups, status displays on some pages were out of sync — they returned to normal once the matching phase began.
Thank you to @Chucky2909, @B@Luu, and @D-Man007 for sharing server info and screenshots of the Cube Energizer screen; @good.girl and @SkyBlueArmy for providing Guardian rankings and mail screenshots; @RNOF20 and @クワトロ市場 for recording device models and steps leading up to crashes; and @⭐⭕black_ncunha⭕⭐ and @-Tree for describing the inconsistent status displays across pages after Eden registration.
Below is a breakdown of what we've confirmed and where things stand.
--
Cube Energizer: Opens When Season 12 Registration Begins
Some Commanders reported that even after upgrading the Energy Control Hub to level 54 and placing a Charging Core, opening the Cube Energizer still showed an "unknown error." Reinstalling the game or switching networks didn't change anything, leading many players to suspect a building or account issue.
@xiaoyu and @fricardo checked the season progress on the affected servers and confirmed that the Cube Energizer does not become available immediately after meeting building requirements — it also requires the server to enter the Season 12 Registration phase.
Until that point, even if the building level and core requirements are met, the Cube Energizer cannot be used normally.
What's genuinely misleading is the current error message. When the feature isn't yet open, the page simply shows "unknown error" without telling players that a season condition hasn't been met, which can easily be mistaken for a technical malfunction. We'll be improving this message in a future update.
If your server has already entered Season 12 Registration and the Cube Energizer still isn't working, please submit your server number, current season phase, and a screenshot of the page through Support so we can look into it further.
--
Guardian Rewards: Top 10 Chests Distributed via System Mail
After the Guardian event ended, some Top 10 finishers noticed that their reward chests didn't appear directly in their bags, which led them to worry that their ranking rewards hadn't been distributed properly.
@yimu checked the reward distribution records and confirmed that the Guardian Top 10 decoration chests were distributed via in-game system mail on August 21 at 10:14 (Beijing Time), not sent directly to inventory.
Among the accounts we've checked so far, every one has a corresponding reward mail. Some players haven't claimed the mail yet, while others have claimed it but still haven't opened the chest from their bags.
So if you don't see the reward directly in your bag after the event settles, we recommend first checking your system mailbox for unread or unclaimed mail.
If you placed in the Top 10 and still can't find the reward, please submit your server number, event ranking screenshot, and mail page through Support, and we'll continue checking on a per-account basis.
--
Client Crashes: Ongoing Optimization for Some iPhone Devices
Some Commanders reported that the game suddenly closes when dragging the view on the world map. Even after updating the client, clearing cache, switching networks, or reinstalling, the issue can recur. When crashes happen frequently, they directly disrupt gathering, marching, and combat operations on the map.
@jiuyan investigated and confirmed that this issue is more noticeable on certain devices, including the iPhone XR. Dragging across the world map loads a large number of decorations and map elements simultaneously, which can cause high memory usage on some devices and lead the system to close the game.
As a temporary measure, you can tap "Hide Decorations" on the left side of the screen to reduce the map's rendering load, which can lower crash frequency on some devices.
We're continuing to optimize this issue, and future versions will further improve memory performance on the world map for these devices.
Our checks so far haven't found any account data loss or missing battle rewards caused by these crashes, but the frequent shutdowns themselves do interfere with normal gameplay.
If you're using a device other than iPhone XR, or if crashes still happen frequently even after hiding decorations, please submit your device model, OS version, client version, time of occurrence, and what you were doing right before the crash through Support — this will help us identify other trigger scenarios.
--
Eden Alliance Registration: Status Display Out of Sync During Sign-Up Phase
Some alliances reported that after completing Eden registration, pages like the alliance leaderboard still showed "not registered." Relogging or updating the client didn't immediately change the status, which made it hard for alliance officers to confirm whether their registration had actually gone through.
@yimu checked the relevant server and alliance records and confirmed that during the sign-up phase, some pages didn't sync the actual registration status in real time, causing already-registered alliances to still display as "not registered."
Once the official matching phase began, the status of successfully registered alliances returned to normal.
Additionally, a smaller number of reports turned out to be cases where the registration flow hadn't actually been completed. Eden registration requires alliance officers to complete all confirmation steps within the designated time window — if the process is interrupted midway or the connection drops, it's possible to have partially completed the steps without successfully submitting the registration.
So if you encounter "registered but showing not registered" again in the future, we recommend first saving a screenshot of the completed registration page and noting the time. After submitting your alliance name, server number, and relevant screenshots through Support, we can check the actual registration records directly — there's no need to repeatedly attempt registration.
--
Thank you to every Commander who has shared server details, device models, and step-by-step accounts of what happened. What looks like simply "won't open" or a "display error" can actually stem from season phases, event unlock conditions, reward delivery methods, or client issues. The more complete the information, the faster we can pinpoint the cause and address it directly.
Going forward, we'll continue following up on the issues above and use your feedback to keep improving event rule explanations, page prompts, and client stability.
Thank you again for your patience and support.
LS Operations Team
1147