I don't mind when you write about the heal all button, this is actually a good thing, because with that I can show the devs, that it is still an ongoing issue. What I don't like is spreading hate and misinformation.
If you write it one more time, I will have give you warning points.
(Sorry, but it is very annoying...)
November 19 on the agenda, but it is December 12.However, it is on our agenda, and something we are investigating solutions towards.
I understand it might take a while to change one thing but it would be instantaneous to put it back as before until you find a more suitable solution.We again apologize for any inconvenience, and thank you all for your patience and understanding.
I think you completely missed my point. As I wrote, I don't mind, that you write about the button, I would even encourage you to do so. The only problem is, how it is written. Writing, that there is no information is just not right and an outright lie. I surely agree, that there could be more information, but not, that there is none.And what else You want to receive from players when the company (InnoGames) with it's devs make players to do so due to their bad implementations in the last months?
Remeber, no one asked for heall all button, a lot of players are tired of waiting and see how bad are developers gestionating this situation without a real and clear answer on WHY this was needed and HOW they are gonna adress this annoying Issue.
Frustrated? Players are already annoyed by all weeks of waiting for nothing
How You want to make us heard?
No need for warning points, it means nothing for anyone, clearly not for me.
You are the Community Manager and I respect Your position and Your work here, but we are tired of such nonsence from InnoGames, even if it's not Your fault for anything, You are still working for them and people will begin to hate You too just for doing Your job, and that's just one of the risks ...
Just tell, when will they remove this button?I think you completely missed my point. As I wrote, I don't mind, that you write about the button, I would even encourage you to do so. The only problem is, how it is written. Writing, that there is no information is just not right and an outright lie. I surely agree, that there could be more information, but not, that there is none.
That's why I am annoyed. Not because of the context, but at how it is written.
after 3rd Ferrari is paidJust tell, when will they remove this button?
To hide a button that don't need 3 weeks...As I wrote many times already, there is much official information. If you write it one more time, I will have to give you warning points.
(Sorry, but it is very annoying...)
I don't mind when you write about the heal all button, this is actually a good thing, because with that I can show the devs, that it is still an ongoing issue. What I don't like is spreading hate and misinformation.
The latest information is this one: https://forum.beta.forgeofempires.c...hangelog-w-c-15th-november.15147/#post-127785 (This was 3 weeks ago)
With this announcement as addition: https://forum.beta.forgeofempires.c...guild-battlegrounds-performance-issues.15208/ (This was not even one week ago)
I thought due to the age of this bug that it would've been solved ages ago. It has hit many. I still remember the outbreak of freaked out players when it did hit them. The BD's depleted to 0 was never refunded "own responsibility" and some forum warnings where given for this bug. Making it one of the most memorable bug. Glad to see it resolved. Though it eerily resembles something that isn't an bug and never should've left Beta before a fix was introduced. Just can't clearly remember what. I guess there are a bit too many examples and it's a little too late now. Maybe next year's good intentions. To before releasing flawed features to live fixing the flaws until it's ready.In rare cases, it was possible to trade the last 2 of one blueprint, so that you ended up with 0 for that blueprint. This no longer possible and 2:1 trades can only be done, when you select 2 different blueprint or you have at least 3 of one blueprint