I've always heard about the "builder lag", never knew it affected barracks too.

[bengan112]

The real question here is, why do you wait until the last possible second to cook your army for war. You get 24 hours, who cares about 3 minutes. Work on your own time management issue because supercell isn't working on theirs.

Looks to me like you should work on your reading comprehension instead of telling the OP to work on his time management.

[Taiden]

My reading comprehension is fine, this is a very old known issue that is not getting fixed. I was offering a work around. But thanks for the advice.

[Echo006]

Supercell, frankly, don't give a s...nevermind. By creating builder lag, Supercell gets more profits from people who gem. If they really had our best interests at heart, they would've fixed it and I'm sure they know how. But why would they fix it, when they get more money from it!?

[Cowbug]

I know the shield isn't impacted by the bug, and I'm pretty sure the boost isn't impacted either. But let's pretend it did - you just extended your builds by 5s by reloading your base, and your timer only cuts off 1.25 seconds of that. You're still 3.75s longer. So, yeah, still bad for consumer. Like I said, if you just stopped to actually think about it, I wouldn't have to explain this...

But please, keep demonstrating what an exemplary complacent consumer you are.

You're the one that said the boosts were impacted, now they aren't because if they were it wouldn't help your argument?

Bottom line is, is the timing perfect? No. Would it be nice if they fixed it? sure. Am I going to lose sleep over it? No, I slept just fine lat night. There are so many much bigger issues out there. There is also, in almost every industry, an acceptable margin of error. Everyone knows there probably isnt exactly 1 gallon of milk in that jug, but its close enough that no one worries about it. Lag is that last drop of milk in the video game gallon jug. It wouldn't surprise me if somewhere buried in the TOS is a blurb about times not being 100% precise, and the user accepts this. If its not there, they are more likely to add that than fix the issue because its 1000Xs cheaper. Its not that I'm super complacent its that I pick my battles and this battle isn't worth my time.

[Kingzenith]

Wow, this is the first I've heard of this. That's pretty messed up. Since they've publicly stated they are too lazy to fix a known issue which is adversely impacting paid services, perhaps an official complaint would be warranted? Their US operations is located out of San Francisco, so a formal complaint to the SF BBB would be a good start. We could always file a complaint with the FTC as well.

I thought I heard SC isn't in good favor with the BBB. I don't know if that was true or not.

[arunt]

My reading comprehension is fine, this is a very old known issue that is not getting fixed. I was offering a work around. But thanks for the advice.

I don't want to get in the middle of you guys arguing, but I would like to say one thing - it may be an old and known issue, but most players do not know about it.

[Kazouma]

The butterfly effect comes into play. Even atomic clock will lose seconds after hundreds milion years

[bengan112]

My reading comprehension is fine, this is a very old known issue that is not getting fixed. I was offering a work around. But thanks for the advice.

He said it was on prep day, that is not last minute.

[Porkloin]

Supercell, frankly, don't give a s...nevermind. By creating builder lag, Supercell gets more profits from people who gem. If they really had our best interests at heart, they would've fixed it and I'm sure they know how. But why would they fix it, when they get more money from it!?

Let us say the error was in favor of the players, rather than against them. I imagine that we would never then have heard this: "Fixing this bug would require us to rewrite the code from scratch, in a completely different programming language. This simply will not happen. "

[Dresden]

Oh relax Dresdan, i believe the world has much bigger issues to worry about than to take Supercell to court over a few seconds or even a few minutes. Its lag, it happens. Would you sue Activision for all the lag in their COD servers?

It's not lag. It's an intentional design which adds seconds to your counters. It has absolutely nothing to do with electronic clocks.

You're the one that said the boosts were impacted, now they aren't because if they were it wouldn't help your argument?

Bottom line is, is the timing perfect? No. Would it be nice if they fixed it? sure. Am I going to lose sleep over it? No, I slept just fine lat night. There are so many much bigger issues out there. There is also, in almost every industry, an acceptable margin of error. Everyone knows there probably isnt exactly 1 gallon of milk in that jug, but its close enough that no one worries about it. Lag is that last drop of milk in the video game gallon jug. It wouldn't surprise me if somewhere buried in the TOS is a blurb about times not being 100% precise, and the user accepts this. If its not there, they are more likely to add that than fix the issue because its 1000Xs cheaper. Its not that I'm super complacent its that I pick my battles and this battle isn't worth my time.

Did you even read? I said I'm pretty sure it doesn't affect boosts, but pretending it did, it still negatively impacts the consumer. What's so hard to understand about this? And again, THIS. ISN'T. LAG. This is code which is directly altering the completion time on your builds. It has ABSOLUTELY NOTHING to do with lag. Honestly you guys don't even know what lag means...

I thought I heard SC isn't in good favor with the BBB. I don't know if that was true or not.

Wouldn't surprise me with scammy practices like this one.

The butterfly effect comes into play. Even atomic clock will lose seconds after hundreds milion years

.... Again. This has nothing to do with clocks or lags. This is Supercell ADDING time to your queues.

Please read before responding.

Let us say the error was in favor of the players, rather than against them. I imagine that we would never then have heard this: "Fixing this bug would require us to rewrite the code from scratch, in a completely different programming language. This simply will not happen. "

Your point...?