Echo Leader
Posts : 985 Join date : 2011-05-15 Age : 32 Location : Columbus
| Subject: Recruitment Policy (Under Construction) Mon Oct 03, 2011 7:27 pm | |
| Recruitment PolicyWhat are your requirements?
- Age is flexible, but we do require maturity. As a general rule of thumb we accept 16+ applicants. We do make exceptions however, and an applicant may play with us (on Teamspeak) for a week before we can deny the applicant based on age.
- KDR is also flexible, but for a competitive oriented player we require a 1.4 KDR or above. If you would like to participate competitively and fall below the mark, you will be playtested before you can be accepted into the clan.
- A mic and Teamspeak 3 is absolutely required. You MAY be let in upon you being in the process of aquiring a new one, but it is very rare. You don't have to be on Teamspeak 100% of the time while you're playing, but it is strongly encouraged and you will not be allowed to clan war without being in Teamspeak.
- You must be a Master Seargant or above to be accepted. No exceptions unless you are specifically referred to the clan on behalf of a current member.
- You must also never have hacked or glitched. Being CBL dirty will be an automatic denial, NO exceptions. If you were wrongly placed as CBL dirty, contact them to try and clear it up.
How do you handle new recruits?All new recruits are given a 7-day probation period where we watch to see if they fit in with the clan, are active, and represent Dead Pixel in an upholding manner. If there are any problems or concerns within those 7 days, we reserve the right to remove you from the clan at any time, no questions asked. For those who fall below the age requirement or the KDR requirement (while wanting to participate in clan wars), that probation period is extended to 14 days. | |
|
Echo Leader
Posts : 985 Join date : 2011-05-15 Age : 32 Location : Columbus
| Subject: Re: Recruitment Policy (Under Construction) Tue Feb 25, 2014 7:21 pm | |
| Due to the rebranding of Dead Pixel, this post no longer applies. This post will be updated before the March meeting on 3/28 | |
|