IanDresari
05-02-2012, 05:04 AM
Hey!
So lately I keep receiving GM warnings for avoiding AFK detection (count: 2).
Both warnings resulted from games that were clearly lost for some reason (meaning chance for turnaround was below 1%) but the team would not concede but rather drag the game out as long as possible.
Now this puts me in a trilemma where you have to choose one option out of three bad ones:
1) keeping on playing an feeding until the base is destroyed; which is not fun, makes me rage and ruins my stats
2) going AFK and receiving a leave
3) avoiding AFK detection and risking a suspension
So I know S2's stance towards this is choosing 1) or 2), but 1) is not a pleasant choice and 2) is not sustainable in the long run.
I would estimate that the distribution of my choices when in the trilemma is 80%-5%-15%, simply because I can't just leave every 15th game or however often this occurs. So if you want to keep your leave percentage low and not risk getting above the threshold, you are left with choices 1) and 3).
Now with the upcoming changes to concede vote times and S2's stance towards 1 or 2 players holding a team hostage by not conceding, I question if it is in S2's interest to tell those who file RAP-reports for avoiding AFK detection, where the AFK detection avoiding is caused by said players, that they were right to do so and have the right to hold the other players hostage, forcing them into the trilemma above.
The upcoming changes to concede vote times are the first step towards getting rid of this trilemma, but it still grants 2 or more friends the power to drag out a game as long as they want.
What do you think is the right choice when you are in this situation?
Can you think about any way to get rid of this trilemma?
Is it correct to give those players right who caused the problem in the first place and then report for the result of their actions?
So lately I keep receiving GM warnings for avoiding AFK detection (count: 2).
Both warnings resulted from games that were clearly lost for some reason (meaning chance for turnaround was below 1%) but the team would not concede but rather drag the game out as long as possible.
Now this puts me in a trilemma where you have to choose one option out of three bad ones:
1) keeping on playing an feeding until the base is destroyed; which is not fun, makes me rage and ruins my stats
2) going AFK and receiving a leave
3) avoiding AFK detection and risking a suspension
So I know S2's stance towards this is choosing 1) or 2), but 1) is not a pleasant choice and 2) is not sustainable in the long run.
I would estimate that the distribution of my choices when in the trilemma is 80%-5%-15%, simply because I can't just leave every 15th game or however often this occurs. So if you want to keep your leave percentage low and not risk getting above the threshold, you are left with choices 1) and 3).
Now with the upcoming changes to concede vote times and S2's stance towards 1 or 2 players holding a team hostage by not conceding, I question if it is in S2's interest to tell those who file RAP-reports for avoiding AFK detection, where the AFK detection avoiding is caused by said players, that they were right to do so and have the right to hold the other players hostage, forcing them into the trilemma above.
The upcoming changes to concede vote times are the first step towards getting rid of this trilemma, but it still grants 2 or more friends the power to drag out a game as long as they want.
What do you think is the right choice when you are in this situation?
Can you think about any way to get rid of this trilemma?
Is it correct to give those players right who caused the problem in the first place and then report for the result of their actions?