Why the petitioning for ch3ats?

Thing is as soon as SC fixes the current issue, there will always be a new one made wuickly after. And it will go on on forever.

Quote:

---

Originally Posted by LightBeatz

I think SC should hire the guys telling them to fix the game to fix the game. :rolleyes:

---

I think society should stop compromising.

Quote:

---

Originally Posted by mARCSBUG

Its a matter of applying resources to an issue, cost of said resources and return on investment.

I can guarantee you if this issue was more publicly promoted 'and people didn't accept it', more attention/resources would be allocated.

Here's what I'd like to see happen:

Getting everyone 'where everyone = a blip and above on their sales register', to not purchase gems for X days. If this could be successfully organised I can guarantee you would see change.

---

Fill us in on the inside information you seem to have. How do you know they aren't allocating resources to fix anything?

Quote:

---

Originally Posted by mARCSBUG

Do I think SC would 'attempt', to turn a blind eye to this, absolutely yes.

They will never directly address it as they don't want to publicly admit there is a problem with their product.

With the brain trust and capital SuperCell has at their disposal they could 'over time', combat this issue.

---

And you've gain this insight via ?......


warm regards
sneaky

Also, there aren't a lot of these people. Sure, it's really annoying to see a replay where someone is "ch3ating", but at least it's not your full log, right? I'm not trying to defend ch3aters. I think it's low they need AI help to do things you can do yourself. SC should patch it, and I think they should address it AFTER they patch it. It's basically like saying they knew about, and that if you even wanted to try it, it's too late. If they announced it NOW, people would Google about and probably get their hands on it, and thus a bigger problem.

Quote:

---

Originally Posted by sneakymaori

And you've gain this insight via ?......


warm regards
sneaky

---

Dear Friend,

Please supply us with an official media release that confirms both the acknowledgement of the issue as well as a breakdown of the internal control procedures that are/have been implemented in regards to this matter.

It would also be greatly appreciated if you could cross reference the resources used in regards to this issue against projects developed/and in development.

1st the more we talk about it the more people will be curious and attempt to try to find such a software guideline or loophole.

2nd being transparent only help the ♥♥♥♥♥er.

Do you want Supercell to tell US hey this month we try to implement a new function that send a ping every 2 second.

Then the month afterward well sorry it didn't work. The ♥♥♥♥♥er learn about the ping (in the newsletters) and send us false ping. Now we going to use a gordon knot algorithm to try to prevent such thing in the future.

Sorry the public algorithm we publish last month didn't work since the ♥♥♥♥♥er have rapidly developed the anti-algorithm. We are dumbfounded on how they could so rapidly detect our algorithm:rolleyes:.

Quote:

---

Originally Posted by mARCSBUG

Dear Friend,

Please supply us with an official media release that confirms both the acknowledgement of the issue as well as a breakdown of the internal control procedures that are/have been implemented in regards to this matter.

It would also be greatly appreciated if you could cross reference the resources used in regards to this issue against projects developed/and in development.

---

oh wait...

so if they don't publicly admit it, that means they're not doing anything to it?

Quote:

---

Originally Posted by Jomarx3me

oh wait...

so if they don't publicly admit it, that means they're not doing anything to it?

---

You are apparently in violation of the TOS, why are you discussing something that you continually use as a defense?

Quote:

---

Originally Posted by mARCSBUG

Dear Friend,

Please supply us with an official media release that confirms both the acknowledgement of the issue as well as a breakdown of the internal control procedures that are/have been implemented in regards to this matter.

It would also be greatly appreciated if you could cross reference the resources used in regards to this issue against projects developed/and in development.

---

Way to not answer the question, ie, back up anything you said.