Judging from your username, I'll take that as a compliment... Honestly who are you, telling me to leave? What, you think you make the forum a better place? I'm not looking to start a flame war. Just watch what you say
Printable View
May I just say something to everyone on here?
You sound exactly like the 9/11 conspiracy theorists. You are dead set on your belief that Supercell is evil and purposely created this bug. You have no solid proof of your claims, just a lot of assumptions with a little bit of fact here and there. You act like you know how to program and fix bugs, but most of the people on here are barely out of high school or college, just like how 9/11 conspiracy theorists act like they're architects and engineers. Furthermore, you insult anyone that doesn't agree with you by calling them "blind" or "fanboys" just like the conspiracy theorists calling people "sheeple." Your articles sound like sensationalist bull♥♥♥♥ and you don't act mature enough. No wonder a lot of people are not agreeing with you. You are going about it the entirely wrong way.
Now I admit, it has been a while that this bug has been around for, and it is costing us more gems than normal. But there is still no proof of a scam. If there were Apple would be on their asses, as I am pretty sure they are not making money from it. In any case, why don't one of you file a law suit against them if you really think this is a scam? Get someone to investigate them instead of blabbering on and on about it on the forum, making empty threats? Surely there is someone on here who knows how to go about doing this, right?
I will start off by admitting I did not read through all 87 pages of this thread so I do not know if this suggestion for a fix has been offered to them yet, if it has been then I apologize.
The following suggestion is based on my belief that everything in the game runs on a database.
When a building or an upgrade begins have it log the start time. It can then calculate and save the end time by adding the build/upgrade time to the logged start time. Then have the build/upgrade finish at the saved end time regardless of lag. To keep it all uniform, the logged times should be server time.
Hope this helps.
PS. To anyone who wants to criticize this, have fun. :D
I come from the group of conspiracist that believes what people are told about 9/11 isn't exactly true. You state things about people like myself not being architects and not knowing about what the real facts are. I'm sorry but it doesn't take an architect to know the true facts. I don't really like to rant about 9/11 because no matter what the truth is the whole thing is sad to think about and I feel great sympathy for those involved. What I'm getting at here is people are easily persuaded into believing things whether they be true or false. It's easy to make up a story, as well make it credible. If there is a known issue that with a solution, obviously it should be fixed. If the fix is being neglected, there is likely a reason. In most cases, I believe this one included. It comes down to one thing, money.
I like the quote, but is it not just as insane to continue reading and visiting such a repetitive thread? Are you expecting different results? It doesn't seem like you feel the bug is a big deal so is it insanity that draws you here? P.S. I admit it, I'm also insane :eek:
It isn't as easy to suppress truth and keep things hidden as you believe. The U.S. Government, supposedly one of the most secretive groups in the world, failed to keep the existence of the supposedly non-existent Area 51 a secret (they did finally reveal its existence and purpose, but before that people knew about it for decades). The wire tapping scheme also didn't go on for long before it was discovered.
The same would go for this bug. I would imagine that after 1.5 years, if it truly were an intentional scam, someone would have let it slip by now.
The last part of your response relies on the assumption that there is already a fix available for the bug, which there is no evidence of there being.
Personally I do not believe it was an intentional scam implemented by SC in the 1st place. However, now that it's been 1.5 years without fix it seems as though SC have adopted the "can't be bothered attitude" since the bug works to their favour due to the increased revenue - no matter how minimal.
To prove my point:
Of course it isn't critical for them they're gaining profit off it.
Steve once stated recently that he has a Th8. Clearly he isn't a serious player due to the amount of time he's been at SC for. The only way to experience how critical this bug really is, is to actually play the game regularly & to have a rather well developed village - as I'm sure the majority of people on this thread do & have.
Under this logic the bug will NEVER be fixed. Perhaps once they stop updating the game & have nothing new to add then they might actually get around to implementing a fix.
In other words SC have created an unintentional "scam" & have come to realise the benefits available to them by keeping it in the game. As a result they've decided to do nothing about it whilst providing the response that the bug is "too hard to fix" - which it probably connveniently is - & are currently reaping the benefits.
I hate to go into much further detail since I would only be repeating what's been said by others & myself throughout the entire thread.
Critical has a seperate meaning when dealing with software/bugs. This instance would be refering to how it affects useability or ability of the software to perform. An example of a critical bug would be one that crashes the game or results in data loss and this bug is neither.
This does help reinforce the point you were replying to that people here are involved in arguments they are not educated in.
*edit* To add, the severity of the bug being described as not critical can also refer to how the customer base reacts to it measured in degrees of dissatisfaction. Being that the vast majority of people who have posted in this thread continued or continue to play the game with the knowledge of this bug reinforces that the bug is not critical.