Oh. The response was 3+ weeks ago. And I wonder why they haven't bothered to 'try' until 2 years later?
Seriously, I half don't believe what's said.
Printable View
These would be my answers to it that make sense.
1) Major server bug with their side of the servers, run by amazon, fixing it is hard.
2) Julez posted a reply pages back to sort this out. Also George's reply.
3) Proof?
4) Some bugs are easier to fix than others.
5) See 2
6) And it has been answered by mods and staff multiple times.
7) See 4. Would you rather have this bug fixed or the last 10 updates happen?
www.supercell.net/jobs Go ahead. Fix it. :/
Nope, see my above reply.
1) okay, but where did the 2 years go?
2) Ok....
3) Have they been trying for 2 years? Or have they Just found out?
4) I see
5) Ok.....
6) Doesn't explain a lot, still.
7) Bug fixed. At least then I don't feel ♥♥♥♥♥ed.
Thanks. Please don't get me wrong. I respect Sc and its developers and the mods etc, but we want answers.
MY EXPLANATION FOR THE CAUSE OF THE BUILDER TIME BUG (THEORIZED AND LIKELY, BUT NOT PROVEN)
Since CoC is server- based, whenever you log off your account info gets relayed back to the servers in Finland. This means that things like armies, spells, and anything else just inside of your village gets small amounts of time added to it due to lag because of multiple re-feeds through the server when it's being processed. If your device were connected right to the servers or had an ultra- high speed internet connection there wouldn't be an issue.
But why then does time NOT get added to shields?
Well, other players interact with your shield when trying to attack you. Because your shield is not limited to a function JUST within your village, the server keeps a primary relay to the shield time whenever your device is connected to the internet, meaning that shield info is constantly being fed to the servers instead of a routine, non continuous update with in- village stuff. Because of the constant updating, no time record is lost because you aren't performing any commands on your shield. The shield in itself serves as a command code that stops the server from letting other players view your village in matchmaking or attack, and so it constantly needs to be accessed in order for the shield to stay active.
Not that there's an easy fix for it, but it explains the situation.
MY REPLY TO A LATER POST, CONCERNING THE ABOVE EXPLANATION:
Well, the explanation has very little to do with the solution. It may well be true that the server cross-feeds the info and that it would take a long time to 'unravel' the twisted server feeds that each account gets processed through, but my opinion for the lack of them fixing it is this:
Sure it may take long, but possibly not as long as they have claimed. I think it could be fixed within two-three update cycles, but they would have to find exactly WHERE to put in the correction time for each of the affected timers and so forth.
Keep in mind that very few people (In relative retrospect) in clash know about the builder bug- the forum populus only represents a fraction of the players, so not many people would see a 'correction' of a bug that they didn't know existed as a good use of the update cycle. Due to the devs having to work on the bug, there would be a decrease in the amount of GAMEPLAY content that would be released with the updates, and so there would be multiple update cycles without a lot of actual 'clash' stuff in them, which would give them a LOT of bad feedback and players hating on them. I would see it as a no win for either side, because people DEMAND to see the bug fixed, but get angry when the update cycles are long or contain very little gameplay content, and also because of the vast majority of players who aren't aware that the bug exists. It's a no win for supercell because they FINALLY get around to trying to fix the major bug in the game, but people are still hating on them because the update cycle is long or because there is no content being released with the update.
I think if supercell were cut more slack by the users they would feel much more optimistic and energetic about fixing the bug, but as long as it remains a catch-22 scenario I don't think it's likely to be fixed.