(11-04-2014, 02:28 PM)DarkEvil Wrote: 9.2 - ACG's policy with regard to cheating:
* 9.2.1 - Cheating is prohibited, and ACG classifies cheating under two categories - intentional game-altering behavior, and non-intentional game altering. Anyone caught cheating will be subject to a ban for the next Gladiators/Go league (not including the current cycle)
* 9.2.2 - Game-altering behavior includes but is not limited to: extreme lag, constant spikes, a series of spikes or a prominent spike during a critical play, or godmode-like behavior (damage immunity).
9.3 - Any player or clan found to be exhibiting game-altering behavior is subject to protest.
* 9.3.1 - ACG will review accusations of game-altering behavior on a case-by-case basis. The only difference between intentional and non-intentional game-altering behavior is, obviously, if the league has sufficient reason to believe a player or clan (or both) had intent behind the exhibited behavior.
* 9.3.2 - *Sufficient reason can exist without concrete proof*. Things such as behavior, patterns, circumstantial evidence, player credibility, testimony as to the nature of the occurrences, etc., will all be examined and the league will decide whether or not there is enough reasonable doubt as to A) whether significant game-altering behavior in fact occurred B) whether there is strong enough likelihood that there was intent behind it.
9.4 - If a player is exhibiting any kind of game-altering behavior, he is expected to sub out immediately. One of the refs should notice it and ask the player to sub out immediately, and if not the opposing clan may urge the ref(s) to observe said player and request he sub-out. A clan's captain is also expected to urge his teammate to sub out if he starts spiking or exhibiting game-altering behavior, because his clan will be held accountable for this player's game-altering behavior, and clans are expected to have any players sub-out if the majority of other players in game including the refs notice this (sometimes a player is smooth on his own screen, but everyone else sees them spiking).
This protest is two-fold. LN is protesting CloudS' (Kweli) spiking in the specific game mentioned above in the title, as we feel it impacted the game in a negative manner. We are also protesting on a larger scale, as this is not the first game he has spiked in, nor has it been the first time it has affected games he has participated in.
Based on the rules above, we feel CloudS spiking falls under the "unintentional game-altering behavior" category. We have no proof it can be labeled "intentional", so we have no desire to argue or make claims regarding that. "game-altering behavior" (to us) has two definitions. There's the simple and more literal definition: any out of place occurrence that directly ALTERS the game in that specific moment. Then the more gray definition: an occurrence that alters the whole gameplay onward (player's decisions, momentum, tempo, etc.) These aren't necessarily one in the same, but they can both stem from the same occurrence. CloudS random, erratic spikes qualify as both, in our eyes.
Now specifically the game at hand. I have watched only the first half of the replay upon writing this, so I can not comment on the 2nd half at this time. From what I have seen thus far, I've noticed 4 or 5 times CloudS spiked. They vary in degree of "how bad" they were, and the impact they had. Most notably, the first spike is the main focal point. Early in the match, with Night and myself top (red) vs Kweli and a 2nd RS, at red base entrance (bridge), CloudS had a large spike. Night and I looked to have a very quality rape on Kweli as he pressed onto the bridge. Night threw a spread/bouncy at him (he ate it on our screen) just as I threw a complimentary nade (which appeared to hit him). He then spiked away from all of that (taking no damage), almost to the other side of the bridge entirely, while also throwing a nade at me in a very tight spot along with a nade from his teammate. This resulted in my death, and then opened a clear path into our base in which they flagged. We were not able to recover. This seems to us to be a clear case of "game-altering behavior", as it clearly affected this moment of the game.
Now in regards to the second defintion of "game-altering behavior", one can not measure how a cap can change the flow of a game, or the way the teams play from that moment on. LN was forced into an early 0-1 hole, and thus had to play an uphill battle to attempt to comeback. We also had to play against CloudS still, knowing his spiking potential still existed, and yes, spikes still did occur that LN had to deal with. This, we feel, alters the way a game plays out because it affects how we, the opponents, play from that point on. Put LN aside, no players should be subject to these type of events in-game.
Which brings me to my next point. Regardless what the result of this protest is, we all know CloudS spikes and does so often. This isn't new. LN surely isn't the first team to endure this, nor will we be the last if he is allowed to continue to play under these conditions. I'm all for including everyone, but not if it is having this sort of impact in-game. The integrity of the games comes first.
