​SECTION 1

Behavior in TeamSpeak

​

1.1 Class Family TeamSpeak Etiquette

 

      1.1.2 Upon entering the Lobby move to another Channel as quickly as possible.

 

      1.1.3 Announce your arrival upon entering a Channel if possible.

 

      1.1.4 Watch your language, adult language & subject matter when in Open Chat Rooms. We are a diverse group that includes children. Subjects to be avoided include but are not limited to politics, religion, sexual orientation and racial discussion as well as current world events that may be controversial.

 

           1.1.4.1 Open Channel Rooms are: ALL Tournament Rooms, Stronghold Rooms, Clan Wars Rooms, Hangout Rooms. 

 

      1.1.5 The Topics listed in 1.1.4 may be discussed in Closed Chat rooms as long as all members are ok with the topic being discussed or debated. If a member is not ok with it, they may leave the channel if they are the minority or the group can agree to stop the discussion.

 

            1.1.5.1 Closed Chat Rooms are: Offices and Platoon Rooms.

       

      1.1.6 Please use Waiting Rooms: – Do not enter an occupied Stronghold, Clan Wars or Tournament Channel unless invited in – If you need to speak with an Officer in their office when it is occupied by more than one person move to the waiting room and “poke” the Officer. Wait for them to move you into their office.

 

      1.1.7 To view material posted in an Officer's room there is no need to enter the office. All you need to do is click on the Channel and the available content will show in the description panel.

​

1.1 Respect:

All members are to be treated with the utmost respect. We will not tolerate any type of bullying or harassment in this clan or between clans. If you have any issues between clans, please take it to a XO or commander of the clan that did the offending and one from your clan so that the offender and or the offended aren't in the conversation. They will handle it. You may be given a warning or kicked however I will take the time to explain why and give you a chance to explain in case there is a mistake.

 

1.2 Vulgar language:

We would appreciate it if we kept this to a minimum. We know that sometimes it slips out and it is tough to control but let's try to keep it under wraps. If I get complaints about it, I will let the person in question know so we can find a solution. This also includes the word "RETARD". I have worked in SPED (Special Education) for several years now and find it to be an outdated and crude word. I will call out people using it regardless of the case. I am firm on this rule. Absolutely no exceptions. If it slips out just apologize and remember it for the next time.

​

1.3 Disagreements:

There will be disagreements at times. All parties are expected to be respectful towards each other and sort it out like ladies and gentlemen. At no point should the argument become personal. Should name calling or vulgar language ensue, please contact a Senior Officer (Personnel Officer, Executive Officer or Commander) to calm the situation. They will ensure it is sorted out and deal out any disciplinary action if it is deemed appropriate. They may also choose to consult other officers.

​

1.4 Political Discussions:

Class Family Clans do not have any stance on political topics or events that happen in this world. Members are free to voice their opinions and discuss with each other openly as long as it follows clan rules. I know these conversations can get fairly heated at times. Please refer to 1.3 and 1.1 for more information.

 

1.4.1 We fully support freedom of speech in all Class Clans, however it has to be agreed on by everyone in the room prior to the debate or discussion starting. Politics and Religion have not and will continue to not be allowed in Team Chat Rooms. This includes All Skirmish Rooms, All Advance Rooms and Clan War Rooms (See 1.1.4 and 1.1.5 for more information).

      1.4.1.1 This rule only applies in the above mentioned rooms if there is an event going on at the time. This includes 30 minutes prior and after the end of the event if applicable, as well as the waiting period in between battles. Outside of these hours, the rooms are to be treated as standard chat rooms. It is encouraged that member use rooms for their intended purpose, however it is loosely enforced.

​

1.5 TeamSpeak Gif/Images

No vulgar images or videos should be used in our TeamSpeak. This includes avatars and names that are different then your in-game name. If any report is given for this kind of infraction, you will be asked to either remove or change it.

​

     1.5.1 Examples of Vulgar images are classified as images that contain unnecessary violence, such as gore, explicitly sexual images or political/ religious statements which might create unnecessary disagreements between members.

 

      1.5.2 Some examples of gore are open wounds, victims of accidents, violence or self-injury (this also includes animals). If there are any questions about whether an avatar contains gore, ask a Staff Officer to verify it prior to posting.

 

      1.5.3 Sexual Images are an image, gif or video that contains nudity, suggestive images or phrases. There is a gray area here and some will be up to Officers to allow or deny. If it's not safe for work, don't post it.

 

      1.5.4 Risky political and religious statements are photo captions, phrases or images which might provoke someone into negatively commenting on it, thus sparking an unnecessary argument.

​

1.6 TeamSpeak tags are not to be Edited or added to the server without a Commander's permission. All tags should have a connection to the game and should not be demeaning or make fun of a member. No vulgar or sexual tags.

 

1.7 Member descriptions are not to be changed without prior approval of the member. Unless it is to add a tank that they had not added.

​

1.8 Descriptions and names of rooms should not be changed without the owner's permission. No personal rooms should be deleted without prior notification of the owner. This will prevent loss of data and confusion.

​

1.9 No horseplay in TeamSpeak this includes kicking people without cause or resetting the server without it being needed.

​

1.9.1 All Class members must be logged in to TeamSpeak during the hours of 7pm-12am eastern time if they are in game (WOT). If you are not logged in, you will be asked to login as soon as possible. THIS IS REQUIRED!

 

1.9.2 If for some reason you aren't able, please talk to a Personnel Officer as soon as possible to communicate why you are unable so they can make sure others are aware.

​

 

SECTION 2

Forums and Other Social Media

​

2.1 Facebook

Use of vulgar language of any kind is not allowed. This includes the word "Retard". No images or videos of questionable morals should be posted. We want to use Facebook to share photos of games, updates, and friendly banter. 

​

2.2 Forums

Everyone must be signed up for our forum. If you aren't signed up upon joining a CLASS Clan, please have an Officer assist you in joining. Please see 2.2.4 for exemptions.

 

      2.2.1: All members who are in the Clan Forum will be assigned a “FORUM MEMBER” tag in Teamspeak3. 

 

      2.2.2 Any member who is not in the Forums, will be assigned a “NOT A FORUM MEMBER” tag as well as the “NEEDS FORUM HELP” Tag.

 

      2.2.3 Members who have a Forum Application Pending will be assigned the “AWAITING FORUMS ACCEPTANCE” tag in addition to the “NOT A FORUM MEMBER” Tag

 

     2.2.4 Members exempt from joining the forums (CLASZ Members ONLY unless approved by a Family Command Staff Member), will be assigned the “FORUM EXEMPTION” Tag

​​

SECTION 3

Clan Battles

​

3.1 Battle Comms:

During battle, talking should only pertain to the battle. Excess chatter is not acceptable (Caller Discretion). If the caller says he or she needs it to stop, everyone must comply. If I get complaints about it, I will let the person in question know so we can find a solution. If a Senior Officer is present at the time of the issue, they should pull out the person in question and make sure they understand the rule. If the problem is repeated several times, the Officer may remove the player from the detachment and remove them from the TeamSpeak channel and if required the server. They may not remove anyone from the clan. To make a recommendation of removal please speak to the Discipline Director.

​

3.2 Battle Callers:

All battle callers must be respectful of the people they are leading. No one should be put down or told they "Need to uninstall". This may lead to a removal of the battle caller tag and a suspension from clan battles. If the caller has an issue with a certain member, they should contact a PO or XO to help deal with the issue or quietly pull the person in question out of the room and talk to them. No one should be shamed in front of the rest of the clan.

​

3.3 In Game Participation:

While in a clan battle, all players MUST try their hardest at ALL times regardless of score. This includes the shooting of gold ammo unless another type is appropriate. We fight until the bitter end. Players who give up prematurely will be dealt with on their own. Players may not: Throw the game, deliberately shoot teammates, try to screw up the call or communicate with the opposing team to give them an unfair advantage. All games should be played in a manner that reflects our core rules and ethics. This means no drowning, no ramming of enemies at the end of game to hold up the ending, and no delaying the game without the caller calling for it. DO NOT MESS AROUND WITH THE ENEMY!! These are just the basics. It is up to a Senior Officer to determine what is deliberate and what isn't. Should you suspect a player is sabotaging a game, please contact a senior officer.

​

3.3.1 Callers removing members:

Callers have the right to remove a member from both Advances and Clan wars for the rest of the night for the below reasons and not limited to:      

-Not firing the proper ammunition        

-Not following the call.       

-Refusing/ ignoring the caller request to ready up certain vehicles.      

-Disrupting the Battle through comms or using your vehicle to disrupt teammates.

-Dragging the game out without being told to by the caller.

-Failure to be in TeamSpeak, in the proper room, within a reasonable time of joining the Advance.

 

     3.3.1.1 Members who are removed for the reasons listed in 3.3.1 may not be guaranteed their spot back if they fix the issue in question. Other members may take the spot if they show up prior to the offending member correcting the problem.

 

     3.3.1.2 Class Family Members and Legionnaires may also replace the offending member at the 2:30 minute mark at the caller’s discretion.

       

​

3.4 Player Improvement:

We expect all members to try their best to learn new skills during Advances and Skirmishes. Members of each clan are expected to perform at a baseline level and show continuous improvement, even if only gradual. If for some reason a member is unable perform the duties as required by the clan, he or she may be asked to move to another CLASS Family Clan until they can show they have learned those skills.

(Please see Section 16 for more information)

 

3.5 Ability to Call Battle:

To call a battle you must have a battle caller tag. This tag is shown to the right of your name in TeamSpeak. To receive a battle caller tag you must start at Tier 6 and work your way up to Advances. All battle caller tags must be approved by the Personnel Director or Head Battle Caller. You may only call the battle types designated by the tag or below. Unless there are no callers on or not willing to call. In those two cases you may call but you will have to find someone that can ready Artillery and Inspire up for you or run without.

​

3.6 Callers Throwing Games:

In the rare event that a caller may be throwing a game or is deemed incompetent at calling, 3 Officers (Combat and Above) must meet at a convenient time during the series of detachments and/or Advances (Including during the Advance) to vote on whether the caller needs to be pulled. If the vote is 50%+ the caller may be pulled. The Officers MUST have a replacement who is qualified to call and has the appropriate tags. If they do not have a replacement, they may NOT pull the caller. The potential replacement caller may be part of the vote as long as they are a Combat Officer+. In the following circumstances callers have the latitude to decide the call. Callers may throw a game to end a game faster or prolong a game to force the end of an advance.

​

3.7 Startup of Advances:

To give all players a fair shot at getting a spot in the Advance, all Advances will be started 20 minutes prior to the start of the first battle. ANYONE may start an Advance at this time and turn it over to a caller when they show up. Any Advances started prior to this will be closed by an Officer (Combat+) as to not give the person who started the Advance an unfair advantage. No Skirmish may be switched to an advance. They must be closed out and a new advance started so every person has the same chance of getting to play in the advance. And invites must be sent out as soon as the advances are opened. 

​

3.7.1 The 20-minute rule only applies to the first hour of the advance, AS LONG AS and Advance was started and at least one battle was played. If an Advance is started, and the caller is unable to start the advance due to: Lack of personnel, failure of a member to ready up or the team is unable to find an opponent to play against, the 20-minute rule will carry over to the following hour. As long as the team drops in, and a match is found and a game is played, the 20-minute rule no longer applies for the remainder of the night. If a match is not found, the caller is unable to click in due to lack of personnel or failure of a member to ready up in a later hour, the 20-minute rule does NOT apply. Also, the 20-minute rule does not apply to any additional advance that is created after the first. i.e., the second, third or 4th Advance. As long as one Advance is actively playing or selecting vehicles, any number of additional advances may be created by other clan personnel. (Please see Section 14 for more information)

 

​

3.8 Joining Advances:

Any person that accepts an invite to an Advance should stay in that Advance. The only exceptions to this are when a caller is needed, and they are already in another Advance. And if another Advance needs more clan players to complete an Advance. In either of these cases volunteers will be asked for. Do not leave until you are told to move over. If a member drops from the server while in advance you may be replaced. Once you come back the person that took your spot gives your spot back as long as there is ample time left on the timer.

​

3.9 CLASS Family Invites:

All Class family members have priority over all legionnaires for skirmishes and advances. Except for potential recruits, they are to be treated as clan members. No Legionnaires invites should be sent out earlier than 10 minutes prior to the start of the Advance. At the 10-minute mark, the caller should send out invites to legionnaires if they have not been filled with clan members. In 5 minutes clan family members may be put into the advance. Potential recruits should be reserved a spot in the Advance and their invite should be sent out along with clan member invites.

 

3.9.1 Once a legionnaire is put into an advance they may not be removed unless they were put in by accident. In this case they should be removed as soon as possible

 

3.9.1.1 Legionaries may also be removed if they are a replacement for a member who was unable to play a battle or battles. (See 3.10)

 

3.9.2 Legionnaires MAY be removed if they: Are not in Teamspeak3, are not following calls or are disrupting the team etc.

 

3.9.3 As soon as a clan family member has been added into the advance, all other legionnaires may be put in.

 

3.9.4 Note: Exceptions to this rule can be made for callers that join another clan's advance for calling and experience purposes.

​

3.9.5 Mid Battle Chatter in Advances:

Between battles there is a 2:30 minute period. All talk MUST pertain to the lineup/ upcoming call before any post battle comments or side chatter starts. This is shown by the caller pressing battle indicating that they are satisfied with the lineup and have given the call. If the caller continues to speak after the battle button is pressed, all players must remain quiet until the caller has said they are finished speaking.

 

3.9.6 Family Command Staff Invites

As part of the Family Command Team’s Efforts to ensure that clans are running smoothly, they are exempt from the above mentioned rules if one of the following apply:

-They are investigating a claim against a member or group and are using the Advance to evaluate the issue.

-They are playing as part of a general rotation to see how clans are doing.

All Family Command Members must abide by all behavioral rules and are subject to the consequences of breaking those rules.

 

3.9.7 Family Staff Invites

Family Staff (Different from Family Command Staff*) may also need to be legionnaires in other clan’s advances for evaluation and observation purposes.

​

3.10: In keeping with CLASS's competitive goal and further desire to improve as a clan the following subsection of 3.0 is introduced. This policy is aimed at keeping CLASS improving as a clan while still providing other clans in the clan family a place to legionnaires in most cases. This rule is not meant to exclude players from other CLASS clans or Legionaries but more as an encouragement for them to increase their level of play and tank line-up.

  

      3.10.1: The caller has the right to refuse legionaries for any of the following reasons listed below:         

-They have had previous poor history with the clan or the caller.       

-They have the "Limited Lineup" tag.        

-The caller is not satisfied with their lineup of Tier X vehicles.        

-The caller is concerned that they may not have the current experience needed to play with CLASS at the moment.        

-Other officers are concerned about any of the above listed reasons and have informed the caller of such reasons.        

 

             3.10.1.1: "Previous poor history" means that the player was previously kicked out of the clan due to misconduct or that the caller has played with the player before, and has had constant disagreements and/or friction with the player. The Caller must believe that this friction could be damaging to the team's overall ability to win. The "previous poor history" ONLY applies to previous situations in team battles (Skirmishes VI and VIII), Advances and Clan Wars. Lack of participation, Inactivity and being unfamiliar with the player are NOT reasons to reject a player for "previous poor history".

​

                  3.10.1.1.1: This Rule WILL NOT be used to prioritize High PR and WN8 Legionnaire in other clans to pump up a team with ultra-high levels of play. If a member suspects a caller is abusing the policy, they will report it to a CLASS Family Officer as soon as possible.

 

            3.10.1.2: The limited lineup tag is a large red "+" or Plus Sign located on the left or close left of the players tags. All players must challenge wearing the tag with an Officer if they feel it was incorrectly placed on them. The tag notifies callers that the player wearing it does not meet the current take requirements for the clan they are in.

 

            3.10.1.3: "The caller is not satisfied with their lineup of Tier X vehicles" means that a caller may reject a player if they are concerned that the player may not have the tanks they need. This is similar to the situation outlined in 3.10.1.2 however not all clans in the CLASS Family use this tag as well as clans having different standards. A caller should only cite this reason if absolutely necessary.

 

            3.10.1.4: "The caller is concerned that they may not have the current experience   needed to play with CLASS at the moment" means that the caller is unsure if the player in question has the knowledge to adapt to CLASS's ultra-competitive nature. This one has generated a lot of controversy so here is the explanation for it. Players in CLASS have spent a lot of time grinding vehicles and working with fellow clan and family members, on their own, with other clans and legionaries to hone their skills and become a player who fits CLASS's current high requirements. Everyone is on their own journey in World of Tanks and at different places. In addition, each clan in the CLASS Family is attempting to take steps to ensure that they are able to take that next step. The feedback given to the Family Command Staff from CLASS Command Staff and Callers related to the issue of the current legionnaire policy in which CLASS Family members were prioritized solely based on time left until the battle series in an Advance begins, Available Slots and the first come first serve policy. This meant that CLASS Callers were required to pull in CLASS Family Legionaries and out of Family Legionaries without taking into account their current place in their World of Tanks journey. This forced callers to have to make in some cases major sacrifices to their lineup and call to accommodate players who may not have the experience or tanks to take on roles or positions that the CLASS Caller might need them to do.

​

                  3.10.1.4.1: Class Family Clans has been and will ALWAYS support the other clans in the Clan Family, however other clans in the Clan Family must recognize what CLASS Leadership is trying to accomplish by adding this adjustment to 3.9. They are not trying to push others aside; they are looking to better themselves so that they help others more effectively in the future.

 

            3.10.2: First come first serve for Advances no longer applies to CLASS Family Legionaries. The caller will select personnel who they feel best fit what they need in the lineup taking into consideration: Tank Lineup, Player Experience and Attitude. The one exception is outlined in rule 3.10.4.

​

                  3.10.2.1: CLASS Callers will prioritize CLASS Family Legionaries as much as possible BEFORE bringing in any Legionaries from outside clans. All attempts will be made to bring as many Clan Family members as possible. Outside legionaries is still considered a last resort. However, the caller may select Clan Family legionaries from the waiting list based on the above mentioned reasons.

 

            3.10.3: All CLASS Callers will attempt to bring in as many CLASS Family Legionaries prior to legionaries from other clans, however if there is a large disparity between a player from a CLASS Family clan and a Legionnaire from another clan, the caller may opt to take the legionnaire from another clan instead. This may only occur at the 5-minute mark.

 

            3.10.4: Should the countdown timer hit 2:30 minutes, the caller will be obligated to take whoever is in the Legionnaire list, regardless of their experience and tank lineup. The caller will attempt to pull players in using the first come first serve method.

​

                  3.10.4.1: If the legionnaire does not have any Tier X vehicles, they should NOT be pulled into the Advance.

​

                  3.10.4.2: If the legionnaire is pulled in at the 2:30 minute mark or afterwards, they will NOT be removed.

 

            3.10.5: Callers will recommend that CLASS Family Legionaries ensure that their clan does not have an Advance should they join a CLASS Advance. If the legionaries' clan does have an advance going, they will be strongly encouraged to support their clan before helping CLASS out.

 

            3.10.6: Once a legionnaire is pulled into the Advance, they will not be removed.

​

                  3.10.6.1: The only exception to this is if the legionnaire was pulled in by mistake. In this case they may be removed but only after a verbal apology is made to the player with an explanation of the mistake.

 

            3.10.7: Invitation Timeline

​

                  3.10.7.1: CLASS Clan Invites will go out at the 20:00 minute mark prior to the Advances starting. Players join on a "whoever clicks the slot quickest basis".

​

                  3.10.7.2.: CLASS Clan Potential Recruits are counted as CLASS Members. They may be pulled in along with Clan Members. A spot in the Advance may also be held for them by a recruiter.

​

                  3.10.7.2.2: Any member who does not get a slot because they were unable to make it prior to the 7:30 Mark, and the Advance is full, will not be given a slot in the Advance. It is their responsibility to ensure they leave ample time to join the advance through the Stronghold Portal or Accept and Invite. If they are short on Battles, they may request entrance into the advance. CLASS Members and Legionaries may opt to step out but are not obligated to.

​

                  3.10.7.3: CLASS Legionnaire Invites and Legionnaire Invites will go out at the 10 Minute Mark

​

                  3.10.7.4: Callers may pull in Clan Family Legionaries at the 7:30 mark.

​

                  3.10.7.5: Callers may put in other Legionaries at the 5-minute mark.

​

                  3.10.7.6: Callers must pull in ALL other Legionaries, including non-family legionaries, but must prioritize Clan Family before other Legionaries.

 

            3.10.8: All legionaries who inquire as to the reasoning behind them not being put into the Advance will be sent the link to this post.

 

      3.11 Clan Members leaving during an Advance

Any member who is unable to play a battle due to: losing connection, severe lag, real life concerns or issues or any other reasonable occasion, will be guaranteed their spot back upon their return.

 

            3.11.1: Members who rage quit will NOT be guaranteed their spot back.

 

            3.11.2: Any member who replaces a member who is unable to play a battle due to one of the reasons stated in 3.10 will be notified that they are replacing a member who was unable to play the battle, and upon the members return, they will be removed.

 

            3.11.3: The replaced member may opt to not return and all the replacements to continue playing. A clan member may also volunteer to step out, however it is voluntary.

 

3.12: After an Advance is completed, members are allowed to move from one Advance to another based on their personal preference as long as they abide by the following guidelines:

 

3.12.1: Members will not change Advances within 10 minutes of an Advance starting, unless the Advance completes after the 10 minute prior mark. In this case, members should quickly identify if another advance is active. If they would rather play in that advance, they must notify the caller of their change and move as quickly as possible.

 

3.12.2: Callers cannot force members to stay in the advance as long as they abide by 3.12.1. Members leaving outside of the above listed timeframe  may be subject to disciplinary action.

 

3.12.3: Members MAY NOT use rule section 3.13 to loop hole 3.12 to get into another advance outside of the timeframe listed in 3.12. Members found using this loophole will be subject to disciplinary action

 

3.13: Members may leave an advance at any time but should leave enough time for the caller to replace the member but if an emergency arises, or personal plans change, callers will not hold a member back from removing themselves from the advance. 

 

3.13.3: Members should communicate any changes in availability to the caller or senior officers in the room if possible.

 

​

​

 

SECTION 4

Random Battles

 

4.1 Random Battles/ Any Battle:

While playing in random battles it is expected everyone to be respectful to others. You wear a Class Family tag, and you represent all of us while in game. I do not want to be receiving messages from players saying that you were rude. This will lead to disciplinary action. If you don't have anything nice to say, don't say anything. Pretty simple.

            

      4.1.1 Retaliation is against clan rules. Players in CLASS Family do not engage with players who are abusing physics or game chat. 

 

            4.1.1.1 The only exception to this is to ensure that you are able to maintain control of your tank. If a teammate’s actions are affecting your game, you may do the minimum to ensure you are able to play the game. However this does not allow you to push them off a cliff or use vulgar language in chat. Instead a report should be submitted through WarGaming's support page with a ticket. Engaging will only lead to both players getting banned. 

​​​​

​​SECTION 5

Other Clans

 

5.1 Interaction: 

The same respect should be given to them as we do with each other. WE WILL NOT ACCUSE OTHER CLANS OF CHEATING IN ANY FORM! This makes us look bad and clouds the real reason we lost. If you have a legitimate reason to believe another group is cheating, you should submit a ticket to Wargaming and let them look into the issue.

​

INACTIVE 5.2 Effective immediately WoT in game General Chat is Off Limits to All CLASS Family Personnel. A review of multiple discipline issues arising and the ensuing review of the content of the General Chat led to this action. All CLASS clans are a Class Act. The definition of a Class Act is someone or a group who exhibits humanity’s best qualities. They are polite and sophisticated, as opposed to rude and bawdy. General Chat could not be further from that definition or a more toxic environment.

 

SECTION 6

Recruiting

​​​

6.2: Recruiting Strategy:

As CLASS Family is an exceptionally large clan, success in recruiting is crucial to any clan's long term success. The CLASS Family has had vast amounts of experience recruiting however the regulations currently set are fairly limited and have not been updated since the clans founding in 2018.

 

6.2: ALL players who are interested in joining a clan within the CLASS Family must have Teamspeak3 with the exception of CLASZ. It is up to the clan recruitment teams to ensure that the member has teamspeak3. They are not required to have teamspeak at the time of acceptance into the clan, however, must be in teamspeak within 7 days of joining the clan or they risk removal from the clan.

     

      6.2.1: All members who join the clan without teamspeak are the sole responsibility of the person who accepted them. It is highly recommended that all potential recruits are spoken to in Teamspeak3 PRIOR to them being sent a clan invite or their application being accepted.

6.2.2: All recruiters who accept a player into the clan without Teamspeak3, must report that they have done so to their Clan Head Recruiter. If the clan does not have a head recruiter, they should report it to the Clan Family Recruiting Coordinator or Clan Family Head Recruiter. 

     

      6.2.2: The only possible exception to this rule for players with exceptionally good stats. In this scenario, it might not be a bad idea to take a chance, rather than risk losing them to another clan. The word "exceptionally" in this phrase is based on the player's stats based on the current clan's requirements they have applied to.

 

6.3: All incoming recruits will be informed that:        

-They must meet the clan's battle requirements.        

-Be an active member of the clan forum.       

-Agree to the attendance policy of the clan they are joining.       

-Be in Teamspeak3 after 7PM EST regardless of the clan they are joining.        

     

     6.3.1: The only exception to this is if the player is joining CLASZ.

​

     6.3.2: All recruiters will explain the CLASS Family Structure to them as well as the officers at each level of the clan family and who they should go to in the event there is a problem, or they have a question.

 

6.4: “Fair Game” Policy: Policies have been created verbally however that does not work long term. Here are the following rules on who is fair game when it comes to recruiting. A few terms need to be identified prior to these rules being read:

​

-"Clanless": Someone who currently does not belong to any clan or have membership pending with another clan "Dead Clan": A Clan that has not played any team battles in the past 28 days and has a history of not playing any advance battles.

​

-"Fractured Clan": A clan currently in the process of falling apart.

​

     6.4.1: All Clanless players on the server are fair game to all recruiters. We have a       spot for ALL player skill types and activity levels. A clanless player should                  never be turned down for skill or activity.

​

     6.4.1: As long as the player is in a Dead Clan or a Fractured Clan, they are fair         game as well, however the process for recruiting them is a bit different. The player needs to express interest in leaving rather than being asked to leave. Asking a player to leave a clan while they are in another clan falls under Wargaming's Poaching Policies. Class Family is proud to follow Wargaming's Rules.

 

6.5: Questions from Potential Recruits

Should someone ask a question about our clan, please answer truthfully. If you do not know the answer, refer them to a Senior Officer, Personnel Officer or Recruitment Officer.

 

6.6: Requirements for Recruitment Officers:

Recruitment Officers must agree to recruit at least ONE player per week for the Class Clan Family, they should report this recruit to their Clan Head Recruit. They can be found as they have the Staff Sergeant Rank (SSG) with 3 chevrons over 1 rocker.

 

6.7: Requirements for Clan Head Recruitment Officers:

Head Recruitment Officers must ensure that their recruiters are recruiting 1 player per week for the family. They also make exceptions for potential recruits based on the recommendations of their recruiters. Clan Head Recruiters answer questions that their recruiters might have and forward the ones they aren't sure on to Family Recruiting Staff

 

6.8: Clan Family Recruiting Coordinator:

The Clan Family Recruiting Coordinator assists Family Command Staff and Clan Command with determining initial and progression changes to the clan's PR, WN8 and Tank List requirements. They also support the Clan Family Head Recruiter.

 

6.9: Clan Family Head Recruiter:

The Clan Family Head Recruiter oversees all aspects of recruiting. They work with Clan Family Command to ensure the overall smooth operation of all clans within the CLASS Family.

 

6.10: Potential Recruits without any Advance Experience:

Potential Recruits will not be denied from a clan in the CLASS Family solely for not having any experience in Advances. We will use their statics in Random Battles, character and ability to meet the requirements in the clan that they applied for. They may be asked to join another clan if they aren't able to perform to that clan's standards.

 

6.11: All New Clan members in the clan family will be placed on a 2 week observation period as soon as they join the clan. This is to further evaluate if the member is a good fit for the clan! Recruiters can look at numbers but it only does so much. Numbers are a good indicator but don’t always tell the entire story. This policy allows us to further evaluate members while in battles with us, to ensure this is the best match!

 

       6.11.1: New members will not be removed during the 2 week observation period for activity or skill level. They may be removed for items not relating to activity or skill

 

      6.11.2: All members will be briefed on this policy by recruiters. They should be informed that their spot is not 100% guaranteed, although we hope it works out.

 

        6.11.2: A new tag will be created called “Observation”. It will be a White O in a Blue Box. This tag will be removed upon the completion of the 2 week observation period

 

        6.11.3: At the period’s conclusion, the clan’s command staff will decide if the members are a good fit for the clan. The clan commander will make the ultimate decision if there is uncertainty, however they may NOT veto the rest of the command staff if the general agreement is clear.

 

      6.11.4: As stated above, this applies to ALL new players to a clan, regardless of status or stats. This protects each clan against purchased accounts or bought statistics.

The tag will be applied to transfers as well.

 

      6.12: All players entering the Clan Family must join the clan Forums within 7 days of accepting the clan invitation with the exception of CLASZ and developing clans. Failure to join the forums within that timeframe will result in a warning. Should they not promptly join the forums afterwards, they will be removed from the clan.

6.12.1: An exception to this is “New and Developing Clans” (See Section 21.0)

6.12.2: Exceptions may be made for those having issues joining the forums, but they must communicate these issues to their recruiter or the clan command staff.

6.12.3: Other exceptions may be made based on individual circumstances, but must be approved by the Clan Family Commander, Clan Family Second in Command or Clan Family Senior Advisor.

6.12.4: The Tag “New Members not in Forums” will be assigned to all new recruits who DO NOT join the forums upon joining the clan. The recruiter will work with them to ensure they join the forums. Should their member not join despite being told to do so, the recruiter will report this to the clan command staff for review, and possible removal of the member.

6.12.4.1: Recruiters who fail to mention the forums or do not help the member join, are subject to review and possible demotion as this creates unnecessary problems for clan and family staff members!

 

     6.13: Recruiters should use the following tools to evaluate recruit statistics and are recommended to use them in the following order:

1: Wotlabs                     Link: https://wotlabs.net/ 

2: WoT-Life (Noobmeter)   Link: https://wot-life.com/ 

3: Tomatoes.gg           Link: https://tomato.gg/ 

4: Tanks GG           Link: https://tanks.gg/

6.13.1: Other sites that recruiters would like to use should be submitted to the Clan Family Recruiting Coordinator or Clan Family Head Recruiter for review.

 

 

 

SECTION 7

Attendance

 

7.1 Attendance Requirements and Punishment:

The system for attendance is as follows: After 2 weeks (14 days) in a row of unreported absence, a member will be issued a warning statement and demoted one rank. The next week (now 21 days) if they still haven't shown up, they will be issued a second warning and demoted to another rank. If after 4 weeks (28 days) they are still absent, they will be sent a reason for their removal and kicked from the clan if they were a recruit. Every seven days of absence thereafter will result in another demotion. A person could regain their previous rank by completing the required number of battles for the month. You could only move up one rank per month in this system.

​

7.2 Reported Absence:

If you are going to be gone for 2 weeks+, please let a senior officer know. This will ensure that your spot is saved in the clan for when you get back. Should you fail to report the absence, you may be subject to a demotion or removal from the clan.

​

7.3 Long Term Leave:

If you are going to be gone for 2 months+, you may be asked to move to a secondary clan until you return. If you fail to comply, you may be subject to a demotion or removal from the clan.

​

7.4 Short Term/Extended Absence:

If you are going to be absent for less than 7 days it is not necessary to report it. If that extends to 14+ unreported, you may be subject to a demotion or removal from the clan.

​

7.5 Limited Activity:

If you are going to have limited participation for 14 days+ it is best to report it. This means that the disciplinary officers will take this into account when checking battles. If it is for 2 months+, you may be asked to move to another clan temporarily. See 6.3

​

SECTION 8 

Participation/Battle Requirements

​

8.1 Participation Requirements/Punishment OPTIONS: (The system for boxes has been changed to battles.)

 

      8.1.1: OPTION 1 - Participation is now tracked by the number of Advance/Clan War battles. Battles will be checked monthly on the first day of the month. First, if you have under the required battles in the past 28 days, you will be demoted 2 ranks. This means that a recruit will be removed from the clan for having under 50 battles. Others may be subject to this rule as well, if you fail to get close to the required battles for the month (case by case basis). If you are close to the amount required (~90%+) you will only be demoted one rank. Those who earn 150 battles will be offered the position of Junior Officer as an acknowledgment to their dedication to the clan. They will also be up for further promotions in the future. [No CLASS Clans currently assigned to this method]

 

      8.2.2: OPTION 2 - The Clan will demote all members starting when they have been inactive for 14 days, regardless of attendance. After 21 days they will be a recruit and after 28 days a reservist. Upon return, they will be promoted as normal back up the ranks as they play clan battles. ALL Reservists will be fair game to remove by ANY PO+ in the event a spot is needed. It is the disciplinary officer’s responsibility to ensure that all reservists are ready to be removed and informed of the possibility. [CLASS is currently using this method]

 

            8.2.2.1 A Reservist will be only removed for 1 of 2 reasons.

                           -The clan has hit 100 members

                           -There are more members waiting to get in than we have slots. We              —---------------------may clear slots ahead of time to make room

 

 

​

8.2 Participation Tracking:

Fifty Advance/Clan Wars battles will be required a month, for a 28-day period and checked once a month on the first day of the month. Except for the ranks of recruits and reservists that have been in the clan less than 28 days. These two ranks will be checked on a weekly basis and demoted if they do not have their 28 battles for the last 28 days. This will allow us to reduce the requirement by ten battles each time there is a Frontline/Steel Hunter. Some months may be reduced more if there is more than one week of Frontlines/Steel Hunter. This also goes for any other event that the XO's determine qualifies for a reduction. If you are unsure of the total you need, please see a Personnel Officer.

​

SECTION 9

Promotions and Demotions

​

9.1 Promotions/Demotion:

Promotions and demotions are subject to all the CLASS clan rules. But the Commander and XO's have the final say in the process.

​

9.2 Any member who plays 3 times the number of required advance battles will be offered the position of Junior Officer as an acknowledgment to their dedication to the clan. They will also be up for further promotions in the future. 

​

This is an update to the Rule 9.2 regarding promotions relating to the following positions:   

-Reservist        

-Recruit        

-Private       

-Junior Officer

         

9.2: All new members in the clan will be assigned the role of Recruit. Once a member reaches the required battles for the month, they will be given the rank of Private. Any member who exceeds the battle requirement by 3-fold, will be given the rank of Junior Officer (See 9.2). Members must maintain the battle amount to remain their rank each month.

​

9.2.1: All demotions will be in accordance with Rule Section 8

​

SECTION 10 

Booster Usage

​

10.1 Boosters and types of Boosters should only be used during the below time frames:

​

Monday-Friday: -Level 10 XP Booster and Level 10 Free XP Booster from 10 am EST-                                 5 pm EST.

                            -Level 10 Credit Booster and Level 10 Crew XP Booster from                                           6 pm EST- 12am EST midnight for a total of three credit boosters                                   a night.

​

Saturday           : -Level 12 XP Booster and Level 12 Free XP Booster from 10 am                                          EST- 5 pm EST.

                            -Level 12 Credit Booster and Level 12 Crew XP Booster from                                            6 PM EST- 12 am EST midnight for a total of three credit boosters                               a night. This is for War Games.

​

Sunday               : -Level 10 Credit Booster and Level 10 Free XP Booster from                                              10am EST- 6pm EST 

                           : -Level 10/11 Credit Booster and Level 10/11 Free XP Booster from 6pm                                      EST- 12am EST midnight. This during advances.

​

DO NOT activate any other boosters outside of this time frame without the permission of the Clan Commander or above!!

​

 

SECTION 11 

Clan Tournaments and Payouts

​

11.1 Clan Tournaments have at this time, three payout, Bonds, Gold, and Resource Boxes. When this type of tournament is played by CLASS the winnings will be determined by the below rules.

    

      11.1.2 Bonds will be kept in the clan treasury until the cap of 10,000 Bonds is met. These will be kept and not given out unless a member wins a tank in clan wars and does not have the required bonds to buy the tank.

    

      11.1.3 Any Bonds above the 10k will be distributed to the member that play in the tournament. We want our players to have these Bonds to either bid on a tank during clan wars or to buy purple items. The tournament leader must provide CO, XO, Quartermaster or whoever is in charge of payouts with the players and the amount they are to receive.

    

      11.1.4 Gold will be kept by the clan for use as incentives and or events.

     

      11.1.5 Resource Boxes can only be used by the clan and will be used for booster purchases or future stronghold upgrades.

     

      11.1.6All Clan Tournaments "MUST" be posted in the Forums under CLASS Discussion at least two days before the end of registration.  

​

SECTION 12

Clan Reward Programs

​

12.1: For acquiring the Object. 279 early: 2,000 Gold

12.2: For acquiring the Object 260: 1,000 Gold

12.3: For acquiring 1 Mark of Excellence on a Meta Tank: 200 Gold

12.4: For acquiring 2 Marks of Excellence on a Meta Tank: 400 Gold

12.5: For acquiring 3 Mark of Excellence on a Meta Tank: 600 Gold

 

12.6: All meta tanks are the ones found in the Clan Family Meta Tanks List in the Meta Tanks list on the Website. No other tanks will be accepted. The tank must be on the Meta list at the time of posting in the CLASS Rewards Program

​

12.6.1: The post to receive gold based on any on 12.1- 12.5 must be posted within 14 days of the achievement being made. Posts after that time frame may not be accepted and your request could be denied.

 

12.7: Any post for the above-mentioned achievements must be posted with a screenshot of the battle result. The date of the battle should be visible at the bottom of the screenshot as well as the player's name. Screenshots missing one or both of these items may be rejected.

 

12.7: Should you be posting about 12.1 or 12.2, you must play one battle before posting to ensure that the tank shows up in your service record. This way we can verify you have the tank.

 

12.8: There is no back pay for the CLASS rewards program, if you received the tank prior to joining the CLASS, as well as in a different clan in the clan family, you are ineligible to be paid for the vehicle.

 

12.9: The post must be made in the CLASS Rewards program page in the Forum. If the post is made anywhere else, you may not be paid for the achievement.

 

12.10: The CLASS Clan Rewards Program may change at any time. As soon as it changes, CLASS Command Staff will not payout for segments of the program that may have been removed. They will also not back pay for any additions that were previously not part of the program.

 

12.11: Inactive- Tanks earned during by placing in the Top X amount to qualify for a fixed price, normally 4,000 bonds in Clan Wars, or like events are not paid out. The clan selects those who are capable of winning a tank via the bi yearly equation and that is considered enough of an award. (NOTE: With CLASS’s adjusted rules, this rule is no longer applicable, however this rule still applies to other clans*)

 

*Other clans do not have a reward program so this rule is inactive across all CLASS Clans

​

SECTION 13 

Removing Members from a Clan and Pre/Post Actions

​

13.1: All members who are removed from a clan due to lack of activity or participation must be done by the clan disciplinary team. There is a fairly complex procedure to ensure someone is removed fairly so only personnel trained in this area may removed someone:

This includes checking the following: Attendance, Participation, Attendance Rooms in the Forums and Sections 7 & 8 in the pages on the website. This is different from Officers removing players due to poor conduct. That is up to an XO vote of 3 or if one person is kicked by one officer, they own that kick.

 

      13.1.1 Clans should avoid removing members for inactivity or participation unless they are at or nearing 100 players. Clan ratings are partially determined by the total number of personnel in the clan. More players = Better Rating

 

      13.1.2 If a clan is at or nearing 100 players and there isn't any disciplinary staff around to remove inactive players, clan command staff should appeal first to the clan family Disciplinary Officer and then to the Family Command Staff to sort out the issue. Clan officers should not take matters into their own hands as it throws off the disciplinary, family command and recruiting staff.

 

13.2: All retention officers must communicate with members who have been removed from the clan as soon as possible following their removal. The message should be the following:

  "As you know we had to remove you from the clan due to lack of activity, however we would love to keep you in the clan family! If you want to come back to the clan or clan family, let me know and I'll set you up with a recruiter to get you back in! :) Thanks!"

​

SECTION 14 

Maintaining an Advance

 

Introduction:  Based on a previous event we are adding this rule/ guideline so that in the future, we know what to do! Abandoning an advance lowers our Tier 10 ELO, clan rating and damages our reputation as a clan and a clan family!

 

14.1: Callers will be responsible for maintaining the personnel in an Advance. This means they are responsible for ensuring that the advances are played to its maximum duration, 57 minutes, if need be.

 

14.2: If a Team loses one of its members for any reason, it is the caller's responsibility to ensure that they find a replacement. This could include delegating to other officers or members if need be.

 

14.3: If the caller is full of legionnaires and cannot get more clan members, they must appeal to the second or third advance for members. If taking a technical loss is at risk, they have the right to interrupt the caller to do so and get members in.

 

14.4: As long as the advance is playable, even with only 13 members, the team will continue to play the advance through its entirety

 

14.5: Should the caller disconnect, another caller in the room must step up to take the call. If there is no caller, the call defaults to the highest-ranking officer in the room unless there is a volunteer caller.

 

14.6: A caller will play through multiple technical losses if need be.

 

14.7: An Advance will not be abandoned unless instructed to do so by a member of the clan's command staff (XO+)

​

​