Thanks for sharing your ideas, some of them are really good!
It will take us some time to develop , so please be patient, things that are really important to you like the shield after attack will be prioritized first.
Dear Players,
We are currently investigating an issue involving unintended troop duplication that began after yesterday’s server maintenance.
At this time, the bug is still active. Once it is fully resolved, all players’ troop counts will be reset to zero in order to ensure a fair and balanced game environment for everyone.
We estimate that a fix may take up to 48 hours. In the meantime, we kindly ask all players not to exploit this issue and to help us maintain fair play across the server.
Edit: Bug is finally fixed.
For those curious about the technical side: during maintenance, we switched the server to a 'green–blue' deployment setup to achieve zero downtime during game updates. Many of you had reported that the game sometimes became inactive, so this change was meant to fix that.
However, the switch caused the cron processes to run multiple times because we temporarily had two servers active. One server handled requests correctly, but both servers were starting cron jobs at the same time. This made everything happen twice, and in some cases even four times, because the cron jobs were triggering additional cron jobs.
As a result, issues like double attacks and unexpected village movements occurred, and things escalated quickly from there.
Thank you for your patience and understanding.
— The Team
Hey, the game had maintenance today. During that time, there was a few servers up in the same time causing multiple movements to be sent for each action.
I will see if i can calculate exactly how much troops each affected player is supposed to have.
It was our bad, the game should have been closed during that time. Sorry for the inconvenience..
Dear players,
First, we want to thank you for the incredible support. Seeing Server 2 grow to over 400 registered players has exceeded our expectations, and we’re excited about the community that’s forming around the game.
As the server grows, it’s important for us to maintain an active and engaging world. Currently, a significant portion of accounts become inactive after just a few days—for example, only a small fraction of players remain active after 7–10 days. Inactive accounts not only affect the gameplay experience by filling the map, but also place unnecessary load on the server.
To address this, we will begin implementing the following approach:
Players who have not logged in for 10 consecutive days will be soft deleted.
This means:
This allows us to keep the game world active and improve overall server performance, while still preserving player data for potential return.
Thank you for your understanding and continued support.
— Emperium
Although 19 players upgraded Self Defense to tier 1, 5 players to tier 2 and one player to tier 3,
Unfortunately Self defense was a skill isn't unique enough, what it did was in case you were winning fights, with Self Defense you would lose less troops, but since Sharper Blades does essentially the same thing, cause the stronger you are the less troops you will lose in fights,
we decided to remove this skill. All players who upgraded it will get their skill points back.
With that being said, we do want to add a new skill in the near future for faster Oasis looting, since Gold Rush only effects the production of your own villages, and Filthy Thief only effects looting in PVP, there is no special skill for players which base their economy on oases.
If anyone has other ideas for Skills that should be added, type them here!
We noticed that players were progressing a bit too quickly through oasis looting.
To better balance the game’s pacing, we’ve adjusted the rate at which troops gather resources from oases.
We’d love your feedback—if it feels too slow now, we can revisit and fine-tune it.
Keep in mind: the more troops you send, the faster the loot. Players with very large armies were progressing at a rate that felt unbalanced, which led to this change.
Thanks,
Emperium