Big Brother Aquanim, Speaking about spectator problem

This post has been downvoted below -5 and collapsed, click here to expand

Be glad at least some people don`t have you on ignore.

First off after reviewing the game:

kelaze purposefully omitted the fact that they were the target of this "admin abuse" and overdramaticized this event. Having wasted a good 10 minutes reviewing the replay here's a hot poker:

The conversation referenced in this post is the following:
[f=0001183] [kelaze (replay)] I predict east win
[f=0001489] <Aquanim> no more spec talking mkay
[f=0002439] [kelaze (replay)] why, Aquanim? this were not violate the rule
[f=0002681] <Aquanim> i mean it kind of did
[f=0003203] <Aquanim> you probably wouldnt have said that if they plopped 10 air
[f=0003534] <Aquanim> or all plopped south or something
[f=0004011] [kelaze (replay)] of course that I wont do spec cheating
[f=0005132] [kelaze (replay)] what is matter if I say someone team will wins at starting point? they were gettting starting
[f=0005855] [kelaze (replay)] that is awful.
[f=0006006] <Aquanim> STOP. TALKING.

Note that Aquanim was a player in this game and had every right to tell kelaze to stop. Section 1 of the CoC states:

quote: Spectators can chat with players, offering advice or conversation, in some of the more casual game types. Avoid excessive public commentary, revealing hidden information, and do not heckle. If a player wants to play without interruption then the spectators should respect this desire and cease using public chat. Feel free to discuss the game in spectator chat (hotkey Alt + Enter). Check for the a: or s: in front of your chat message.

Note the lack of an actual threat used here (while I acknowledge that Aquanim is an admin and there's an IMPLIED threat, no actual threat was given out). During this conversation, it caused a minor distraction:
* Ontheheavens decided to chime in with aggressive remarks towards Aquanim. (this probably is mute worthy given their past behavior)
* @123132123132123 reacted to the initial comment with "no we win"

This is clearly having an impact on game state. Spectators are expected to not impact game state (ie: speccheat is one method of impact). Aquanim attempted to explain in good faith that players read into comments like that by analyzing the motivation behind it (ie: "they must have something wrong somewhere, so I should push aggressively").

We do not need your ESPN commentary in all chat. If you want to make comments like that, do so in spec chat. You're not being asked much, just to actually respect other players' ability to play a game uninterrupted. You should not be engaging players or making engaging conversation without a clear purpose such as 'giving technical support'. Consider the "necessary" test: is this comment necessary to make over all chat? Does this comment help anyone? Both of the answers to this were no, thus you are in the wrong here.

Furthermore, overdramaticizing posts with jargon like "big brother" is childish, unnecessary, uncalled for and only makes your intention look like you're trolling. Omitting the fact that you were the target here is pretty suspicious too.

quote: it is indeed my impression that admins of this place often behave plainly offensive and in a "big brother" manner.

quote: Jesus, it's a good thing that at least in Teams All Welcome the insufferable bores like one above have died out. Good riddance I say.

Your continued presence in this community given your long history of abuse combined with crass comments like this continuing to happen are proof enough that admins are very lenient.

In summary, a spectator chatting after being asked to stop by a player is violating the rules. It doesn't matter why the player asked them to stop.

If AFK Detector were not malfunction, at this state I won't have to conflicting admin and no such of the thread and joined the game.
This is be 1 year or 2 years problem were always stay in here:
https://zero-k.info/Forum/Thread/25797

And that problem in reference thread still exists now.

Shaman, show all of the chat logs if you could. it is no fun to highlight/cut a part of chat log then speaking something about it.

First, someone want me to predict who wins, then I looking on player list then guessing, so I say predict east win, then admin involved until he was yelling plus "Last warning", were feeling to me being threatened. And why would I do looking east fac and wast fac and compare with to predict who wins? that is explicit spec cheat.

After this thing later so I know

quote: In summary, a spectator chatting after being asked to stop by a player is violating the rules. It doesn't matter why the player asked them to stop.

EDIT: not all people were expect to they read out the newest code of conduct and someone probably didn't read like me.

We've decided to forum ban Ontheheavens for a week. He does what he does here basically every time, and it's getting old. He's been doing this for at least a year (yes, we're pretty lenient) but I think by now we can safely say he's not going to improve without prompting any time soon. The ban is only a week, but personally I don't hold out hope for an improvement by the end of it.

Yes, but rarely in big team games.

I would really miss the ability for spectators and players to chat. Obviously spec cheat pops up occasionally, but being able to continue conversations from the lobby in the game is quite nice and I think it is good from a social perspective.

Possibly the guidelines could use the addition that only helping a player with technical issues is a valid reason for a spec to use all chat, provided that the player to be helped asked in all chat themselves and that no information about the game state is revealed.

Note that if a player has problems with the game and asks for advice in team chat only, this might indicate he does not want the other team to know he has trouble. There is reason for such caution as an opponent might decide to use the distraction to gain an advantage: For example using an attack that would require intense micro to cope with may have a higher success chance if the defender just accidentally ctrl-tabbed to overview zoom and does not know how to undo it.