Sun Nov 19 11:52:12 - CST
 

The Ruling Government and Laws of SLP

The Ruleing Government of SLP is commonly reffered to as "Section 778". This section starts off with the CoC, and the rest of the structure and governmental layout of SLP.
The sections found on this page are to be considered the "up to date" version of thier respective sections.
Current Revision: 2010 Mar 01 17:31 - GST

Section 778
Codes of Conduct

In Section 778:
"OvKhan" is defined as a higher ranking member than yourself.
"Clans" are defined as other online gaming units regardless of their faction type.
"Clan business" is defined as SLP meetings, restricted SLP discussions on the forums, the conduction of a campaign or battle, and any order of business SLP and or allied forces must conduct.
"Restricted materials" is any information in text image file or attachment found in the restricted areas of the forums; Members Area, Keshik Hall, and Khan Halls.
"Match" is defined as a rated match against another clan and or players, or a rated match within SLP.
“Played Game” is defined as making a full drop with other SLP members for at least 15 minutes or at least a contiguous 15 minutes of gameplay with other SLP members.
“Weekly Meeting” AKA “Clan Meeting” is defined in three phases. Phase-1 is the actual conductance of the meeting and clan business. Phase-2 is the notarizing and recording of weekly reports and Phase-1 of the current Weekly Meeting as well as the weekly Keshik Meeting. Phase-3 is the gaming session held by the present members.
“Active Presence” is defined as interacting at minimal on the forums, interacting in the SLP TeamSpeak server, or interacting in a game. It also may include fully participating in played games and weekly meetings.


§778.5.4 a
Fight with honor and fairness.

(i.)Fighting with honor is defined by keeping and adhering to any agreements and rules to the engagement while respecting the outcome and aftermath of the engagement, and entering and executing and engagement with no trickery or deceit.
(ii.)Fighting with fairness is defined by engaging the opposing force in a clean fair equal and compassionate manor.

§778.5.4 b
Respect other clans friend or foe.

(i.)The respect of other clans and their members in part or in whole or other players are to be treated in a respectful manor that will not cause any discrepancies feuds or complications with yourself SLP or another clan.
(ii.)This rule is with an exception as deemed by the Keshik as to ban players from our servers and such, but is not to condone actions that will openly and rudely offend other players and clans.
(iii.)Treat other players in a respectful manor in our servers and show them hospitality.

§778.5.4 c
Treat others how you would like to be treated.

(i.)As a recap of Section 778.5.4 Chapter C; other players are to be treated in a respectful manor that will not cause any discrepancies feuds or complications, this is done by being aware at all times of what say and act, and how you say and act.

§778.5.4 d
Follow and honor the words of your OvKhans.

(i.)To follow and honor the words and orders of your OvKhans is to simply do what you were ordered to do in the respectful boundary that it will not cause any conflictions or problems with any; rules, laws, online gaming units, or other players.

§778.5.4 e
Legging & chaining.

(i.)Legging is defined as intentionally shooting the leg and or legs of a mech, chaining is defined as intentionally firing your weapons one by one causing the target difficulty to draw a bead on its target. (ii.)These acts are condoned because it demonstrates ones lack of ability to best another in combat by skill knowledge and force.
(iii.)These rules are in exception by the Keshik or a member of the Keshik during an engagement.

§778.5.4 f
Disorderly conduct & dishonorable acts.

(i.)Disorderly conduct is; a disruptive act or behavior that causes SLP and or allied forces to lose a battle, a disruptive act or behavior that disrupts the flow of clan business.
(ii.)Dishonorable acts is defined as a disruptive act or behavior that causes conflict or complication with rules, laws, SLP, other clans, other players, and or yourself.

§778.5.4 g
Abuse of Power.

(i.)Blackmail of a member(s) or SLP, extortion of a member(s) or SLP, harassment of other members, distribution of restricted materials outside their respective areas and or outside of SLP, giving a command or order that would put another member(s) at jeopardy of violating any part of section 778.5, treating other members in a way that would cause them to become discouraged, or jepordise the well being or integraty of the clan, ect.

§778.5.4 h
Participation

(i.)Participation determines what is and is not an active member. (a.)An active member of SLP must make an active presence of at least three times a week, which must include two played games and Phase-1 of the weekly meeting to be considered an active member. (b.)An active member of the Keshik must make an active presence of at least four times a week, which must include three played games and Phase-1 of the weekly meeting and Phase-2 of the weekly meeting. (c.)If a problem arises that you cannot make the meeting or activity let your commanding officer know.
(ii.) When you sign up for a match you have made a commitment to yourself and the other members of SLP that you will be there on time for logistics stage and the match itself, if a problem arises that you are not able to attend the match, leave a message so that the CO and other members of the match know you will not be able to make it.
(iii.)Your participation level is rated and recorded by your commanding officer; the above is just the minimal requirements for being an active member in SLP to avoid repercussions. Repeated excused absences from meetings and matches, as wellas repeated LOAs, may be reviewed and acted upon by the Keshik as they see fit.


Section 779
Standard Practices and Procedures

In Section 779:
"Clan" is referred to as the BattleTech faction type, Clan.
"Clan business" is defined as SLP meetings, restricted SLP discussions on the forums, the conduction of a campaign or battle, and any order of business SLP and or allied forces must conduct.

§779.1.1 a
We Are Clan Doctrine

(i.)SLP is a Clan based faction. Allot of players are lured to the clans because of their "better technology", ignoring and/or not properly researching who the Clans are. In allot of aspects this respectfully ruins as well as imbalances allot of the videogames when they stray from the original lore of BattleTech.
(ii.)It is impossible to recreate the entire lore of BattleTech due to the lack of participation from other players in the community, so it is best to stress upon creating the "feel" of the clans. This is done by implementing a handful of trials, traditions, and lore carried out among the clans, and refitted best to suit the experience for online gaming in MechWarrior. (iii.)This aspect makes SLP not an online gaming unit for every player, it is more for the players who enjoy the BattleTech lore, particularly the Clan lore.
(iv.)A player can get a better understanding for who the clans are and what they are about by reviewing the "About The Clans" section on our website.

(v.) Who are the clans?
(a.)In short the clans are best described as the remaining SLDF forces that took to exile with Aleksandr Kerensky, but this is for too short of an explanation that touches the roots of the Clans existence. (b.)After the SLDF forces embarked into exile on the Pentagon Worlds they soon fall into a paralleled feud and disarray as to the Inner Sphere, where Aleksandr lead a second exodus with the remaining forces who were still loyal to him. (c.)Upon Aleksandr's death he made it his dying wish that his son would take charge of the SLDF forces and under his command and retake the Pentagon Worlds. And Nicholas Kerensky did just that. (d.)He reorganized the society so that it would rid itself of the ongoing feuds related to the old successor states. Nicholas also reorganized the military structure to better suit the conquest of the Pentagon Worlds. The changes that Nicolas made to their new society would turn the SLDF into the Clans, and through the years this culture would turned their warriors and citizens into an unrecognizable face of humanity structured upon war and fundamentals of might makes right with ritualistic duals and complex rules of engagement for combat. (e.)Most of these rules and rituals revolve around the idea of minimizing collateral damage, the efficiency of each warrior by holding their own, as well as the intent to minimize the waste of resources in a battle or campaign.
(f.)Anyone who knows about the Clans in the BattleTech lore would know that this is by far a vague description of who the cans are, and their vastly complex society and culture. This is just a start and prelude for new players, better materials and resources can be found under the "About The Clans" section in our website.

§779.1.1 b
We are Warden Doctrine

(i.) SLP is not only a "Clan based faction" but a Warden based Clan faction. (a.)In short the Wardens mostly believe that Aleksandr intended the remaining forces of the SLDF in exile to watch over and protect the Inner Sphere as the old Star League once did, and when the time was right they would approach the Inner Sphere to rebuild the new Star League. (b.)Where the Crusaders lean towards thinking the Inner Sphere should be conquered and ruled by the new Star League.

(ii.) A better understanding of the Warden Clans' beliefs and political standings can be achieved by reading the excerpt "Defenders of The True Faith" from the Warden Clans Field Manual.

§779.1.2
Enhancing the Clan Experience Doctrine

(i.) First of all if you already know a great deal about the clans, their way of life, their history, and their language then all you need to do is to skip to step four, otherwise read the rest to learn how your character should be based.
(ii.) You should have read through the sections on the "About The Clans" page if you do not know much about the Clans right now.
(iii.) You should have a fair understanding the clan language/terminology. We have a small collection of their "Terminology" in our site under the About The Clans page. Become familiarized in the clan language for fluent usage in the game. You must also come to understand that the language is highly respected in the Clans, and the use of contractions are a forbidden taboo. However over the years the language has become straggled with many hyphenations abbreviations and buzzwords to convey the most amount of meaning with the least amount of words.
(iv.) You then use what you now have learned aboutthe Clans, Warden Clans, and Clan terminology to make an "alternate personality" that you will use inside the MechWarrior online community. Do what a Warden warrior would do, say what a Warden warrior would say, and think what a Warden warrior would think. Aggression and somewhat of disrespect may be shown towards the Crusader Clans, lower casts, and freeborns is highly promoted. But it all must be displayed and conducted as a sense that everyone can understand that it is a little role-play of BattleTech lore. But try to play along with the character format when in real-time. When someone speaks in character it is mostly playful remarks that was said to add flavor to the game.

§779.2.1
Real-Time and Fast-Pace Modes

(i.)There are two modes of operations in SLP; one mode supports the role-playing formalities of clan character, and the other drops allot of the role-playing formalities to streamline meetings ceremonies and trials when time is of the essence.

(ii.) Real-Time Mode
When running in “Real-Time” everyone uses their clan character. All the ceremonial protocols and procedures are performed. All Clan Terminology will be used to the best of our abilities. If you were to sit back and watch SLP operate in Real-Time, it would be like watching the Clan ceremonies trails and culture you read out of a BattleTech novel come to life. Trying to operate under Real-Time may become hard for people who are new to BattleTech and/or the Clans. Real-Time Mode is the standard setting for SLP, and everything should be carried out in Real-Time unless told differently by a senior member of the Keshik.

(iii.) Fast-Pace Mode
“Fast-Pace” is an accelerated procedure that allows clan business to be executed in a quick and timely fashion by dropping all the extra enhancements and protocols to role-playing Clan society & culture. Fast-Pace is put into effect by a senior member of the Keshik when there is a need to get a large list of things done quickly. After the list of objectives are completed, the mode automatically returns to Real-Time, unless otherwise stated.

§779.3.1
The Rules of Zellbrigen

(i.)Zellbrigen is a Clan term describing the body of rules used to regulate and ritualize duels. In SLP there are four levels of Zellbrigen known as Zell-0, Zell-01, Zell-2, and Zell-3. As the higher Zell level goes the more rules and restrictions to combat that apply.

(ii.)Zell-0:
(a.)No targeting rules or engagement restrictions apply. Zell-0 would be known amongst the clans as a "melee" ware no rules or restrictions apply to combat, however this rule is not related to the Star Melees and Grand Melees held in SLP.

(iii.)Zell-1:
(a.)Targeting Rules: No legging or chaining.
(b.)Engagement Restrictions: None
(c.)Zell-1 is standard policy for SLP servers. It is also offered as a common courtesy and good sportsmanship in addition to house rules by SLP members who are a guest in other servers. However this courtesy does not have to be offered if it is being exploited against the player.

(iv.)Zell-2:
(a.)Targeting Rules: No legging or chining. A pilot may not fire upon the rear of a mech.
(b.)Engagement Restrictions: None
(c.)This is the standard policy for most trials and melees in SLP.

(v.)Zell-3:
(a.)Targeting Rules: No legging or chaining. A pilot may not fire upon the rear or cockpit of a mech. A pilot may not fire upon a shutdown mech.
(b.)Engagement Restrictions: A pilot will only engage upon one target at a time. At no point in time should a pilot in combat engage with multiple targets, or fire upon a target already engaged. If at any point a pilot fires upon multiple targets the stricken target may engage this pilot.
(c.)This is a rare policy in SLP, mostly used to spice up the game a bit from time to time.


Section 780
Advancement in Rank

In Section 780:
"Lower Ranks" is defined as the ranks and/or ranking members from Cadet to Nova Captain.
"Command Ranks" is defined as the ranks and/or ranking members from Star Colonel to Galaxy Commander.
"Upper Command Ranks" or "Upper Command" is defined as the ranks or ranking members of; Galaxy Colonel, saKhan, and Khan.
"Match" is defined as a rated match against another clan and or players, or a rated match within SLP.

§780.1.1
The Lower Ranks

(i.)Advancement through the Lower Ranks is achieved through a Trial of Position (see Section 781 for First Blooding, Blooding, and Trial of Position for ToP rules and procedures). The Lower Ranks include; Cadet, MechWarrior, Point Commander, Star Commander, Nova Commander, Star Captain, and Nova Captain.
(ii.)A member advancing through the Lower Ranks must meet these conditions: (a.)must be evaluated as an "Active" member, (b.)must not be currently suspended from a rank advancement, (c.)and no SLP member present at the time of the ToP has a viable reason to deny rank advancement.

(iii.)To be considered an "Active" member, the member must have met the minimal requirements of activity within the clan for their current rank for the past 15 days in accordance to their database record, excluding all Leave of Absences unless the LOAs are considered to be excessive by the Keshik.
(iv.)Advancements to any rank will be denied if there is a currently pending suspension denying rank advancement.
(v.)Present senior members of the Keshik will decide if any objection to deny rank advancement is a viable objection. If the objection is considered viable the ToP will be postponed until the Keshik can review and discuss the matters to see if the rank advancement is to be denied.
(vi.)Any successful Lower Rank advancement can be voided up to 15 days after the ToP was held if a viable reason was found and proven to deny that rank advancement.

§780.1.2
The Command Ranks

(i.)Advancing into and through the Command Ranks must be first voted upon, and then achieved through a ToP (see Section 781.1.3 for ToP rules and procedures). The Command Ranks include; Star Colonel, Nova Colonel, and Galaxy Commander.
(ii.)A member advancing into the Command Ranks (to the rank of Star Colonel) must meet these conditions: (a.)must succeed the voting process for their advancing rank, (b.)must be evaluated as an "Active" member, (c.)must not be currently suspended from a rank advancement, (d.)and no SLP member present at the time of the ToP has a viable reason to deny rank advancement.
(iii.)A member advancing through the Command Ranks (to the rank of Nova Colonel and Galaxy Commander) must meet these conditions: (a.)must succeed the voting process for their advancing rank, (b.)must be evaluated as an "Active" member, (c.)must not be currently suspended from a rank advancement, (d.)and no SLP member present at the time of the ToP has a viable reason to deny rank advancement.
(iv.)The voting and ToP will be held at the soonest Clan Meeting available to assure the most amount of members present for voting, viable objections, and bidding.

(v.)To be voted into the Command Ranks, the member must meet a 2/3rds (or 66%) vote by the present members of the Senior Keshik to advance into the Commanding Rank.
(vi.)To be considered an "Active" member for advancing into the Command Ranks, the member must have met the minimal requirements of activity within the clan for their current rank for the past 30 days in review of their database record, excluding all Leave of Absences unless the LOAs are considered to be excessive by the Keshik.
(vii.)Advancements to any rank will be denied if there is a currently pending suspension denying rank advancement.
(viii.)Present senior members of the Keshik will decide if any objection to deny rank advancement is a viable objection. If the objection is considered viable the ToP will be postponed until the Keshik can review and discuss the matters to see if the rank advancement is to be denied.
(ix.)Any successful advancement into the Command Ranks can be voided up to 30 days after the ToP was held if a viable reason was found and proven to deny that rank advancement.

(x.)To be voted through the Command Ranks, (a.)the must meet a 2/3rds (or 66%) vote by the present members of the Senior Keshik to advance through the Command Ranks, (b.)and must meet a 1/2 (or 50%) vote by the present members of the clan (who are not members of the Senior Keshik).
(xi.)To be considered an "Active" member for advancing through the Command Ranks, the member must have met the minimal requirements of activity within the clan for their current rank for the past 30 days in review of their database record, excluding all Leave of Absences unless the LOAs are considered to be excessive by the Keshik.
(xii.)Advancements to any rank will be denied if there is a currently pending suspension denying rank advancement.
(xiii.)Present senior members of the Keshik will decide if any objection to deny rank advancement is a viable objection. If the objection is considered viable the ToP will be postponed until the Keshik can review and discuss the matters to see if the rank advancement is to be denied.
(xiv.)Any successful advancement through the Command Ranks can be voided up to 30 days after the ToP was held if a viable reason was found and proven to deny that rank advancement.

§780.1.3 a
The Upper Command

(i.)Advancement through the Upper Command Ranks is achieved by first gaining candidacy via rank and seniority, and then final candidacy election is decided upon by the Senior Keshik. The Keshik and members of SLP then vote upon advancing the candidate(s) into rank. The Upper Command Ranks include; Galaxy Colonel, saKhan, and Khan.

(ii.)Candidacy by rank is electing by default a member of the next lowest rank to become a final candidate for this advancement. There may be other factors that can change a candidate by rank from being a final candidate for the open Upper Command Rank, (a.)the candidate may be denied final candidacy by the Senior Keshik if they find the candidate unfit for the rank, (b.)the candidate my also respectfully decline becoming a final candidate for personal reasons.

(iii.)Candidacy by seniority is electing by default members of the same rank by the amount of time they have served in SLP. There may be other factors that can change a candidate by seniority from being a final candidate for the open Upper Command Rank, (a.)the candidate may be denied final candidacy by the Senior Keshik if they find the candidate unfit for the rank, (b.)the candidate my also respectfully decline becoming a final candidate for personal reasons.

(iv.)If an inadequate final candidate can be found in the next lowest rank to advance into the open Upper Command Rank, or there is a possible better suiting member outside the default candidacy by rank or seniority they may also be elected as a final candidate. By default if there is no suitable final candidate in the next lower rank level, the candidacy selection then goes to the next lower rank. There is no minimum rank required to select member to be elected into the final candidacy to fill the open Upper Command Rank, the member just has to be agreed upon by the Senior Keshik to be a fitting and suitable individual for the open Upper Command Rank.

(v.)Once the Senior Keshik has found their final candidate(s); (a.)If there are more than two final candidates the members of the clan present at the meeting will hold a vote upon which of the two final candidates will face off for the open Upper Command Rank. (b.)Once there are two final candidates they will face each other in a Moderated Circle of Equals (see Section 781.3.4 for Moderated CoE), the victor of the Moderated CoE will be the winner of "two out of three" while upholding Zell-3 during the CoE. (c.)If/once it is down to one final candidate the Senior Keshik holds a final vote and members of SLP (who are not a member of the Senior Keshik) hold a final vote to elect the final candidate into the open Upper Command Rank. (d.)If the final votes pass, the final candidate takes on his/her new rank. (e.)If the final votes fail, the Senior Keshik must start the candidacy selection over again excluding the individual who failed the final votes. This entire process is to be repeated as many times as needed until the final votes pass. (f.)To save time, if the final votes fail only by a little (a few votes) the Senior Keshik may choose to address all present members of SLP if there is any objection to the letting the chosen final candidate to have this rank in the Upper Command. Any objections must have an arguable reason(s) stated with their objection, if the reason is found arguable by the majority of the Senior Keshik then candidacy process will start over.

(vi.)A member of the Upper Command Ranks may retire from SLP or step down from their rank, if this is done the member may request an heir/replacement (of any rank) to their Upper Command Rank. If an heir/replacement is requested this individual will automatically become a final candidate (and will only need the approval of one other member of the Upper Command Ranks as stated below instead of both). A member of the Upper Command choosing to step down from his/her rank will by default be stepping down to the rank of Galaxy Commander unless further demotion is requested (or as seen fit by the Senior Keshik).
(vii.)A member of the Upper Command Ranks may also be reviewed and found by the Senior Keshik to be unfit to carry out the responsibilities and duties of their current rank. The Senior Keshik will hold a meeting to find out what rank (if any) will respectfully best suit this member and SLP.

§780.1.3 b
Advancing to Galaxy Colonel

(i.)To first become a candidate for Galaxy Colonel the individual needs the approval of the existing Khan and saKhan in the candidacy selection, further discussion by the Senior Keshik may occur to sway the approval of the Khan and/or saKhan on why this individual should be a candidate.
(ii.)Once the Senior Keshik believe they have their best suitable candidate(s) for a new Galaxy Colonel, the candidate(s) will go onto their respective process as outlined in §780.1.3a.
(iii.)The final votes to pass a member into the Upper Command Rank of Galaxy Colonel must meet 3/4ths (or 75%) by members of the Senior Keshik, and 2/3rds (or 66%) by the members of SLP (who are not a member of the Senior Keshik).

§780.1.3 c
Advancing to saKhan

(i.)To first become a candidate for saKhan the individual needs the approval of the existing Khan and Galaxy Colonel in the candidacy selection, further discussion by the Senior Keshik may occur to sway the approval of the Khan and/or Galaxy Colonel on why this individual should be a candidate.
(ii.)Once the Senior Keshik believe they have their best suitable candidate(s) for a new saKhan, the candidate(s) will go onto their respective process as outlined in §780.1.3a.
(iii.)The final votes to pass a member into the Upper Command Rank of saKhan must meet 3/4ths (or 75%) by members of the Senior Keshik, and 3/4ths (or 75%) by the members of SLP (who are not a member of the Senior Keshik).

§780.1.3 d
Advancing to Khan

(i.)To first become a candidate for Khan the individual needs the approval of the existing saKhan and Galaxy Colonel in the candidacy selection, further discussion by the Senior Keshik may occur to sway the approval of the saKhan and/or Galaxy Colonel on why this individual should be a candidate.
(ii.)Once the Senior Keshik believe they have their best suitable candidate(s) for a new Khan, the candidate(s) will go onto their respective process as outlined in §780.1.3a.
(iii.)The final votes to pass a member into the Upper Command Rank of Khan must meet 9/10ths (or 90%) by members of the Senior Keshik, and 4/5ths (or 80%) by the members of SLP (who are not a member of the Senior Keshik).

§780.2.1
Ranks, Rights, and Duties

(i.)In SLP each advancing rank charges its members with more duties to SLP. And each rank is given rights to effectively perform their respective duties.

(ii.)Descriptions of the basic duties:
(a.)"Learning the way of the clan" - Members with this duty are to learn most of the common and basic practices and procedures of SLP.
(b.)"Teaching the ways of the clan to Cadets" - Members with this duty are to help the Cadets learn and understand the practices and procedures in SLP.
(c.)"The Advancement and progression of SLP" - Members with this duty are to aid in Clan Meetings and discussion to better progress SLP forward.
(d.)"Securing the integrity of SLP by screening cadets" - Members with this duty are to watch over the cadets making sure they have the potential of being a good addition as full members of SLP.
(e.)"Learning the ways of the Keshik" - Members with this duty are to learn the practices and procedures that the Senior Keshik partake on.
(f.)"Securing the integrity of SLP by screening advancing warriors" - Members with this duty are to watch over the members of SLP making sure they have the potential to take on the responsibilities and duties of their next rank.
(g.)"Teaching the ways of the Keshik to Junior Keshik members" - Members with this duty are to help instruct and show members of the Junior Keshik of the practices and procedures of the Senior Keshik.
(h.)"Learning the ways of the Upper Command" - Members with this duty are to learn the responsibilities practices and procedures of the Upper Command Ranks.
(i.)" Performing the tasks of the Upper Command (Third in Command)" - Members with this duty are to watch over the members of the clan making sure they are heading in the right direction, making sure that the SLP online gaming unit is heading in the right direction. Advise the Khan and saKhan with topics that pertain to the Upper Command. And perform any task given to him/her by the Khan and/or saKhan.
(j.)" Performing the tasks of the Upper Command (Second in Command)" - Members with this duty are to watch over the members of the clan making sure they are heading in the right direction, making sure that the SLP online gaming unit is heading in the right direction. Advise the Khan with topics that pertain to the Upper Command. And perform any task given to him/her by the Khan. Taking over the duties of the Khan in his/her time of absence.
(k.)" Performing the tasks of the Upper Command (First in Command)" - Members with this duty are to actively watch over the SLP online gaming unit is heading in the right direction. Represent SLP diplomatically to other online gaming units and alliances.

(iii.)The Greater Good Policy
TGGP is a special right granted to each of the Upper Command Ranks that allow them to step out and perform actions that "bend" or "break" the rules and laws of SLP as they see fit.
When a member of the Upper Command exorcizes TGGP they must justify themselves to the Senior Keshik on why they exorcized TGGP, and how it benefitted "the greater good" of SLP. If the Keshik fail to see how the action(s) benefitted SLP the member may have reparations to undergo that the Keshik see fit.
(iv.)TGGP may be invoked by the Galaxy Colonel if the Khan and SaKhan have been out of contact for 72 hours. TGGP may be invoked by the if the saKhan has been out of contact for 72 hours. TGGP may be invoked by the Khan at any time.

(v.)The Ranks and their rights and duties:

(a.)Cadet
-Junior Member of SLP
(1.)May observe SLP meetings.
(2.)May only observer in all other ceremonies.
(3.)May only participate in clan business when asked upon by a member of the Keshik.
(4.)May participate in matches, yielding to full members.
Duties include; (I.)learning the ways of the clan.

(b.)MechWarrior
-Full member of SLP
(1.)May participate in SLP meetings.
(2.)May participate in clan business as a full member of SLP.
(3.)May participate in the First Blooding ceremonies.
(4.)May participate in Star Melees and Grand Melees.
(5.)May participate in matches, yielding to members of the Keshik.
Duties include; (I.)teaching the ways of the clan to Cadets, (II.)learning he ways of the clan, (III.)the advancement and progression of SLP.

(c.)Point Commander
(1.)May participate in SLP meetings.
(2.)May participate in clan business as a full member of SLP.
(3.)May participate in the First Blooding ceremonies.
(4.)May participate in the Blooding ceremonies.
(5.)May participate in matches, yielding to members of the Keshik.
Duties include: (I.)teaching the ways of the clan to Cadets and members of SLP, (II.)learning he ways of the clan, (III.)the advancement and progression of SLP.

(d.)Star Commander
-No additional rights or duties given to this rank at this point in time.
(1.)May participate in SLP meetings.
(2.)May participate in clan business as a full member of SLP.
(3.)May participate in the First Blooding ceremonies.
(4.)May participate in the Blooding ceremonies.
(5.)May participate in matches, yielding to members of the Keshik.
Duties include: (I.)teaching the ways of the clan to Cadets and members of SLP, (II.)learning he ways of the clan, (III.)the advancement and progression of SLP.

(e.)Nova Commander
(1.)May participate in SLP meetings.
(2.)May participate in the conduction and recording of SLP meetings as a LoreMaster, submitting all records to the Archives and to a senior member of the Keshik.
(3.)May participate in clan business as a full member of SLP.
(4.)May participate in the First Blooding ceremonies.
(5.)May participate in the Blooding ceremonies.
(6.)May participate in matches, yielding to members of the Keshik.
Duties include: (I.)teaching the ways of the clan to Cadets and members of SLP, (II.)the advancement and progression of SLP.

(f.)Star Captain
(1.)May participate in SLP meetings.
(2.)May participate in the conduction and recording of SLP meetings as a LoreMaster, submitting all records to the Archives and to a senior member of the Keshik.
(3.)May participate in clan business as a full member of SLP.
(4.)May participate in the First Blooding ceremonies.
(5.)May participate in the Blooding ceremonies.
(6.)May vouch for a Cadet to become a full member of SLP on their Blooding Trial to the rank of MechWarrior.
(7.)May participate in matches, yielding to members of the Keshik.
Duties include: (I.)teaching the ways of the clan to Cadets and members of SLP, (II.)the advancement and progression of SLP.

(g.)Nova Captain
-No additional rights or duties given to this rank at this point in time.
(1.)May participate in SLP meetings.
(2.)May participate in the conduction and recording of SLP meetings as a LoreMaster, submitting all records to the Archives and to a senior member of the Keshik.
(3.)May participate in clan business as a full member of SLP.
(4.)May participate in the First Blooding ceremonies.
(5.)May participate in the Blooding ceremonies.
(6.)May vouch for a Cadet to become a full member of SLP on their Blooding Trial to the rank of MechWarrior.
(7.)May participate in matches, yielding to members of the Keshik.
Duties include: (I.)teaching the ways of the clan to Cadets and members of SLP, (II.)securing the integrity of SLP by screening cadets, (III.)the advancement and progression of SLP.

(h.)Star Colonel
-Junior Member of the Keshik.
(1.)May observe Keshik meetings.
(2.)May participate in SLP meetings.
(3.)May participate in the conduction and recording of SLP meetings as a LoreMaster, submitting all records to the Archives and to a senior member of the Keshik.
(4.)May participate in clan business as a full member of SLP.
(5.)May participate in the First Blooding ceremonies.
(6.)May participate in the Blooding ceremonies.
(7.)May vouch for a Cadet to become a full member of SLP on their Blooding Trial to the rank of MechWarrior.
(8.)May vouch for a member of SLP to advance in rank on their Blooding Trial as long as they do not advance above Star Colonel.
(9.)May participate in matches, yielding to senior members of the Keshik.
Duties include: (I.)learning the ways of the Keshik, (II.)teaching the ways of the clan to Cadets and members of SLP, (III.)securing the integrity of SLP by screening cadets and advancing warriors, (IV.)the advancement and progression of SLP.

(i.)Nova Colonel
-Senior Member of the Keshik.
(1.)May participate in Keshik meetings.
(2.)May participate in SLP meetings.
(3.)May participate in the conduction and recording of SLP meetings as a LoreMaster, submitting all records to the Archives.
(4.)May participate in clan business as a full member of SLP.
(5.)May participate in the First Blooding ceremonies.
(6.)May participate in the Blooding ceremonies.
(7.)May vouch for a Cadet to become a full member of SLP on their Blooding Trial to the rank of MechWarrior.
(8.)May vouch for a member of SLP to advance in rank on their Blooding Trial as long as they do not advance above Star Colonel.
(9.)May participate in matches, yielding to decisions of the Keshik.
Duties include: (I.)teaching the ways of the Keshik to Junior Keshik members, (II.)teaching the ways of the clan to Cadets and members of SLP, (III.)securing the integrity of SLP by screening cadets and advancing warriors, (IV.)the advancement and progression of SLP.

(j.)Galaxy Commander
-No additional rights or duties given to this rank at this point in time.
Senior Member of the Keshik
(1.)May participate in Keshik meetings.
(2.)May participate in SLP meetings.
(3.)May participate in the conduction and recording of SLP meetings as a LoreMaster, submitting all records to the Archives.
(4.)May participate in clan business as a full member of SLP.
(5.)May participate in the First Blooding ceremonies.
(6.)May participate in the Blooding ceremonies.
(7.)May vouch for a Cadet to become a full member of SLP on their Blooding Trial to the rank of MechWarrior.
(8.)May vouch for a member of SLP to advance in rank on their Blooding Trial as long as they do not advance above Star Colonel.
(9.)May participate in matches, yielding to decisions of the Keshik.
Duties include: (I.)learning the ways of the Upper Command, teaching the ways of the Keshik to Junior Keshik members, (II.)teaching the ways of the clan to Cadets and members of SLP, (III.)securing the integrity of SLP by screening cadets and advancing warriors, (IV.)the advancement and progression of SLP.

(k.)Galaxy Colonel
-Third in Command.
(1.)May participate in Keshik meetings.
(2.)May participate in SLP meetings.
(3.)May participate in the conduction and recording of SLP meetings as a LoreMaster, submitting all records to the Archives.
(4.)May participate in clan business as a full member of SLP.
(5.)May participate in the First Blooding ceremonies.
(6.)May participate in the Blooding ceremonies.
(7.)May vouch for a Cadet to become a full member of SLP on their Blooding Trial to the rank of MechWarrior.
(8.)May vouch for a member of SLP to advance in rank on their Blooding Trial as long as they do not advance above Star Colonel.
(9.)May participate in matches.
(10.)May exorcize TGGP if Khan and SaKhan have been out of contact for 72Hrs.
Duties include: (I.)performing the tasks of the Upper Command (Third in Command), (II.)teaching the ways of the Keshik to Junior Keshik members, (III.)securing the integrity of SLP by screening cadets and advancing warriors, (IV.)the advancement and progression of SLP.

(l.)saKhan
-Second in Command
(1.)May exorcize TGGP if Khan has been out of contact for 72Hrs.
(2.)May participate in Keshik meetings.
(3.)May participate in SLP meetings.
(4.)May participate in the conduction and recording of SLP meetings as a LoreMaster, submitting all records to the Archives.
(5.)May participate in clan business as a full member of SLP.
(6.)May participate in the First Blooding ceremonies.
(7.)May participate in the Blooding ceremonies.
(8.)May vouch for a Cadet to become a full member of SLP on their Blooding Trial to the rank of MechWarrior.
(9.)May vouch for a member of SLP to advance in rank on their Blooding Trial as long as they do not advance above Star Colonel.
(10.)May participate in matches.
Duties include: (I.)performing the tasks of the Upper Command (Second in Command), (II.)teaching the ways of the Keshik to Junior Keshik members, (III.)securing the integrity of SLP by screening cadets and advancing warriors, (IV.)the advancement and progression of SLP.

(m.)Khan
-First in Command.
(1.)May exorcize TGGP at any time.
(2.)May participate in Keshik meetings.
(3.)May participate in SLP meetings.
(4.)May participate in the conduction and recording of SLP meetings as a LoreMaster, submitting all records to a Senior member of the Keshik.
(5.)May participate in clan business as a full member of SLP.
(6.)May participate in the First Blooding ceremonies.
(7.)May participate in the Blooding ceremonies.
(8.)May vouch for a Cadet to become a full member of SLP on their Blooding Trial to the rank of MechWarrior.
(9.)May vouch for a member of SLP to advance in rank on their Blooding Trial as long as they do not advance above Star Colonel.
(10.)May participate in matches.
Duties include: (I.)performing the tasks of the Upper Command (First in Command), (II.)teaching the ways of the Keshik to Junior Keshik members, (III.)securing the integrity of SLP by screening cadets and advancing warriors, (IV.)the advancement and progression of SLP.

§780.3.1
Becoming an Officer of a Star/Binary

(i.)Any member with the rank of Nova Colonel on up may become a Commanding Officer of a star/binary. By taking the path to becoming a CO you are choosing a path that requires more time dedication and diligent care to be devoted towards SLP. Some may find becoming a CO a meaningful goal in SLP ware they have a handful of members that they personally command over, however these individuals have to understand that they need to take the all of the responsibility required to do so.

(ii.)For a member of rank wishing to become a CO of their own star in the Alpha Galaxy will only be allowed to do so if; (a.)There are sufficient active members, there needs to be at least three active members in the Zeta Garrison Cluster who can join up into the new star. (b.)If there are two or more members awaiting their own star, (1.)the member of the highest rank has priority, (2.)if the members are of the same rank the member with the highest seniority has priority.

(iii.)Once the member has been granted to become a CO of his/her own star in the Alpha Galaxy, the Keshik and their star-mates have expectations of them to command the star.
(a.)You are expected to make Weekly Star Reports in a timely fashion, (1.)these reports cover the events that the star partook on, (2.)they must also report the status on each member of the star including their activity level, and any other notes that will be openly shared with all members of SLP. (b.)The reports are to be filled out and handed in every Friday night after the Keshik Meeting, COs are given a grace period of having been submitted the following Saturday 24:00 -6:00 UT, any submission after that are considered late. A late submission will cause a review of your ability to lead a star by the Keshik, repeated late submissions may cause you to lose your commanding position in the star as well as other reparations.
(c.)As the CO you are also role-model to your star-mates, this will require a higher amount of activity, not only to encourage your star-mates to be more active, but to monitor them as well.
The minimum participation for a CO is; (1.)Showing up and playing up at least four days out of the week (there appearance should be for at least two hours each day), One of these nights should be partaking in the Clan Meeting and Keshik Meeting. (2.)Must actively partake in discussions within their star as well as other discussions. (3.)Must make active and timely submissions to the Archives pertaining to their star and its members.
(d.)The CO must also support and coax the activity amongst star-mates in a constructive manner.
(e.)The CO is responsible for setting up Matches for his/her star, and should do so by consulting with all his/her star-mates to set up a time in which every star-mate can participate (or make an effort to include every star-mate) in a timely fashion.

(iv.)A CO can remove and/or replace inactive members in their star. (a.)A CO may replace a star-mate if he/she goes to the status of MIA-1 twice in a 60 day time-frame. (b.)A CO can remove a star-mate if he/she goes to the activity of MIA-1 twice in a 60 day time-frame. (c.)A CO can also request permission from the Keshik to replace a star-mate with a minim activity record.

(v.)A CO must ensure that his/her star does not fall below three members (including the CO) at any time, in this case they can lose command of their star. If a star has been at only three members for more than a week, the situation may be looked into by the Keshik to permanently dissemble the star to place the active members to fill other stars in times of need.

(vi.)A CO must appoint an XO of his/her star. The likely candidate for his/her XO is usually the next highest ranking member with the most seniority, however the CO has to be sure that the star-mate they choose as the XO will be responsible enough to carry out the CO's duties in their time of absence. The CO is also responsible for training their XO in the duties of submitting the Weekly Reports and other responsibilities of the CO.
The CO must list and show their current XO in his/her star's board on the forum.

(vii.)(a.)As an XO of a star in the Alpha Galaxy; (1.)He/she must be able and ready to take over the command and record keeping of the star at any time. (2.)The Keshik or CO may call upon the XO to lead the star temporarily taking on the above duties and responsibilities of the CO. (3.)The XO should be keeping a current record of the star in case they have to submit the Weekly Report at any time in the absence of the CO. (b.)The XO is not permitted to replace add or remove star-mates by themselves, he/she must first consult the Keshik and get permission to do so.

(viii.)For a member of rank wishing to become a CO of a binary in the Beta Galaxy will only be allowed to do so if; (a.)There are sufficient active members, there needs to be at least one active member in the binary for a CO to take command of it. (b.)If there are two or more members awaiting command of a binary, (1.)the member of the highest rank has priority, (2.)if the members are of the same rank the member with the highest seniority has priority.

(ix.)Once the member has been granted to become a CO of a binary in the Beta Galaxy, the Keshik and their star-mates have expectations of them to command the binary.
(a.)You are expected to make Weekly Binary Reports in a timely fashion, (1.)these reports cover the events that the binary partook on, (2.)they must also report the status on each member of the binary including their activity level, and any other notes that will be openly shared with all members of SLP. (b.)The reports are to be filled out and handed in every Friday night after the Keshik Meeting, COs are given a grace period of having been submitted the following Saturday 24:00 UTC -6:00, any submission after that are considered late. A late submission will cause a review of your ability to lead a binary by the Keshik, repeated late submissions may cause you to lose your commanding position in the binary as well as other reparations.
(c.)As the CO you are also role-model to your binary-mates, this will require a higher amount of activity, not only to encourage your binary-mates to be more active, but to monitor them as well.
The minimum participation for a CO is; (1.)Showing up and playing up at least four days out of the week (there appearance should be for at least two hours each day), One of these nights should be partaking in the Clan Meeting and Keshik Meeting. (2.)Must actively partake in discussions within their star as well as other discussions. (3.)Must make active and timely submissions to the Archives pertaining to their binary and its members.
(d.)The CO must also support and coax the activity amongst binary-mates in a constructive manner.
(e.)The CO is responsible for setting up Matches for his/her binary, and should do so by consulting with all his/her binary-mates to set up a time in which every binary-mate can participate (or make an effort to include every binary-mate) in a timely fashion.

(x.)Any member with the rank of Nova Captain on up may become an XO of a binary. (a.)For a member of rank wishing to become a XO of a binary in the Beta Galaxy will only be allowed to do so if; (b.)There are sufficient active members, there needs to be at least one active member in the binary for a XO to take XO command of it. (b.)If there are two or more members awaiting XO command of a binary, (1.)the member of the highest rank has priority, (2.)if the members are of the same rank the member with the highest seniority has priority.

(xi.)(a.)As an XO of a binary in the Beta Galaxy; (1.)He/she must be able and ready to take over the command and record keeping of the binary at any time. (2.)The Keshik or CO may call upon the XO to lead the binary temporarily taking on the above duties and responsibilities of the CO. (3.)The XO should be keeping a current record of the binary in case they have to submit the Weekly Binary Report at any time in the absence of the CO.

(xii.)A star/binary-mate of the rank Galaxy Commander or higher may challenge the CO for command of the star/binary, as long as the challenger has member in that star/binary for the past consecutive 60 days.
(a.)During the weekly meeting a star/binary-mate of rank can issue this challenge to his/her CO for command, however the present Keshik members must first approve of the challenge.
(b.)If the Keshik approves of the challenge the existing CO and ranking star/binary-mate are to enter a Moderated CoE using Zell-3, the best 2 out of 3 will obtain/retain the command of the star/binary.
(c.)The victor will remain the CO of the star/binary until another challenge is issued.
(d.)A challenge can only be issued 30 days after the last challenge was made.
(e.)If multiple star/binary-mates are of rank and both wish to challenge the CO for command, and the Keshik approves of all challengers, a Moderated CoE using Zell-2 will occur with all approved challengers, the last man standing will earn the right to enter the CoE with the CO for command of the star/binary.
(f.)In most cases, unless otherwise stated by the Keshik, the CO who loses the command of his star/binary to the challenger will by default become the XO of that star/binary.


Section 781
General Procedures to Trials

In Section 781:
"OathMaster" is defined as the LoreMaser.
"Warrior" is defined as a member of SLP.
"Test-down" is defined as declining in rank during a ToP.

§781.1.1
The First Blooding

(i.)The "First Blooding" is the initiation ceremony of a joining candidate to SLP.

(ii.)Procedures:
(a.)The OathMaster must state the candidate’s name, asking if there are any objections to the candidate joining SLP.
(b.)Objectors are to state their objection and give there reason(s) why they object.
(c.)The candidate selects their tonnage and the bidding begins. (during fast-pace try to avoid CoEs on your biddings if possible)
(d.)OathMaster states the results of the First Blooding.

(iii.)Rules:
(a.)To be a valid Trial of Position there must be at least 3 members present; (1.)a ranking member of Star Colonel or higher to give the consent of the trail, (2.)the person on trial who wishes to join SLP, (3.)and at least one witness to the trail.
(b.)Next step is the bidding process. (1.)The joining candidate must state what is the tonnage of the BattleMech he/she wishes to use in the trail, this will set the starting bid. (2.)Members present of MechWarrior or higher may bid upon the trial, when someone bids to trail, they are bidding on the tonnage of the Mech they will use against the joining candidate, they try to bid a lower tonnage than everyone else. (3.)No bid can fall below 35 tons than the starting bid. Once the bidding is done, the lowest bidder gets to choose the map on which the trail will take place. (4.)All conflicting lowest bids will be settled by a Moderated CoE.
(c.)Next is the trail. (1.)The trial will last 10 minutes. (2.)All witnesses to the trail are to select a camera ship. (3.)At the end of the game, the joining candidate must make at least one kill to join SLP.

§781.1.2
The Blooding

(i.)The "Blooding" is the ceremony and trial of a Cadet wishing to advance into the rank of MechWarrior becoming a full member of the clan.

(ii.)Procedures:
(a.)The OathMaster must state the candidate’s name, asking if there are any objections to the candidate advancing to MechWarrior.
(b.)Objectors are to state their objection and give there reason(s) why they object.
(c.)The candidate selects their tonnage and the bidding begins. (during fast-pace try to avoid CoEs on your biddings if possible)
(d.)OathMaster states the results of the blooding.

(iii.)Rules:
(a.)After 30 days from the First Blooding trial a cadet can request a Blooding trial to become a MechWarrior.
(b.)To be a valid Trial of Position there must be at least 3 members present; (1.)a ranking member of Star Colonel or higher to give the consent of the trail, (2.)the person on trial who wishes to advance in rank, (3.)and at least one witness to the trail.
(c.)Next step is the bidding process. (1.)The Cadet must state what is the tonnage of the BattleMech he/she wishes to use in the trail, this will set the starting bid. (2.)Members present of MechWarrior or higher may bid upon the trial, when someone bids to trail, they are bidding on the tonnage of the Mech they will use against the candidate, they try to bid a lower tonnage than everyone else. (3.)No bid can fall below 35 tons than the starting bid. Once the bidding is done, the lowest bidder gets to choose the map on which the trail will take place. (4.)All conflicting lowest bids will be settled by a Moderated CoE.
(d.)Next is the trail. (1.)The trial will last 10 minutes. (2.)All witnesses to the trail are to select a camera ship. (3.)At the end of the game, the candidate must make at least three kills to advance to MechWarrior.

§781.1.3
The Trial of Position

(i.)The" Trial of Position" is the trial in which a warrior wishes to advance in rank.

(ii.)Procedures:
(a.)The OathMaster must state the candidate’s name, asking if there are any objections to the candidate advancing to (advancing rank).
(b.)Objectors are to state their objection and give there reason(s) why they object.
(c.)The candidate selects their tonnage and the bidding begins. (during fast-pace try to avoid CoEs on your biddings if possible)
(d.)OathMaster states the results of the ToP.

(iii.)Rules:
(a.)After 30 days from their last rank advancement a member can request a TOP to advance in rank.
(b.)To be a valid Trial of Position there must be at least 3 members present; (1.)a ranking member of Star Colonel or higher to give the consent of the trail (as long as the candidate is not advancing above the rank of Star Colonel), (2.)the person on trial who wishes to advance in rank, (3.)and at least one witness to the trail.
(c.)Next step is the bidding process. (1.)The candidate must state what is the tonnage of the BattleMech he/she wishes to use in the trail, this will set the starting bid. (2.)Members present of Star Commander or higher may bid upon the trial (as long as the candidate is not advancing into a rank above theirs), when someone bids to trail, they are bidding on the tonnage of the Mech they will use against the candidate, they try to bid a lower tonnage than everyone else. (3.)No bid can fall below 35 tons than the starting bid. Once the bidding is done, the lowest bidder gets to choose the map on which the trail will take place. (4.)All conflicting lowest bids will be settled by a Moderated CoE.
(d.)Next is the trail. (1.)The trial will last 10 minutes. (2.)All witnesses to the trail are to select a camera ship. (3.)At the end of the game, the candidate must make their required kills to advance to their next rank.

(iv.)These are the required kills for each rank:
1 kill for Cadet
3 kills for Mech Warrior
4 kills for Point Commander
6 kills for Star Commander
7 kills for Nova Commander
9 kills for Star Captain
10 kills for Nova Captain
12 kills for Star Colonel
13 kills for Nova Colonel
15 kills for Galaxy Commander
16 kills for Galaxy Colonel
17 kills for saKhan
18 kills for Khan

§781.1.4
The Reblooding Trial

(i.)The "Reblooding Trial" is when a member comes back from an absence without leave lasting three weeks, or an absence of leave lasting two months or more without any game activity in SLP.

(ii.)A member who has taken a LOA for 30 days or longer, or a member that has gone MIA for three weeks must consult the Keshik upon returning to SLP, the Keshik may define a test-down for the member. Only during the Reblooding Trial is there a chance to test-down.

(iii.)Procedures:
(a.)The OathMaster must state the candidate’s name, asking if there are any objections to the candidate re-joining SLP.
(b.)Objectors are to state their objection and give there reason(s) why they object.
(c.)The candidate selects their tonnage and the bidding begins. (during fast-pace try to avoid CoEs on your biddings if possible)
(d.)OathMaster states the results of the Reblooding Trail.

(iv.)Rules:
(b.)To be a valid Reblooding Trial there must be at least 3 members present; (1.)a member of the Keshik to give the consent of the trial, (2.)the person on trial who wishes to rejoin SLP, (3.)and at least one witness to the trail.
(c.)Next step is the bidding process. (1.)The candidate must state what is the tonnage of the BattleMech he/she wishes to use in the trail, this will set the starting bid. (2.)Members present of Star Commander or higher may bid upon the trial (as long as the candidate is not advancing into a rank above theirs), when someone bids to trail, they are bidding on the tonnage of the Mech they will use against the candidate, they try to bid a lower tonnage than everyone else. (3.)No bid can fall below 35 tons than the starting bid. Once the bidding is done, the lowest bidder gets to choose the map on which the trail will take place. (4.)All conflicting lowest bids will be settled by a Moderated CoE.
(d.)Next is the trail. (1.)The trial will last 10 minutes. (2.)All witnesses to the trail are to select a camera ship. (3.)At the end of the game, the candidate must make their required kills to retain their rank, or test-down.

§781.2.1
The Star Melee

(i.)The "Star Melee" is a trial each star must undergo to select their candidate for the Grand Melee.

(ii.)Procedures:
(a.)The OathMaster must state the star’s name, and designate to the candidates to ready up for the Star Melee.
(b.)The candidates ready up, and the melee begins.
(c.)The OathMaster states the results of the melee, and congratulates the victor.
(d.)The Victor is given the chance to pass down his/her honor in the Grand Melee.

(iii.)Rules:
(a.)At the end of each quarter, each star from the Alpha Galaxy and each binary from the Zeta Garrison Cluster hold a Star Melee to elect their representing candidate in the Grand Melee.
(b.)The CO must schedule the Star Melee before for his/her star/binary at the end of March, June, September, and December.
(c.)All members of the star/binary will participate in a Moderated CoE using Zell-2. Last man standing wins the right to fight in the Grand Melee to represent their star/binary.
(e.)The winner of the Star Melee may pass on his/her place in the Grand Melee to another star-mate to fight in their honor.

§781.2.2
The Grand Melee

(i.)The "Grand Melee" is the trial that the ceremonial chosen candidates undergo for the honor of representing their star/binary and the glorious chance at earning a blood name.

(ii.)Procedures:
(a.)The OathMaster must state the Grand Melee’s Blood Name, and designate the candidates to ready up for the Grand Melee.
(b.)The candidates ready up, and the Grand Melee begins.
(c.)The OathMaster states the result of the Grand Melee, and congratulates the victor.

(iii.)Rules:
(a.)Once all participating stars/binaries have undergone their Star Melee to select their candidate, the Grand Melee is scheduled.
(c.)All selected candidates will participate in a Moderated CoE using Zell-2. Last man standing wins the right Grand Melee.
(d.)The winner of the Grand Melee gets to keep and use the chosen Blood Name of that Grand Melee.

§781.3.1
Moderated Circle of Equals

(i.)The "Moderated Circle of Equals" (otherwise known as a CoE) is held when two or more clansmen hold a difference of opinion and the resolution is carried out on the battlefield.

(ii.)Procedures:
(a.)The OathMaster states the challenger’s name and the challenge’s name, and designates the participants to ready up.
(b.)The participants ready up, and the CoE begins.
(c.)The OathMaster states the results of the CoE.

(iii.)Rules:
(a.)The participants in the CoE will name and agree upon the stakes in the CoE, if there are any to be made.
(b.)Traditionally the CoE is held in Zell-2, however the participants can agree upon what rules and restrictions apply, if any.
(c.)By standards the victor is declared in one round as the last man standing, however winning conditions are decided and agreed upon by all participants.
(d.)All participants must honor the outcome of the battle.
(e.)If the rules and or binding agreements were broking in the CoE, the offending party is to be reported to the Keshik for further settlement of the dispute.

§781.4.1
Trial of Grievance

(i.)The "Trial of Grievance" (or ToG) is an honor duel between two parties ware one party has been wronged by another party. The idealism and fundamentals of the ToG is "Justice by combat".

(ii.)Procedures:
(a.)The OathMaster states the challenger's name(s) and the challengie’s name(s).
(b.)The challenger(s) bid their force(s), and the challengie(s) accept the bid.
(c.)The participants ready up in a timely fashion, and the ToG begins.
(d.)The OathMaster states the result of the ToG

(iii.)Rules:
(a.)The participants in the ToG will name and agree upon the stakes in the ToG, if there are any to be made.
(b.)Traditionally the ToG is held in Zell-3, however the participants can agree upon what rules and restrictions apply, if any.
(c.)By standards the victor is declared in one round as the last man standing, however winning conditions are decided and agreed upon by all participants.
(d.)If the rules and or binding agreements were broking in the CoE, the offending party is to be reported to the Keshik for further settlement of the dispute.

§781.5.1
Trial of Refusal

(i.)(a.)A "Trial of Refusal" (or ToR) is given right where a when a warrior can decrease their chosen punishment(s) for their crime(s) or for the Keshik to re-evaluate their decision(s) by a warrior entering combat against two members of the Keshik. (b.)That is if the Keshik allows for a ToR upon their decision. (c.)If the Keshik agrees to a ToR for a reduction of punishment, members of the Keshik will discuss and decide upon the decreased punishment, and then declare the changes to the challenger. (d.)If the Keshik agrees to a ToR for a re-evaluation of their decision(s), the re-evaluation will take place after the ToG is won by the challenger.

(ii.)Procedures:
(a.)OathMaster states the challenger's name acknowledging that he/she wishes to refuse the Keshik's decision by a ToR.
(b.)The Keshik states their terms of the trial.
(c.)If the challenger declines the terms, the OathMaster states that the challenger chose surkai.
(d.)If the challenger agrees the trial progresses, and the challenger states their bid.
(e.)Keshik states their bids.
(f.)The participants ready up in a timely fashion and the ToR begins.
(g.)The OathMaster states the results of the ToR.

(iii.)Rules:
(a.)The Keshik will diced upon the two members of the Keshik that will face the challenger.
(b.)The challenger can only bid a mech between 50-100T.
(c.)The Keshik's combined bids may not exceed the challengers bid by more than 20T.
(d.)The ToR is held in Zell-3.
(e.)The victor is declared in one round as the last man standing.
(f.)If the rules are broken the offending party is to be reviewed by the Keshik for reparations.


Section 782
The Honor Points System

782.1.1
Introduction to Honor Points

(i.)Honor Points is a complex point system within SLP that apply to players and stars/binaries individually as well as reflect upon each other.
(ii.)Each player has their own HP ratings. (a.)Their initial rating is their Career Honor Points (or Career HP). (b.)It is then modified into their Total Honor Points (or Total HP, AKA Honor By Association) which is modified by their Star/Binary- Mates HPs and their Star/Binaries HPs.
(iii.)Each Star/Binary has their own HP ratings as well. (a.)Their initial rating is Star/Binary Honor Points (or Star/Binary HP) it has gained and lost. (b.)It is then modified into the Total Honor Points (or Total Star/Binary HP) from the current star/binary-mates in the star/binary.

782.2.1
Honor Point System For Members

(i.)(a.)The Base HP of every member is determined by their rank. (b.)Each rank has the following HP:
(1.)Cadet = 0
(2.)MechWarrior = 100
(3.)Point Commander = 200
(4.)Star Commander = 300
(5.)Nova Commander = 400
(6.)Star Captain = 500
(7.)Nova Captain = 600
(8.)Star Colonel = 700
(9.)Nova Colonel = 850
(10.)Galaxy Commander = 1000
(11.)Galaxy Colonel = 1200
(12.)saKhan = 1400
(13.)Khan = 1600
(c.)Base HP is non-accumulative. (e.g. A Nova Commander advances to a Star Captain changes their Base HP changes to 500.)

(ii.)(a.)Honor Points Modifiers (or HP Modifiers) is the personal gained honor points of an individual member of SLP. (b.)The following is a list of HP Modifiers:
(1.)Participating in a Rated Match +20
(2.)Winning a Rated Match +30
(3.)Winning a Star vs. Star match +30
(4.)Participating in a Clan Meeting +5
(5.)Achieving awards from the Keshik +10
(6.)Achieving awards from another unit +10
(7.)Wining a Star Melee +50
(8.)Fighting in some ones honor in a Grand Melee +25
(9.)Winning a Grand Melee in some ones honor +25
(10.)Winning a Grand Melee +100
(11.)Taking Command of a Star via CoE +10
(12.)Winning a ToG as the defending party +150
(c.)HP Modifiers are accumulative. (e.g. A member participates in three clan meetings, two rated matches, and wins one of these rated matches. Their HP Modifier is now 85 (5 + 5 + 5 + 20 + 20 + 30 = 85).)

(iii.)(a.)Demerits are simply negative HP Modifiers gained by committing disgraceful. (b.)The following is a list of Demerits:
(1.)Failing to show for a rated match -100
(2.)Refusing a ToG as the offending party -200
(3.)Losing a ToG as the offending party -150
(4.)Challenging the Keshik to a Trial of Refusal -150
(5.)Violating zellbrigen -150
(6.)Loosing a Trial of Refusal -350
(7.)Loosing Command of a Star via CoE -5
(c.)Demerits are accumulative. (e.g. A member has failed to show for two rated matches, and has violated Zellbrigen once should have 350 Demerits(100 + 100 + 150).)
(d.)The above is a non-exhausting list for the Keshik to use as a guide when handing out demerits to members .

(iv.)(a.)Career Honor Points (or Career HP) is found by (Base HP + HP Modifiers - Demerits = Career HP). (e.g. A member of the rank Star Commander has participated in seventeen clan meetings, participated in three rated matches, won one rated match, won one star vs. star match, won one star melee, has achieved one award from the Keshik, and failed to show in one rated match has the Career HP of 465 (300 + 265 - 100 = 465).)

(v.)(a.)Total Honor Points (or Total HP, AKA "Honor By Association") is an extremely dynamic rating found by (Career HP + All Star/Binary- Mates HP Modifiers - All Star/Binary-Mates Demerits + Star/Binary HP Modifiers- Star/Binary Demerits = Total HP). (e.g. A member has a Career HP of 545, the total of all his/her star/binary-mates HP Modifiers is 425, the total of all his/her Star/Binary-mates Demerits is 115, his/her Star/Binary HP Modifiers are 210, and his/her Star/Binary Demerits are 150 has a Total HP of 915 (545 + 425 - 115 + 210 - 150 = 915).)

782.2.2
Honor Point System For Stars/Binaries

(i.)(a.)The Star/Binary Honor Points Modifier (or Star/Binary HP Modifier) are the gained honor points of a Star/Binary when members of this Star/Binary act as a whole team. (b.)The following is a list of Star/Binary HP Modifiers:
(1.)Winning a Grand Melee +100
(2.)Winning a Star vs. Star Match +30
(3.)Participating in a Full Star Assault +30
(4.)Winning a Full Star Assault +30
(5.)Achieving awards from the Keshik +10
(6.)Winning a ToG as the defending party +150
(c.)Star/Binary HP Modifiers are accumulative. (e.g. A star/Binary has won one grand melee, won two star vs. star matches, participated in a full star assault, won a full star assault, and won an award from the Keshik has the Star/Binary HP Modifier of 230 (100 + 30 + 30 + 30 + 30 + 10 = 230).)

(ii.)(a.)The Demerits of a Star/Binary are simply negative gained by the star acting disgracefully as a whole team. (b.)The following is a list of Demerits for Stars/Binaries:
(1.)Failing to show for a rated match in a Full Star Assault -100
(2.)Refusing a ToG as the offending party -200
(3.)Losing a ToG as the offending party -150
(4.)Challenging the Keshik to a Trial of Refusal -150
(5.)Violating Zellbrigen -150
(6.)Loosing a Trial of Refusal -350
(7.)Loosing a Star vs. Star Match -5
(8.)Loosing a Full Star Assault -5
(c.)Demerits of a Star/Binary are accumulative. (e.g. A Star/Binary has failed to show for one rated match in a full star assault, lost two star vs. star matches, and lost one full star assault has 115 Demerits (100 + 5 + 5 + 5 = 115).)
(d.)The above is a non-exhausting list for the Keshik to use as a guide when handing out demerits to Stars/Binaries .

(iii.)(a.)The Star/Binary HP is found by (Star/Binary HP Modifiers - Demerits(Star/Binary) = Star/Binary HP). (e.g. a Star/Binary that has won a grand melee, won three star vs. star matches, participated in two full star assaults, won one full star assault, achieved an award from the Keshik, failed to show for one rated match in a Full Star Assault, lost two star vs. star matches, and lost one full star assault has the Star/Binary HP of 175 (290 - 115 = 175).)

(iv.)(a.)The Total Star/Binary HP is an extremely dynamic rating found by (Star/Binary HP + All Star/Binary-Mates Career HP = Total Star HP). (e.g. A Star/Binary has the Star/Binary HP of 385, the total Career HP of all Star/Binary-Mates is 2,715 which makes a Total Star/Binary HP of 3,100 (385 + 2,715 = 3,100).)


For the violation of any part of the above guidelines and rules the Keshik has the ability to take any reprehensive actions as they see fit, which includes but is not limited to: demerits given, denial of rank advancement, reduction in rank, denial to participate in a rated match, banned from the forums, removed/banned from the SLP online gaming unit, and or reported to your ISP.