Thread: What is a "team player"?

I may not be an active CS:Ser but I am an old school teamplayer from the BF days as some other notables are. The way I've always viewed teamplay is "Go for the objective or die trying". Ideally this means figure out what you are supposed to do and do it in the best way possible to win victory. Sometimes what the objective that is communicated is the wrong call at that time and if that ever happened people are always free to communicate what they think will help the team with the overall victory.

It is never blindly following the call or listening to the squad leader, it is trusting what you hear and making sure the team knows if you disagree and why your idea works. If you want to go against the grain all you have to do is communicate it and the team will either support you or shut you down. What makes a teamplayer is how they communicate with the team and how they react to doing what they need to do to win the game for the entire team. Never thinking about themselves and doing whatever they can to help everyone else.

"Go for the objective or die trying"


I remember quite the shitstorm going down a few years ago because of that philosophy.

And let's not forget, join T side even when it's going to be hard to win as a T. Take responsibility for making sure that the quality of experience is what people expect by ensuring that T side is competent every map. It doesn't have to win, just be competitive. This applies in the daytime and not just at night when the server is full of regs. Given that the constant stream of new players generally likes to play CT more than T (because it's easier to win on and more fun when you are losing) if you want to consider yourself a real reg/reservist here you should have more T than CT joins.