Change Protocol regarding F-spec and how to deal with AFKs. Specifically, H3ll4flush

@H3ll4Flush what do you think

 

Paci, I love ya, but you're missing the point
This has been a problem for *years*. If it's a fringe case, it's the single most destructive fringe case this server has. Xpro might be being overly aggressive, but you're the inverse of that, minimizing and being dismissive to the longstanding issue that everyone hates. Which you might not realize you're doing, but keep in mind your first reaction to having this well-known issue pointed out to you was basically 'OK, but how, we already deal with this, here is how' and the other staff reactions haven't been much better. Which might entirely be my fault for not explaining it properly, but it is frustrating.

Keep in mind, staff don't experience this problem anywhere near the same as any other player. When a staff notices this problem, they can deal with it at their leisure. It never seems like a problem to them. When a player notices this problem, they can only hope that a staff will pay attention to them and deal with it. It creates a blindspot that most staff can't realize they have, because why would they?

 

AFK players smell bad and don't deserve this level of protection. I will always break this rule and risk a ban to kill them, mods can lick my entire cock and balls

 

I haven't missed the point, it just feels like your suggestion isn't "make fspec mandatory" its "please deal with hellaflush". I would rather focus on the broader point and get away from hellaflush, because it isn't very productive. I'm more interested in what we do next time, and i'd suggest just allowing moderators to fspec people if they are afk for more than a round or two, and to punish players further if they are constantly going afk randomly. Best way to do that? Warnings, kicks, or bans, based on an admin's discretion.

Do you disagree with me? What would you actually propose?

 

You're somewhat correct, but I'm not exaggerating when I say flush is the incarnation of this problem. Whatever solution we apply to solve his AFKing will solve the root of this problem. Further changes of protocol could further enhance the general player's experience, but the direct problem is players that are persistently AFK.

Going a little off what @Orion said (Sorry, missed your post before) I do think something new would be prudent. It's niche, unusual, and very specific. The way to address it while retaining a player-friendly environment requires completely different rules than those meant to deal with malicious players, because it would be so rare to find someone maliciously AFKing.

Step 1- F-spec. If any players mention that the target has been AFK for multiple rounds/minutes, staff are allowed to use discretion to bypass warnings.
Step 2- Kick. If the target has to be F-spec'd multiple times in a session*, then kick them with a warning message not to continuously AFK. To retain maximum players, I think it would be prudent to repeat step 2 indefinitely (With exceptions listed below). The kick is also a way to tell point-farmers fuck off for awhile and let people play.
Step 3- Ban. If the target has to be kicked multiple times in a session, they receive a short global ban. An hour or so, like a karma ban. Just a 'Hey, finish up what you're doing before playing'. And these bans should expire fast- Even a few weeks would be fine. The reason why it's global is because no matter what server they go to, they've proven themselves an immediate detriment to everyone's player experience, just by circumstance.
Step 4- Longer Ban. If someone racks up multiple AFK bans in a short period of time, even if they're not doing it maliciously, they're still a detriment to the server. I'd say a week, globally. And a week might seem harsh, but consider how a mass RDMr will typically effect, at most, the individual round of maybe a dozen people, a few times. A mass AFKr will effect possibly hundreds of rounds, for everyone- The detrimental effect is staggeringly larger (I hope I worded that explanation correctly)
*Session as defined by whatever the staff team want to define it as.

The thing about AFKing is that we all do it at least a little, and the exceptions to 'all' prove the rule. if you're going to the bathroom, popping something in the microwave, grabbing a drink, or taking the dog out to pee, or whatever- It's such a short amount of time that there is no way of telling if a round will pass or not in your absence. I start out rounds AFK all the time, though I'm usually back before I'm missed.
Most AFKing isn't malicious, or even intentional. To maliciously AFK takes way more effort with way too little reward than most trolls would tolerate. But the worst thing in a TTT game is dead time. Where nothing happens, and people have to wait for minutes on end. The only thing an AFK can produce is dead time, and especially if conditions line up poorly, people can end up waiting as much as playing due exclusively to an AFK. Getting rid of AFKs is not something that draws players in, but it is one of the best ways to retain players who are already there, and that's something SGM really needs.

 

Very interesting

 

I wrote about this a month ago but isn't the server supposed to automatically spectate someone if they haven't put any inputs in for 3 rounds or so? I know I've seen the automated warning multiple times, but it's never consistent. The main problem here seems like the auto spectate thing is broken. Also, fuck AFK people I don't even do the UnIded body thing if I see someone AFK for over 4 rounds or so I just kill them when I see them because I know the server nor staff don't often do anything, and I doubt they're going to report.

Waiting to move a player whose been afk for 4 maps or so to delay is dumb to me. The longer you keep an AFK player in the pool of players the more unbalanced the game is. The AFK is now the only detective and now there's no health stations. Your only T buddy is the guy whose been AFK for the entire map. Waiting until that AFK player gets traitor and is the only traitor left takes so long and takes away from the game

 

Because I've already brought this up back here https://www.seriousgmod.com/threads...-most-recent-reports.57637/page-2#post-619562 with the same sentiment, went to lordy, went to highwon.

 

No hijacking! There is a lot of overlap, and I do think there is a few critical differences (Namely intent) But for the most part the steps I listed

Would also cover excessive delays, with some modification. The differences though are important enough that we shouldn't dismiss them outright- Intent is very important to consider. I 'unno though, that's just my take on it.

 

Cool, if you're AFKING on a populated server and affecting legit players, you are kicked. If you want to be a better pointfarm, ask me for my ethical python script that joins the most populated server IF there are less than 30 players on, so that I never hurt legit players, and I'm always repopping whatever server has the most players on. Stop being scared of a single players feelings and focus on the people PLAYING THE GAME.

 

I did that for an extremely small amount of time because I learned you earned points in specmode or they added that. I've pointfarmed thousands of hours probably over 10k and never affected players, get off me.

 

I just rdm h3llflush if I saw he was afk the round prior, works pretty well in stopping him delaying it's not rdm if it improves other players experiences

 

I love my energy bill being twice as expensive because I wanted some points on sgm.

 

Ban him for intentionally circumventing the fspec system, intentionally AFKing without putting himself in spec. There is no advantage to being in the round while AFK since spectators get points, he probably has enough points to buy everyone's printshop items anyways. It's an intentional detriment to the community. It's a rare enough situation where the rule doesn't need to be in the books, just say it's admin discretion to ban for constant intentional delaying, intentionally avoiding spectator while AFK, and toxically harming the community.