Code of Conduct & Basic Constitution of 1st Crucis Recon
1st Crucis Recon traces our lineage back to the Star League Defense Force. Our ancestors were members of the 149th Dragoon Regiment, a detachment of the VII Corps. After fighting valiantly in the Hegemony Campaign and the Liberation of Terra, we refused to leave our homes in the Inner Sphere on Kerensky’s Exodus and instead pledged our service to House Davion and the Federated Suns. In the 1st Succession War, the bulk of our forces were destroyed in a desperate last stand against Kurita forces on Kentares IV. Only the 798th Reconnaissance Company survived, fighting a guerrilla campaign until relieved by AFFS forces. Shipped back to New Avalon, the survivors of the 798th were rebuilt into the 1st Crucis Recon, attached to a larger Davion RCT.
With the arrival of the Clans, the 1stCR, now a formidable fighting force in its own right, has converted to a Mercenary Command. To this day, we bear both the Sword and Sun and the Cameron Star, never forgetting our heritage. When House Davion is threatened, we will be there, and will not contract against them. However, we always remember our responsibility to the rest of the Inner Sphere and will stand against the Clans should they threaten Terra. Notwithstanding this, we will fight for Clan Forces against some Houses, even leaving our homes in the Federated Suns for a time to take the fight out into the Periphery.
Members of the 1stCR are expected to be polite, to salute our fellow players (<S> or o7) as appropriate (whether friend or foe), and not to engage in smack talk, trolling, or other behaviours of a dishonourable nature. Friendly jibes and ‘locker room talk’ among team members is one thing; trash talking is something else. Insults aimed at member’s race, gender identity, religion, nationality, ethnic origin, sexual orientation, or other personal factors will not be tolerated.
1stCR plays to win, but also for fun and to uphold a strong image in the Battletech community. We do not teamkill or grief our fellow players in any way while in-game and will be respectful to honour the [1CR] tag we all carry.
1stCR does not maintain a strict anti-swearing policy, as we understand that occasional slips of the tongue happen and too strict an observance of a ‘no-cussing’ policy creates undue stress. However, we ask that if any member or guest should request a cessation of such behaviour, all pilots respect that individual’s wishes at that time and in the future. Certain channels may be established on our TeamSpeak server may specifically be marked to denote a ‘Mature’ room. Conversely, we did not cuss in the presence of Junior MechWarriors. We will neveruse inappropriate language or insults via in-game communications to harass or deride other pilots, whether members of 1stCR or otherwise.
Recognizing that members of 1stCR and MWO as a whole come from diverse ethnic, racial, national, religious, political, and cultural backgrounds, we ask that inflammatory discussions of these natures not take place in our general Teamspeak rooms. Should you wish to discuss these things, we ask they be taken into a TeamSpeak room designated for that purpose.
1stCR does not maintain rigid requirements for activity level. However, we ask that members of 1stCR attempt to log in and play at least once every 30 days. Inactivity for more than 60 days will result in a transfer to Reserves. Pilots inactive beyond 180 days will be moved off the roster, and permanently decommissioned after 1 year. Allowances can be made for special circumstances if prior notice is given before the deadline.
Officers (members of Lieutenant rank and higher) will be held to a higher standard of activity and are expected to be active at least fortnightly, with absences of no longer than 30 days at a time without prior leave. Officers are expected to lead combat drops and to train the unit. This is their primary role and is to take precedence over other concerns.
1stCR utilizes the rank and structure system of the Star League Defense Force for day to day operations. Rank progression takes place in the following order: Recruit - Private - Senior Private - Corporal - Sergeant - Master Sergeant - Warrant Officer - Lieutenant - Captain -Major - Lt. Colonel. We also maintain the ceremonial honour ranks of CSM and Colonel-in-Chief. Rank and organizational structure will develop and evolve as the unit grows.
The Unit CO will not hold any rank higher than that appropriate to the number of members in the Unit. Each Battalion will include 2-3 Companies (commanded by a Major or a Captain), supported by a Lieutenant, Warrant officer and 9-12 additional Pilots. Each Battalion will be led by a BCO (Lt. Colonel), seconded by a BXO (Major) and additional staff (if required). The CS< may be seconded to a Battalion on request.
Company Command staff shall be the primary point of reference for grievances, concerns, and problems within a Battalion. Serious issues may be taken to Battalion Command staff, and if necessary the Unit CSM (who officially exists outside the immediate Chain-of-Command).
While the military-simulated Chain-of-Command will be utilized to handle day-to-day operations, 1stCR will operate on democratic principles. Major decisions (like whether to change contracts for a major event, change TeamSpeak servers or rebrand the Unit, etc) will be handled by a general vote of all members. Issues open for a vote will be placed on the unit website in the form of a forum post with a poll. Voting will usually remain open for a full 7 days, at which point a majority vote is binding (unless previously declared otherwise).
Disciplinary actions will be handled by a council of officers. Minor infractions are expected to be dealt with at lower levels and only referred if a recurrent problem exists. Major infractions will be handled by a Council of (at least four) Officers, where the case will be heard and a vote on the course of action will be taken, up to and including ejection from the Unit for repeated infractions.
Members of an individual Command or Batallion may, upon dereliction of duty or repeated infractions on the part of an Officer may also hold a ‘Vote of No Confidence’, in which case a two-thirds vote will see the vote passed (from which the subject of the vote is recused). This vote will then be passed to the next most senior Command for ratification. In most cases, the Officer in question will then be demoted, and replaced by the next most senior. Should the subject of a Vote of No Confidence be the Unit CO, the Unit XO will preside over the Council of Officers. Should there be a successful Vote of No Confidence, no further recourse will be necessary to appoint a new CO.