End is Near was founded on the 10th of February, 2009 by Violent, Red and Xero. Their goal was to bring together players who played Battlefield for team work, coordination and squad play. When the community first came to be, ^EIN^'s flagship game was Battlefield 2142. End is Near was one of the best competitive teams in 2142 and quickly rose to high spots in various ladders. Shortly after, Battlefield Bad Company 2 was released, which became ^EIN^'s new flagship game. This game brought on a large change for ^EIN^, as our member base multiplied and our 32 man Conquest server became the 25th most popular in the world. With more members and a firm foothold in the Battlefield community, ^EIN^ was ready to make the transition into Battlefield 3. Now, ^EIN^ has expanded into divisions. Each division is represented in their own way. Some are elaborate and have their own sub-site in the ^EIN^ Community with their own ranks.
The ^EIN^ Chain of Command and Conduct explains the guidelines under which both casual and ranked members operate.
Activity in ^EIN^ is required to rank up. Covering these areas will allow you to progress in the ^EIN^ community. When progression is made, more rights and responsibilities are given within ^EIN^. To maintain yourself in ^EIN^, you need to make sure you cover certain requirements. Being active in TeamSpeak will ensure you will never get dismissed or retired in ^EIN^. Covering two out of the three areas will get you ranked up.
All members of ^EIN^ are required to show activity on ^EIN^'s TeamSpeak server, especially when in-game. Members who spend a high amount of time in TeamSpeak will become integrated within the ^EIN^ community.
In addition to being active on both TeamSpeak and the ^EIN^ Forums, members are encouraged to bring forth their ideas for further improving ^EIN^. Members with specific abilities such as website design capabilities and graphical design capabilities are encouraged to aid in developing those areas within the community. If a member does not feel that they can contribute to an internal part of the community, members are encouraged to donate to support ^EIN^'s TeamSpeak, website and game servers.
All members of ^EIN^ will fall under the following consequences for violating the Conduct Guidelines. Each violation will result in an email warning and be placed in our records. ^EIN^ is proud to be a drama-free community. Every community consists of people with different ideas and opinions, sometimes these differences can escalate and members can become aggressive. When these situations arise, ^EIN^ follows a structured policy. Once you violate the Chain of Command and Conduct four times, you are dismissed.
A ranked member in ^EIN^ should spend the majority of their time online participating in the ^EIN^ community. Spending more time elsewhere while having responsibilities within the community leads to little or no progress. Instead, step down from your Ranked status and become a Casual member.
Hacking is the most serious manner in which one can breach the Conduct Guidelines.
Any members caught hacking or cheating in-game will be immediately expelled from ^EIN^ as a community, will be banned from the ^EIN^ website, will be banned from the ^EIN^ TeamSpeak and will be banned from all ^EIN^ game servers.
Individuals caught hacking will have their activities made public, so that the rest of the gaming community is aware of their play style.
^EIN^ takes hacking very seriously and as such will not hesitate to enforce serious consequences for those who choose to do so.
Spamming ^EIN^'s TeamSpeak server will not be tolerated. Spam includes rapidly leaving and joining a channel using audio queues to annoy other members, playing music over the microphone or participating in conduct which is generally irritating and repetitive.
Spamming ^EIN^'s forums will not be tolerated. Spam includes making posts which contribute nothing to the topic or do not encourage response or discussion. Padding posts for the sole purpose of increasing one's post count is also classified as spam.
At any time, a member may contact a higher ranking officer to resolve any problem he/she may be having. If you feel you have been treated unfairly by any member, you may go to a higher ranking officer and have them file a complaint with the |XO|s. An officer who has too many complaints issued will be demoted.
^EIN^ is not just a one game clan, we are a community. We have expanded to include different types of games. Each division is granted a division level based on how many members it has as well as how active they are on places like the forums and TeamSpeak. We encourage all divisions to talk with each other and get along. Do not interrupt members of other divisions who do not wish to be disturbed.
^EIN^ has two categories of members: Casual and Ranked. Casual players simply enjoy gaming with ^EIN^ members without the duties that come with ranking. Ranked members get to participate in the way ^EIN^ operates, this grants certain privileges and adds responsibilities. Once you pass the recruit phase you become a full status member. Casual members will remain full status, but will not be able to earn rank ups.
When your application is accepted you become a Recruit. During this phase of ^EIN^, we make sure you will be an active member by observing your activity on TeamSpeak and the website. This phase only lasts 5-12 days and ensures that you will be a good addition to the community.
Ranked members serve as the driving force behind the community. All ranked members contribute in various ways to make sure ^EIN^ stays updated, fair and constantly evolving. To do this, ranked members get access to tools and powers based on the area(s) they are assigned to. ^EIN^ is divided into four Branchs: the Member, Restricted Officers |RO|, Non-Restricted Officers |NRO| and Executive Officers |XO|. Each Branch is responsible for a part of ^EIN^. As you change Branchs during the ranking process, you are given more tools and powers.
The Corporal |Cpl| is the first step to becoming an officer. These members have shown they wish to be more involved with the community and eventually want to become leaders. They have demonstrated an excellent understanding of the Chain of Command and Conduct and an exceptional level of activity.
A |Cpl|'s Access Level is no higher than a regular member, except that they have their own |Cpl| channel.
|Cpl| is a stepping stone to becoming an officer in the community.
A |Cpl| must remain active in order to keep their rank.
A |Cpl| must be willing to join and play on ^EIN^ servers.
A |Cpl| must have served 30 days an ^EIN^ Member (unless stated otherwise by the |XO|s).
A |Cpl| must have a complete understanding of the Chain of Command and Conduct.
The Restricted Officers |RO| take care of the day to day needs of ^EIN^. The |RO|s moderate the forums, TeamSpeak and game servers. Each |RO| is assigned to one of three Branchs. Each Branch runs and serves a primary function within the community, the Branchs are listed below.
Community Management Branch:
The Community Management Branch of ^EIN^ serve as the directional leaders. Community |RO|s are responsible for all social media aspects of ^EIN^, as well as recruitment.
The Community Management Branch acts as ^EIN^'s main source for recruiting. Community |RO|s maintain and moderate all social media services ^EIN^ has:
Community |RO|s welcome new members to ^EIN^ and ensure they have everything they need.
Moderating on TeamSpeak.
Minor website tools.
Access to all social media networks.
Accepting of applications.
Access to the ^EIN^ Master List.
Access to the appropriate |RO| channels.
The Server Branch ensures all ^EIN^ game servers are functioning and moderated. Server |RO|s are responsible for getting members together to populate a game server.
Server |RO|s moderate ^EIN^'s game servers and ensure they are up to date. They also decide the settings our servers run on. They make fair, justified rules to follow while on our servers. Server |RO|s must report all bans to the appropriate forums Branch.
Moderating on TeamSpeak.
Back-end access to all ^EIN^ servers.
Procon access to all ^EIN^ servers.
Accepting of applications.
In-game admin rights.
Access to the appropriate |RO| channels.
The Staff Branch of ^EIN^ is responsible for the organization and updating to the ^EIN^
Master List. The Master List serves as a vital resource to keep ^EIN^ ranks active and moving.
The List also keeps track of all members and their activity within ^EIN^ to ensure we have an
Staff |RO|s update and make changes to the Master List. Staff |RO|s deal directly with the ^EIN^ audit system. A Staff |RO| must be very well organized. These Staff |RO|s have their own rank. A Staff |RO| will rank faster than other |RO|s. Staff |RO|s must work directly with the |SMA|.
|SGT|s are the default rank of the |RO|s. Community and Server |RO|s start off with this rank. This is the first rank where you receive assignments and are granted tools to do them. To progress further in rank, a |SGT| must show initiative and understanding of their Branch.
Universal Branch Tools
|SGT|s may kick anyone from ^EIN^'s TeamSpeak server who is lower in rank and in violation of the Chain of Command and Conduct.
|SGT|s may kick and ban anyone outside of the community who violates the Chain of Command for a maximum of 24 hours.
|SGT|s may not ban anyone who is a registered ^EIN^ member.
How to Become a |SGT|:
All |SGT|s must have served 30 days as a |Cpl| (unless stated otherwise by the |XO|s).
All |SGT|s must have a thorough understanding of the Chain of Command and Conduct.
The |SSG| has an important role within the community. The |SSG|s are responsible for the crucial task of keeping the Master List updated. Sometimes |SSG|s expanded tools beyond the privileges of the other |RO|s. A |SSG| will sometimes be called up to a higher rank at any given time because of the skill level needed to fulfil this rank.
|SSG|s update and make changes to the Master List.
|SSG|s deal directly with the ^EIN^ audit system.
|SSG|s must be very well organized.
|SSG|s will have a direct relationship with the |SMA|.
|SSG|s will rank faster than other ranks.
|SSG|s have moderating powers on TeamSpeak.
|SSG|s have minor website tools.
|SSG|s may accept applications.
|SSG|s have access to the ^EIN^ Master List.
|SSG|s have the ability to edit anything to do with the ^EIN^ e-mail.
|SSG|s have access to the appropriate |RO| channels.
|SSG|s may be granted additional tools based on their skill.
How to Become a |SSG|:
All |SSG|s must have served 30 days as a |Cpl| (unless stated otherwise by the |XO|s).
All |SSG|s must have a thorough understanding of the Chain of Command and Conduct.
All |SSG|s must be appointed by the |Capt| with recommendation from the Staff |RO| leader.
|MSGT|s are the current leaders for each Branch. A |MSGT| continues to do the required duties of a |SGT|, with some extra responsibilities. They may be asked to perform duties in other Branchs as well. A |MSGT| has shown they wish to go further in ^EIN^ and are ready to move on to become an |NRO| with time and devotion.
|MSGT|s make sure their Branch is always functioning properly.
|MSGT|s may learn other Branchs and help with them.
|MSGT|s conduct the ^EIN^ audit.
|MSGT|s train all |SGT|s and |SSG|s for their Branch.
|MSGT|s report all Chain of Command and Conduct violations in forums.
Two |MSGT|s must meet to conduct a bi-weekly audit.
|MSGT|s recommend rank advancements from |Cpl| to |SGT| during audits.
|MSGT|s must submit audit reports to the proper Branch of forums bi-weekly.
|MSGT|s have moderating powers on TeamSpeak.
|MSGT|s have the ability to edit anything to do with the Master List.
|MSGT|s have access to the |MSGT| channel.
|MSGT|s have in-game admin rights.
|MSGT|s have Procon access to all ^EIN^ servers.
|MSGT|s have back-end access to all ^EIN^ servers.
|MSGT|s may ban a member for a Chain of Command and Conduct violation for no longer than 24 hours, report must be filed properly.
How to Become a |MSGT|:
All |MSGT|s must have served 30 days as a |SGT| (unless stated otherwise by the |XO|s).
All |MSGT|s must show excellent knowledge of their Branch.
All |MSGT|s must be able to lead.
All |MSGT|s must be appointed by the |XO|s with recommendation from the |SMA|.
The |SMA| leads the entire |RO| Section of ^EIN^. Any problem within the |RO| Section
goes directly to the |SMA|. There can only be one |SMA| at a time and they serve as a link
between the |RO|s and the |NRO|s.
The |SMA| resolves all issues within the |RO| Section.
The |SMA| reviews the audit for any mistakes and makes the necessary changes if needed.
The |SMA| may suggest someone to be ranked to |MSGT| based on performance.
The |SMA| must know each Branch well.
The |SMA| must play a part in each Branch's major function.
The |SMA| should keep the |NRO|s aware of everything.
The |SMA| will be asked to help in the making of new divisions, groups and other community related projects.
The |SMA| will attend the |XO|/|NRO| monthly meeting.
The |SMA| receives advanced TeamSpeak moderating powers.
The |SMA| has the ability to edit anything to do with the Master List.
The |SMA| has access to the |SMA| channel.
The |SMA| receives minor website tools.
The |SMA| has in-game admin rights.
The |SMA| has Procon access to all ^EIN^ servers.
The |SMA| has advanced back-end access to all ^EIN^ servers.
The |SMA| may ban a member for a Chain of Command and Conduct violation for no longer than 72 hours, report must be filed properly.
How to Become the |SMA|:
The |SMA| must have served as a |MSGT| for 30 days (unless stated otherwise by the |XO|s).
The |SMA| must be proficient in every Branch of the |RO| Section.
Non-Restricted Officers are responsible for website management, disciplining actions and other duties dealing with the administration of ^EIN^. |NRO|s have shown they have the ability to make ^EIN^ a better community. A |NRO| must be loyal to the community and must also show the ability to deal with problems and solve them quickly and justifiably. The |NRO|s are split into two Branchs, Administration and Organization. These Branchs are split into two ranks, 1st Lieutenant and 2nd Lieutenant. Each rank is described below in detail. All |NRO|s must show they have the ability to perform various duties or else they will face demotion at anytime.
|2LT| is the administration backbone of ^EIN^. A |2LT| ensures that the Chain of Command and Conduct is followed at all times by all members. With this duty, they have expanded abilities to deal with situations as they arise. A good |2LT| is fair and will always deal with problems maturely.
A |2LT| responds to all reports filed by each Branch of ^EIN^.
A |2LT| makes a duplicated report in their Branch of the forums.
A |2LT| must follow the steps listed in the Consequences for Violating Conduct Guidelines: HERE.
A |2LT| must keep track of who has violations and the dates of expiry.
A |2LT| may be asked to attend emergency meetings regarding fourth violations of the Chain of Command and Conduct.
A |2LT| will send out appropriate e-mails for the violations.
A |2LT| will be asked to help in the making of new divisions, groups and other community related projects.
A |2LT| will attend the monthly |XO|/|NRO| meeting.
A |2LT| moderates all forum activity for violation of the Chain of Command and Conduct.
A |2LT| may need to lock or delete any post or thread on forums.
A |2LT| receives high level TeamSpeak moderating powers.
A |2LT| has the ability to edit anything to do with the Master List.
A |2LT| has access to their own channel in the |NRO| TeamSpeak Branch.
A |2LT| receives advanced website tools.
A |2LT| has in-game admin rights.
A |2LT| has Procon access to all ^EIN^ servers.
A |2LT| has advanced back-end access to all ^EIN^ servers.
A |2LT| may ban a member for a Chain of Command and Conduct violation for no longer than 1 week, report must be filed properly.
A |2LT| receives their own Branch on the forums.
A |2LT| is heavily involved in all Chain of Command and Conduct violations within the community. When a lower ranking officer files a report for discipline, the |2LT| duplicates it, files it and then ensures it is in proper order. They also ensure that once the member gets a third violation, a report is filed with the |XO|'s. A |2LT| will always follow up with a report they received from a |RO|, by talking to the |RO| and the member to ensure this is not a power trip of any kind and the action was justified.
How to Become a |2LT|:
A |2LT| must have served either as a |SSG|, |MSGT| or |SMA| for 90 days (unless stated otherwise by the |XO|s).
A |2LT| must be justified with their actions.
A |2LT| must be very active in ^EIN^ covering all three Areas of Influence: HERE.
A |2LT| must be 18 or older unless member before 9/20/2010.
|1LT| is the second rank in the |NRO| Section of ^EIN^. |1LT|s also receive key tools for moderating the ^EIN^ community website. These tools are granted for the purpose of keeping everything organized and up to date. A |1LT| is a part of the |NRO| Organization Branch.
A |1LT| performs the appropriate maintenance to the website.
A |1LT| gives permission to users to open up certain areas of the site, based on permission level, this is commonly known as tagging.
A |1LT| is responsible for keeping all ^EIN^ community groups up to date.
A |1LT| checks to ensure the ^EIN^ e-mail system is running correctly.
A |1LT| acts as a fail-safe to ensure the Master List is always kept up to date.
A |1LT| will be asked to help in the making of new divisions, groups and other community related projects.
A |1LT| will attend the monthly |XO|/|NRO| meeting.
A |1LT| must keep the Donation List up to date.
A |1LT| checks the ^EIN^ game servers' back end for any inconsistencies and deals with it accordingly.
A |1LT| receives high level TeamSpeak moderating powers.
A |1LT| has the ability to edit anything to do with the Master List.
A |1LT| has access to their own channel in the |NRO| TeamSpeak Branch.
A |1LT| receives advanced website tools.
A |1LT| has in-game admin rights.
A |1LT| has Procon access to all ^EIN^ servers.
A |1LT| has advanced back-end access to all ^EIN^ servers.
A |1LT| may ban a member for a Chain of Command and Conduct violation for no longer than 1 week, report must be filed properly.
When a |1LT| is moderating |RO| activity and sees any inconsistencies, a |1LT| should never fix the problem themselves. Instead go to the |SMA| or a |MSGT| and allow them to run their Branch. Remember that as a |NRO|, it is your duty to keep an eye on your former duties and not to do them. Communication is a key trait a |NRO| must have to go further.
How to Become a |1LT|:
A |1LT| must have served as a |2LT| for 90 days (unless stated otherwise by the |XO|s).
A |1LT| must be very active in ^EIN^ covering all three Areas of Influence: HERE.
A |1LT| must be 18 or older unless member before 9/20/2010.
The |Capt| acts as the go between for the |XO| and |NRO| Sections. They are also the |NRO|
Branch leader and only one can exist at the same time. The |Capt| has the ability to access |XO| areas of the site. The |Capt| has been with ^EIN^ for a long time and knows everything about each Branch.
The |Capt| is the leader of the |NRO| Section.
The |Capt| oversees all |2LT| and |1LT| duties.
The |Capt| will be in close contact with the |XO| Branch.
The |Capt| must approve all audits before any further action is taken.
The |Capt| will be apart of the monthly |XO|/|NRO| meeting.
The |Capt| must attend all emergency meetings.
The |Capt| moderates all forums activity for violation of the Chain of Command and Conduct.
The |Capt| may need to lock or delete any post or thread on forums.
The |Capt| receives |XO| TeamSpeak moderating powers.
The |Capt| has the ability to edit anything to do with the Master List.
The |Capt| has access to their own channel in |NRO| TeamSpeak Branch.
The |Capt| receives advanced website tools.
The |Capt| has in-game admin rights.
The |Capt| has Procon access to all ^EIN^ servers.
The |Capt| has advanced back-end access to all ^EIN^ servers.
The |Capt| may ban a member for a Chain of Command and Conduct violation for no longer than 1 week, report must be filed properly.
The |Capt| will have access to the |XO| Branch of the forums.
The |Capt| is one of the most advanced ranks in ^EIN^. The |Capt| has many unrestricted tools in areas of ^EIN^. The |Capt| is the only ranked member outside of the |XO| Branch that can make fast and immediate actions at any time. The |Capt| is fully aware of new projects and changes coming to ^EIN^.
How to Become the |Capt|:
The |Capt| must have served as a |1LT| for 120 days (unless stated otherwise by the |XO|s).
The |Capt| must be justified with their actions.
The |Capt| must be very active in ^EIN^ covering all three Areas of Influence: HERE.
The |XO| Branch of ^EIN^ are the ones who run the community. They oversee everything to do with ^EIN^. They control the treasury and use its funds to cover ^EIN^'s to ensure the community can continue to operate well into the future. Any rank within the |XO| Branch is composed of top ranking officers. |XO|s have been here for a long time and should be respected at all times.
|XO|'s are in charge of new projects. When an idea is proposed, an |XO| puts together a project team consisting of themselves and any number of |NRO|s. They guide the project through completion. Projects are divided into five phases and are classified based on their progress.
Phase 1: Idea conception.
Phase 2: Appointing |NRO|s to help with project.
Phase 3: Constructing the project.
Phase 4: Finalizing everything, checking spelling, grammar, bugs and contradictions to other parts of ^EIN^.
Phase 5: Launching project fully.
Becoming an |XO|:
An |XO| must have served as the |Capt|.
An |XO| have contributed funds to the community on a regular basis.
An |XO| must show the ability to be able to run short and long term projects.
All current |XO|s must agree to an |XO|s appointment.
Full website powers.
Full TeamSpeak powers.
Controlling of projects.
It takes two or more |XO|s to appoint anyone above |RO|. An |XO| may appoint any |MSGT|, |SSG| or |SMA| as long as they make note of it in the proper audit area of ^EIN^.