Vexx

I'm just going to give the same reply I gave to @TheSupremePatriot asking almost the same thing.

Edit: Also

Bsor is fine. It's a very nice map in my opinion and I'm tired of seeing "remove this map" votes. I don't understand why everyone complains about removing maps when I know when we DO clean the maplist people will just complain that there's not enough maps. I like bsor a lot personally, it has a nice aesthetic and really fits on a trade server, like ours. I say this a lot but, a measurement of "fun" in your eyes isn't exactly a reason to keep or remove a map, the map has 0 bugs or problems that I can see and I would rather see it stay on the server. It's the only map I think we're going to get that has the entirety of Bomb-omb battlefield, and still have spawns fair enough to actually consider it a trade map.

Bsor is fine. It's a very nice map in my opinion and I'm tired of seeing "remove this map" votes. I don't understand why everyone complains about removing maps when I know when we DO clean the maplist people will just complain that there's not enough maps. I like bsor a lot personally, it has a nice aesthetic and really fits on a trade server, like ours. I say this a lot but, a measurement of "fun" in your eyes isn't exactly a reason to keep or remove a map, the map has 0 bugs or problems that I can see and I would rather see it stay on the server. It's the only map I think we're going to get that has the entirety of Bomb-omb battlefield, and still have spawns fair enough to actually consider it a trade map.

Bsor is fine. It's a very nice map in my opinion and I'm tired of seeing "remove this map" votes. I don't understand why everyone complains about removing maps when I know when we DO clean the maplist people will just complain that there's not enough maps. I like bsor a lot personally, it has a nice aesthetic and really fits on a trade server, like ours. I say this a lot but, a measurement of "fun" in your eyes isn't exactly a reason to keep or remove a map, the map has 0 bugs or problems that I can see and I would rather see it stay on the server. It's the only map I think we're going to get that has the entirety of Bomb-omb battlefield, and still have spawns fair enough to actually consider it a trade map.

A: 10
M: 10
+1 very active, is also my waifu.

A: 10
M: 10
+1 very active, is also my waifu.

I'll stay neutral on this. While Reiki has improved, they still show signs of passive-aggressiveness when confronted or when they get angry at something.

I'll stay neutral on this. While Reiki has improved, they still show signs of passive-aggressiveness when confronted or when they get angry at something.

Over time, people would then start to instantly press 3 instead, they're always just going to push the first button that has an option just to get the menu to go away.

I'll stay neutral on this. While Reiki has improved, they still show signs of passive-aggressiveness when confronted or when they get angry at something.

I'll stay neutral on this. While Reiki has improved, they still show signs of passive-aggressiveness when confronted or when they get angry at something.

I'll stay neutral on this. While Reiki has improved, they still show signs of passive-aggressiveness when confronted or when they get angry at something.

So apparently staff doesn't know how warnings work on the servers based on recent incidents, so I'm going to go over how warnings should be issued.
 
A normal warning: You tell the player through All Chat (which is just a single @ before your sentence in public chat) OR Voice what they are doing wrong. If the player does not acknowledge when using voice, give them another warning through All Chat, before punish them for their first punishment.
 
Quoted from the staff manual: Warn, then slay/mute (sometimes optional), then kick, then ban [WSKB]
Players should know why they were punished
When you punish a player, make sure to let them know why they were punished so they can improve.
Example: Person Y freekilled person X, you slay person Y and respawn person X. You need to tell person Y why they were slain. Something like "You were slain because you freekilled person X." works.
 
How past warnings work: If you warn a player for something in the past and they do it, don't immediately jump to banning them. Depending on the amount of time it has been since their last warning for the incident, you may need to warn them again to remind them not to do it. 1 warning per week is good enough for someone who is repeating the same offense. If you feel the person has committed an offense too many times you can jump to a kick.
 
Now keep in mind, you can skip warnings for certain things. An example of this would be: Hacking, micspamming music, exploiting, etc. Generally if you are unsure what to do about a situation, feel free to ask a fellow staff member. If you're still unsure, please look at the staff manual here: TF2 Staff Manual (Everything you need to know!)
 
@Bello @Sesh @mrnutty12 @Rejects Feel free to add on to my post if you feel I left something out.

Personally I think this entire idea is a bit silly to really be taken seriously. People could already gamble their credits/items before, so there's really no need for this thread. You shouldn't gamble without staff online as, people can run away/scam others through gambling. Personally, I think it's fine for you to set up games and whatnot, but you can do that on your own time, no point in making this thread. The Trade Gaming History server is almost always full of people, if you want to do events on there just ask people to join. Another thing, even though yes we have permission from MassCC to use their map, it just doesn't feel right to me to be using their map for gambling purposes. If there are specific events you would like to host though, like a giveaway, feel free to message a staff member to help you.

So apparently staff doesn't know how warnings work on the servers based on recent incidents, so I'm going to go over how warnings should be issued.
 
A normal warning: You tell the player through All Chat (which is just a single @ before your sentence in public chat) OR Voice what they are doing wrong. If the player does not acknowledge when using voice, give them another warning through All Chat, before punish them for their first punishment.
 
Quoted from the staff manual: Warn, then slay/mute (sometimes optional), then kick, then ban [WSKB]
Players should know why they were punished
When you punish a player, make sure to let them know why they were punished so they can improve.
Example: Person Y freekilled person X, you slay person Y and respawn person X. You need to tell person Y why they were slain. Something like "You were slain because you freekilled person X." works.
 
How past warnings work: If you warn a player for something in the past and they do it, don't immediately jump to banning them. Depending on the amount of time it has been since their last warning for the incident, you may need to warn them again to remind them not to do it. 1 warning per week is good enough for someone who is repeating the same offense. If you feel the person has committed an offense too many times you can jump to a kick.
 
Now keep in mind, you can skip warnings for certain things. An example of this would be: Hacking, micspamming music, exploiting, etc. Generally if you are unsure what to do about a situation, feel free to ask a fellow staff member. If you're still unsure, please look at the staff manual here: TF2 Staff Manual (Everything you need to know!)
 
@Bello @Sesh @mrnutty12 @Rejects Feel free to add on to my post if you feel I left something out.

Sesh's post explained it quite well:

You can not blame a user for everything, staff incompetence and unwillingness to take a few seconds to type is sometimes the problem.

You can't constantly blame a player for choosing to keep their voice chat/sound off. Once again I'll make this clear. Staff should always give a clear warning through text chat. There is a reason why you have handy tools such as all-chat and the multiple menu/pop-up commands.

You can't constantly blame a player for choosing to keep their voice chat/sound off. Once again I'll make this clear. Staff should always give a clear warning through text chat. There is a reason why you have handy tools such as all-chat and the multiple menu/pop-up commands.

User will be unbanned.
Closed.

A player having their volume off is a completely justifiable reason when staff refuses to give proper warnings through text chat at least once before banning them. As for the colorized while friendly thing, you shouldn't instantly start pointing fingers calling it "trolling". It's a donator perk that the donators have decided to use to get around an annoying quirk with the friendly plugin, which is the transparency. We're currently going over the colorizing while friendly thing in private and will let everyone know when we finish up there.
 
Also just to clarify, I made a PSA going over how to give a proper warning: Staff Psa: Issuing Warnings. This isn't the only incident I've had to go over recently and I think now would be a good time to get it out there.
 
Now as for the protest, @Bello @mrnutty12, we going to unban him or not? His ban is almost up and @Sesh has already agreed.

This thread is really disappointing.
Rejects has done great work, really humongous amounts of work and he is definitely more experienced when it comes to server stuff than me.
I mean, we got VSH back and it's actually really great, all thanks to Rejects.
But Rejects, I really don't know what's going on in your mind. It is beyond me why you'd go back to abusing after everything that has happened.
Rejects does care about the clan, very much, I believe, there's no doubt about it. -> Why else would he do all the work for our FF2 server.
We spoke for a good two hours about the incidents that happened previously on TeamSpeak, you seemed like your position really meant something for you and that you wouldn't wanna lose it.
You promised not to do it again, but here we are.
I'm not even mad, angry or anything similar, just a little disappoined in Rejects.
I'm not sure if he should be demoted, yes, he has really fucked up, but I, myself, couldn't even get to his level of server experience.
I really don't think Rejects does realize what he's doing. Whenever he does things like that, it's probably just some harmless fun for him which I can't blame him for.
>but bello, does that justify it!!! :rage: :punch: :mad: @Goblins
No, it does not. In no way am I implying that it was justified whatsoever.
Really, I'm quite unsure at this point what to do. I personally wouldn't want Rejects demoted, but if you're looking at everything from an unbiased perspective, you have to admit that it's pretty bad.
No +1 or -1 from me yet, just my thoughts so far.

You can't constantly blame a player for choosing to keep their voice chat/sound off. Once again I'll make this clear. Staff should always give a clear warning through text chat. There is a reason why you have handy tools such as all-chat and the multiple menu/pop-up commands.

So apparently staff doesn't know how warnings work on the servers based on recent incidents, so I'm going to go over how warnings should be issued.
 
A normal warning: You tell the player through All Chat (which is just a single @ before your sentence in public chat) OR Voice what they are doing wrong. If the player does not acknowledge when using voice, give them another warning through All Chat, before punish them for their first punishment.
 
Quoted from the staff manual: Warn, then slay/mute (sometimes optional), then kick, then ban [WSKB]
Players should know why they were punished
When you punish a player, make sure to let them know why they were punished so they can improve.
Example: Person Y freekilled person X, you slay person Y and respawn person X. You need to tell person Y why they were slain. Something like "You were slain because you freekilled person X." works.
 
How past warnings work: If you warn a player for something in the past and they do it, don't immediately jump to banning them. Depending on the amount of time it has been since their last warning for the incident, you may need to warn them again to remind them not to do it. 1 warning per week is good enough for someone who is repeating the same offense. If you feel the person has committed an offense too many times you can jump to a kick.
 
Now keep in mind, you can skip warnings for certain things. An example of this would be: Hacking, micspamming music, exploiting, etc. Generally if you are unsure what to do about a situation, feel free to ask a fellow staff member. If you're still unsure, please look at the staff manual here: TF2 Staff Manual (Everything you need to know!)
 
@Bello @Sesh @mrnutty12 @Rejects Feel free to add on to my post if you feel I left something out.

So apparently staff doesn't know how warnings work on the servers based on recent incidents, so I'm going to go over how warnings should be issued.
 
A normal warning: You tell the player through All Chat (which is just a single @ before your sentence in public chat) OR Voice what they are doing wrong. If the player does not acknowledge when using voice, give them another warning through All Chat, before punish them for their first punishment.
 
Quoted from the staff manual: Warn, then slay/mute (sometimes optional), then kick, then ban [WSKB]
Players should know why they were punished
When you punish a player, make sure to let them know why they were punished so they can improve.
Example: Person Y freekilled person X, you slay person Y and respawn person X. You need to tell person Y why they were slain. Something like "You were slain because you freekilled person X." works.
 
How past warnings work: If you warn a player for something in the past and they do it, don't immediately jump to banning them. Depending on the amount of time it has been since their last warning for the incident, you may need to warn them again to remind them not to do it. 1 warning per week is good enough for someone who is repeating the same offense. If you feel the person has committed an offense too many times you can jump to a kick.
 
Now keep in mind, you can skip warnings for certain things. An example of this would be: Hacking, micspamming music, exploiting, etc. Generally if you are unsure what to do about a situation, feel free to ask a fellow staff member. If you're still unsure, please look at the staff manual here: TF2 Staff Manual (Everything you need to know!)
 
@Bello @Sesh @mrnutty12 @Rejects Feel free to add on to my post if you feel I left something out.

So apparently staff doesn't know how warnings work on the servers based on recent incidents, so I'm going to go over how warnings should be issued.
 
A normal warning: You tell the player through All Chat (which is just a single @ before your sentence in public chat) OR Voice what they are doing wrong. If the player does not acknowledge when using voice, give them another warning through All Chat, before punish them for their first punishment.
 
Quoted from the staff manual: Warn, then slay/mute (sometimes optional), then kick, then ban [WSKB]
Players should know why they were punished
When you punish a player, make sure to let them know why they were punished so they can improve.
Example: Person Y freekilled person X, you slay person Y and respawn person X. You need to tell person Y why they were slain. Something like "You were slain because you freekilled person X." works.
 
How past warnings work: If you warn a player for something in the past and they do it, don't immediately jump to banning them. Depending on the amount of time it has been since their last warning for the incident, you may need to warn them again to remind them not to do it. 1 warning per week is good enough for someone who is repeating the same offense. If you feel the person has committed an offense too many times you can jump to a kick.
 
Now keep in mind, you can skip warnings for certain things. An example of this would be: Hacking, micspamming music, exploiting, etc. Generally if you are unsure what to do about a situation, feel free to ask a fellow staff member. If you're still unsure, please look at the staff manual here: TF2 Staff Manual (Everything you need to know!)
 
@Bello @Sesh @mrnutty12 @Rejects Feel free to add on to my post if you feel I left something out.