Gator

Basic Supporter isn't a thing anymore. Already a perk for any game that supports it.

Hello everyone, We have a very special promotion for you all today. In support of Labor Day, we wanted to show recognition for one of our hardest workers. I'm pleased to announce @kabLeis the proud owner of a $5 gift card to Subway! And he's now Director. Their new responsibilities will include: Support/build/fix servers Approve admin applications Set up new Admin and Supporter access Issue admin warnings/punishments Keep the community updated of any changes Final say in all admin disputes Plan for growth (website/servers) Support forum/plugins/logos Review and implement community suggestions Promote/demote server admins Handle admin complaints Handle disputes among fellow admins Be a role model to all admins/setting by example Collect donations and manage subscriptions Manage the website, forums, and bansite Manage staffing and responsibilities ... anything else that needs to be done

Hello everyone, Please welcome Starlegendgod, Sully, touchy, Phoenix_, john jones, and Dong to Community Adviser! Their new role includes: Advise the higher staff on important decisions Handling player complaints and issuing bans Moderation of the forum Give awards to members on request Keep servers clean from rule breakers Issue warnings/kicks/bans Screenshot/demo proof for permanent bans Request permanent bans via on the forum Post in-game server problems on the forum Help in any way to make the servers fun Congratulations!

Please welcome to following individuals to their new or old roles! To Events Manager we have Zero Two! Their new responsibilities will include: Manage Events Team Organize, plan, and run events Manage/Promote special events on our servers Manage and monitor gaming tournaments (ie. SGSL) Make sure servers are ready for all special events Schedule events to fill servers in need via the steam community Work with the Administrative Team to create events that cater to community interests To Server Manager we have Dominic! Their new responsibilities will include: Verify that servers are operational Reboot dead/lagged servers Assist in training new admins Search for new maps for all servers Upload maps to the servers and fast downloads site Edit map lists & rotations To Technical Administrator we have Revenga! Their new responsibilities will include: Fix technical issues that arise day to day (servers/site) Research/manage mods, scripts, and plugins to improve our servers Develop solutions to improve our servers/mods performance Discover and fix exploits against our servers/site Assist in data backup operations for the community's data Assist AT's when problems arise or others are on vacation Lastly, to Director we have Hawks! Their new responsibilities will include: Support/build/fix servers Approve admin applications Set up new Admin and Supporter access Issue admin warnings/punishments Keep the community updated of any changes Final say in all admin disputes Plan for growth (website/servers) Support forum/plugins/logos Review and implement community suggestions Promote/demote server admins Handle admin complaints Handle disputes among fellow admins Be a role model to all admins/setting by example Collect donations and manage subscriptions Manage the website, forums, and bansite Manage staffing and responsibilities ... anything else that needs to be done

I personally really liked the old rank structure we had before breaking off into teams. It was easy to identify where each rank was in the hierarchy and who to go to for particular issues. Right now you can be a CA (below SM), but also be an IA (above/equal to SM) which doesn't make sense to me. Looking at you two @kabLe @Hawks It also gave a significant incentive for promotions. The responsibilities and powers that came with going from SA to CA to AO made it much more worth the effort it took for the promotions.

I'm glad we had the opportunity to be on the board together @John and more so to be able to become better friends. Please keep posting updates on your ricer Elantra

The site is optimized for mobile use. An app is not necessary.

I think you're both misunderstanding how we handle harassment situations here. It's impossible to define a stance on every form of prejudice which include homophobia, bigotry, racism, and many more. These are all forms of harassment though, which is why our stance on harassment is clearly defined as not being tolerated. On paper specific or formal rules seem like a great idea, however they don't work in practice for multiple reasons. It's impossible to create an exhaustive list of slurs which moots the purpose of a list. An example of this can be seen with the amount of racial slurs out there. If you're too detailed you risk exclusion and if you're too vague, you just end up with a blanket harassment rule anyway. Rules aren't flexible, and you need flexibility in this environment. This was a primary reason for the change in our racism rules. When we had strict racism rules, it was pretty much a joke because someone who isn't racist and a slur in racist context (i.e. doing karaoke on a song) was labelled as a racist and could be banned. Like I said above with creating specific rules, cracking down or pushing server administrators to get involved doesn't work like it does on paper. Obviously there are exceptions, but for the most part our server administrators are pretty much kids. Expecting them to confront these situations would be inappropriate. This isn't to say they can't though as it's within their reach to enforce. Grow the fuck up. We keep repeating to report harassment (which it is), because people like yourself downplay the importance of it. A chunk of this community would have likely been banned at some point if we just punished for every instance and not received context that reporting provides, regardless if they were joking or not. It's especially important to emphasis for when it all starts as jokes and fun between friends and evolves into something serious. Until everyone knows they have a way of getting help (victim or bystander), it's hard to handle the issue effectively.

Not too shabby. Too bad you couldn't hit 500 hours though. Maybe next time.

Hello everyone, To begin with, I would like to send a big thank you to Black Rain for all of her hard work over the years. She's been instrumental in leading the Events team and organizing raffles and will be greatly missed. She will now be taking on a well deserved retirement as a Veteran! Good luck @Black Rain with med school and don't come back till you're Dr. Black Rain! Next up has been a long time in the making. This individual has stood out ever since they joined the admin ranks and continues to impress every day. Please welcome TheZZL to the Board of Directors! We're very excited to have this board and look forward to seeing where @TheZZL takes us! TheZZL's responsibilies will include: Support/build/fix servers Approve admin applications Set up new Admin and Subscriber access Issue admin warnings/punishments Keep the community updated of any changes Final say in all admin disputes Plan for growth (website/servers) Support forum/plugins/logos Review and implement community suggestions Promote/demote server admins Handle admin complaints Handle disputes among fellow admins Be a role model to all admins/setting by example Collect donations, manage subscriptions, and pay the bills Manage the website, forums, and bansite Manage AT staffing and responsibilities ... anything else that needs to be done Congratulations you two!

Thank you for all the memories buddy. Still owe you VP...

Easy +10 hp. Just needs a racing stripe now.

Congratulations!

TheZZL, VP Puppet Master

Caution is a trained killing machine, I'd never stand a chance.

The real slaves are @Liam Brown and @Nishok with @fantastic working his way into it. The BDs just take the credit.

We still manually update servers (the process is easier than it was when you were SM too). Automatic updating would be convenient, but updates come at inconvenient times usually. By doing it manually, we can control when the update is applied that way we aren't shutting down a full server.

You're lucky I have to work during this.

Correct. We'll be setting this up over the next day or two. Yup. However, everyone who was JA will still need to wait until they reach 3 months of admin and submit what was the "SA Promotion" form in order to received the extra permissions that came with SA.

Hello everyone, As I mentioned in a reply a few days ago regarding changes in the admin application process, the Board has been busy discussing some changes to the community. Since our inception, Steam-Gamers has been a Counter Strike community. We've dabbled into some other games, but overall, Counter Strike has been our home. Because of this, our community has been built around being a Counter Strike community and that is reflected through our rules, policies, and rank structure. Within the past year, we've expanded from being just a Counter Strike community and have brought in TF2, Squad, and most recently, Rust. As we've expanded into these new games and look forward to expanding into more, we've found that the way we have some things setup and the way we do some things doesn't always translate between games. In order for us to fix this and adapt, we have to make some changes. The first change we made was to the admin application voting process. This of course isn't it's final form and will be tweaked as we discuss more and see how this change does. The second change is to discontinue the Junior Admin rank. The difference between JA and SA has always been very limited, revolving mostly around a select few "fun" commands for CSGO admins that were changed internally on the sourcebans side anyways. As Rust and Squad do not have any differentiating commands and simply only need one admin rank it is sensible that we revert back to only having one admin rank. In this way, we can make the function of the Server Admin rank virtually the same no matter if they are a CSGO, Rust, or Squad admin. We will still reserve the select fun commands for CSGO admins who have been around for 3+ months, we just don't need a rank to do so. This is in part to help us manage the community as it grows and in part to make the community more easily accessible and understandable to new people looking to get involved.

You don't have to worry about getting a future position anymore, so that won't be a problem.

Unfortunately some who do make solid input in votes will be "punished". Restricting to a case-by-case basis isn't a feasible option as there isn't a fair way of making a criteria to determine who would get it and you'll have members who feel they should be included but aren't. Doing a blanket change is the most fair way of implementing this change. Why would they? Team Managers don't have authority in our admin structure. To quote another Board member from when we were discussing this, "it's like the supervisor of the bakery department determining the inventory for the meat department". As I mentioned in my reply to deli about this, having a whitelist of people who can vote and aren't CA+ wouldn't be fair as it'd just be personal opinions on who would be eligible. If we favored just supports/reapplies from CA+ anyway, it'd pretty much be this system anyway. This is a great example of making a judgement without the facts. We're not just changing who can vote and calling it a day. We're well aware of how many CA+ vote and how much they play/what servers they play. We've communicated our expectations to the CA+. Again, we've communicated our expectations. With ~30 CA+, there shouldn't be apps that receive 3-5 replies. If that happens, we'll notice and it'll be fixed. This has been long discussed. It was just a coincidence that Rust and Squad had a similar process to this beforehand. As I've mentioned above, we've made server activity expectations clear. We're well aware that this system wouldn't be effective if changes weren't made to CA+ server activity. If there is something that we absolutely must know, it can always be PM'd to an IA or BD. I'm also curious what you would consider "something serious can fly over your heads" as I can guarantee we research each applicant enough before approving an app to know if there is something serious. - - - - - - - - - - - - - - - While I expected some people to be unhappy, I wasn't expecting so many, so I should have mentioned in the OP that this is the first step towards some further changes that are still be discussed. As those changes are finalized and pushed out, it'll be clear why we've decided to move towards this voting system.

Hello everyone, After some discussions, the Board has decided to change the way voting on admin applications works. Previously voting was public and anyone could vote. In this new change, only CAs and SMs can vote. Applications and votes will still remain public. If you have any questions, please feel free to comment here.

Fantastic is our guiding light, so yeah it was pretty dark. Never say never my friend