Leadership Division: This division holds The Galactic Order’s highest ranked members of authority, who govern over other Divisions with the responsibility of establishing and organizing all aspects of military action and protocol.
Members of Leadership Division are most commonly seen leading individual battalions (as Captains & 1st Officers) within a fleet, with each fleet being led by an Admiral that reside outside of the Battalion structure. At the heart of every Fleet, exists a Leadership Council which governs over all decisions and delegations, with each Captain acting as a representative of their Battalion, similar to government officials representing a district, and each Admiral representing the Fleet itself.
| 1st Officer | |
| Captain | |
| Vice Admiral | |
| Admiral |
Elite Sub-Division: This sub-division is a branch of the Leadership Division, known for units at the top of their field; individuals whom mostly operate as they see fit without the complications and responsibilities of command. They answer only to the high-ranking members of the Leadership Division unless otherwise stated in their unit card description.
| Commissar | |
| Praetorian |
Each Fleet within The Galactic Order military houses a Leadership Council. On this council, different ranked members are afforded different levels of authority:
Often held at least once per month, each Fleet holds a Leadership Council meeting to address any and all recent comments, questions, concerns and suggestions. Although attendance is completely optional among members of Leadership, it is highly encouraged as these meetings provide each unit a voice in all matters that are discussed, regardless of rank/role.
These meetings can be organized by a Commissar or any member of High Leadership, although the primary responsibility tends to fall on a fleet Admiral or Vice Admiral. 1st Officers may call meetings with the approval of their Captain.
As with other Events, those who attend these meetings will gain +1 Event and may qualify for mission vouchers based on their level of participation.
Example: Taking notes to share with other members whom could not attend: +1 Manage Data
With the existence of multiple Fleets, sitting above each Leadership Council, resides the Senate. This is where all members of Admiralty gather to discuss matters of the entire Galactic Order military. As with each Leadership Council, different ranked members of the Senate are afforded different levels of authority:
2.1 This title grants members of Leadership the authority to accept applications on the RSI Org site.
2.2 Units with this title work in recruit acquisition, managing application processing into The Galactic Order military. It is a challenging but honorable title to obtain, but also easily lost as any Warning will automatically remove the title, requiring re-application.
2.3 The title of Acquisitor can only be gained through a written application (following chain of command) to a member of Admiralty who may approve or deny the application. When approved, the title will appear on the Acquisitor's Unit Card and the role will be added on Discord.
2.4 Approval of this application does not require any formal announcement.
"You are being recruited. Do not resist" - 1st Officer Jigsauce
Similar to Promotions, Recruit application acceptance follows specific steps that are required to ensure stability of The Galactic Order’s structure and chain of command. Below are listed instructions for this process...
Important Note: Applications may ONLY be accepted after the individual has joined the Discord.
- Identify Applicant in Discord.
- Applicant must have both Discord Roles: Unlocked & Guest
- Server Nickname must match Star Citizen handle name.
- Investigate Applicant on RSI Site for suspicious affiliations.
- Post application image/screenshot in | recruit-messages Discord channel, including message.
- Accept Application!
- Announce that the Application has been Accepted by tagging the Novitiate in | general and congratulating them on Rank Novitiate:
- Add Novitiate role (in Discord), and remove Unlocked & Guest.
- Visit Full Roster page and Select the Button, followed by Register Unit button to fill out information...
- Star Citizen Name (handle name)
- Discord Profile (lowercase name)
- Recruiter's Name(optional)
- Start Date
- When all info is filled out, press Submit to apply changes.
Example 1: “Application Accepted! Congratulations @Chocula on Rank Novitiate!”
Example 2: Application Accepted! Congratulations {NAME} on Rank Novitiate! Look to any Lieutenants, Commanders, or @Progenitor in-game or in a voice chat as they are your guides to The Galactic Order, getting started or answering any org specific questions moving forward! Welcome aboard! 😎 👍
Battalion Captains, when first promoted, often get the option to choose their Battalion’s Type from the available options:
- Harbinger
- Venator
- Economy
- Expedition
- Medevac
In some instances, a unit’s promotion to Captain may be conditional based on which Battalion Type is needed for the Fleet. This is ultimately decided by Fleet Command and Leadership Council.
With Fleet Command’s approval, Captains may change their Battalion Type but this is uncommon and rarely encouraged as it can significantly reduce a Battalion's Mark progression.
Vehicle Selection is decided by the Captain, and refers to the Battalion’s chosen Primary Ship, Support Ships, protective Fighters, and all other Vehicle specifics.
Vehicle Selection will play a significant role when Star Citizen persistence is further implemented, as there will be limits on the number of ships each Battalion will be able to operate, manage, and store. This will be even further enforced once base building is implemented and The Galactic Order has established a permanent settlement with planned Districts for each Battalion. For these reasons, it is highly encouraged that each Battalion Leadership limits their vehicle selection to those they can effectively crew concurrently .
These are the personal vessels of Fleet Command, with Flag ships belonging to Fleet Admirals and Vice Ships belonging to Vice Admirals. Due to the crew size and resources required, use of these ships are often reserved for significant operations, with requisitioned units from battalions within the Fleet to act as the vessel's crew.
Each battalion is run by a Captain and is typically centered around a primary ship. These vehicles are intended to house a majority of the Battalion's crew, requiring they be larger than 70 meters in length and fall under sub-capital or capital ship category.
Most battalions utilize troops (units) from multiple divisions to function, requiring 5 or more crew members minimum to operate. The Starting Mark I standard battalion size is anywhere between 5 to 10 units, including leadership. As additional Marks are added to the Battalion, limits on unit capacity are modified.
For additional ships within a battalion, the primary ship must meet the minimum safety requirements such as docking or a hanger to provide safe crew transfers to accommodate shift changes and crew demands.
Currently, Battalions are limited to a selection of 10 Support Vehicles, however it is highly encouraged that each Battalion Leadership limits their vehicle selection to those they can effectively crew concurrently.
This refers to the chosen members / crew of each Battalion. Ultimately, Captains hold the final word for all Transfer requests made to Leave or Join their Battalion. With new Battalions, Transfer requests are common from members of other existing Battalions. However, most transfers will come from the Academy, often based on familiarity and gameplay preferences.
Each Captain holds nearly full authority over their personal Battalion, within the limitations of Galactic Order protocol and commands set forth by the overseeing Fleet Admiral(s).
The Rank of Captain is awarded in 1 of 2 situations. Either a Captain is promoted to assume command of an existing Battalion or they are appointed to form their own. Both are considered a great honor and hold unique challenges.
Note: Captain limit per Battalion: 1
The promotion to Captain with the option to form one’s own battalion comes with the challenge of deciding what battalion type that captain will adopt as it will often be a choice they can make for themselves. Only in the situation where Admiralty holds specific needs for a fleet is there an exception to this. Captains in a New Battalion position will also have their choice of ship(s) and crew. Because promotion to Captain in this context requires that they must achieve the rank of Commander in at least 2 different Divisions, it is typically recommended that they form their battalion based on a past-served division (not required).
Captain promotion for an existing battalion (either from within or outside the battalion itself) occurs when the former Captain has been removed from their role by either demotion, resignation, reassignment, or execution.
When a Battalion loses its Captain, Fleet Command will assume temporary authority & oversight while existing 1st Officers (if present) maintain their responsibilities. This throws the battalion into a Trial period, during which time all potential candidates for Captain are taken into consideration from throughout the Fleet.
Ideally, a 1st Officer will be chosen from within the Battalion for promotion to Captain, however lack of experience or necessary prerequisites can heavily obstruct this from happening, particularly in unexpected circumstances.
If no Captain can be found within a 2 month period, the Battalion will enter retirement, giving battalion members 1 week to Transfer out or face automatic transfer back to the Academy, which may result in auto-demotions for any units Rank 2 or higher.
After achieving the role of Captain, the journey of progression through the ranks doesn’t just stop before Admiral. There are sub-Ranks that may be achieved within Captain, designated: “Marks”. These display on a Captain’s title as Stars…
- Units: 40 (max)
- +1 Titan Trooper
- +1 Commander (1st Officer)
- +1 Commander (Trooper)
- +1 Commander (Engineer)
- +1 Commander (Medical)
- Units: 55 (max)
- +1 Titan Trooper
- +1 Commander (1st Officer)
- +1 Commander (Trooper)
- +1 Commander (Engineer)
- +1 Commander (Medical)
- Units: 75 (max)
- +1 Titan Trooper
- +1 Commander (1st Officer)
- +1 Commander (Trooper)
- +1 Commander (Engineer)
- +1 Commander (Medical)
With each Mark achieved, a Captain gains additional Authority, Battalion Funding, and greater Unit Capacity. This will allow for their Battalion to not just grow in numbers but also scope, as additional units can also mean additional support ships or fighters.
Note 1: Captains inherit Marks from their battalion.
Battalions gain Marks through 3 Progression Prerequisites: Missions, Events, & Patrols.
Battalion progression works similar to individual unit rank prerequisites, found on the Rank Information page. Missions, Events & Patrols logged for each unit will also apply to that individual's Battalion, adding to the exisiting total.
Example: If a Battalion’s current Patrols sit at 150, and 2 Troopers of that Battalion participate in a patrol, the Battalion's total will reach 152 once those patrols are added to the Roster.
Missions tally similar to Events & Patrols, but hold the same restriction to Division roles, as only related Battalion Type missions can be counted. Example: Economy Battalion can only count Engineer missions towards Battalion Progression, just as Medevac Battalion can only count Medical missions.
Harbinger Missions: Turret, Ground Assault, Escort, Inquiry, Pilot/Co-Pilot, and Supply.
Venator Missions: Ground Assault, Pilot/Co-Pilot, Cargo, Supply, Manage Data, and Explore.
Economy Missions: Pilot/Co-Pilot, Mining, Salvage, Cargo, Transit, Supply, and Manage Data.
Expedition Missions: Inquiry, Supply, Manage Data, Research, Explore, and Agronomy.
Medevac Missions: Ground Assault, Escort, Transit, Supply, and Search & Rescue.
Battalions are named with a designation number (F-##) to indicate the assigned Fleet/Admiral followed by the founding Captain’s Last name, the first Letter of their battalion Type (I for Intercept, X for Expedition, etc…) and a number starting at ‘01’. This number is significant for fleets with multiple Battalions of the same type.
-
Example:
- F-01 Remington I-01
- Fleet #1
- Captain Remington
- Harbinger battalion #1
Note: In the event that a Battalion’s Captain is changed, typically the Battalion's name will remain the same. However, any Captain is well within their right to modify the name at any time, after informing Admiralty.
Campaign Ribbons are honors attached to a Battalion to recognize particular achievements or events of service. These are similar to the Ribbon awards & Titles an individual unit may achieve, but differ in that they remain with the Battalion itself as a legacy to its accomplishments, and the achievements of those who served during that time. These are awarded to Battalions by the Admiralty within a single Fleet Command, or by Supremacy and the Senate.
More details will be Available when unlocked with 9th Roadmap Goal
Promotions act as the primary form of progression within The Galactic Order and help maintain stability within the organization’s hierarchy. To maintain structure and order within the chain of command, it is important to incorporate an organized system related to all changes in Ranks & Roles. Here is a basic Guide to follow for promotions…
To start, when a unit qualifies for promotion, it is not a guarantee that they will be promoted. There are 3 factors that can influence this change in Rank/Role:
- Role Availability: Some roles have a limited number of available positions within a single Battalion. If the limit has been reached, no promotion can be offered.
- Unit History: Past warnings, official reprimands, outstanding loans or demotions can hinder or completely prevent a unit from being promoted, despite prerequisite qualifications. More details for Demotion provided in Rank/Role Demotions section.
- Discretion: Even with availability and clean unit history, a particular unit may not receive a promotion offer if their superior officer(s) don’t wish to promote them. This can be for a multitude of reasons. Perhaps the role is not needed for the Battalion’s structure. Perhaps the unit is not ready for the added responsibility. Perhaps a more qualified unit is expected to take the promotion instead. Although these reasons can sound harsh, it is important to keep in mind that elements within the org are ever-changing, and nothing is set in stone. There are always options!
Important Note: To maintain order & stability, Commanders should not promote Units outside of their Battalion. This preserves the Chain of Command and avoids Conflict or Confusion.
When a promotion offer has been given and accepted, here are the steps that must be followed:
- Promote Unit on Full Roster page.
- Promote Unit in Discord (selecting Role, Rank & Division)
- Announce the promotion in the | enlisted Discord Channel
- Add the Command role on RSI Member page
- Add the Leadership role on RSI Member page (Leadership Division ONLY)
- Introduce the new Commander in the relevant channels and give a brief introduction of their added responsibilities and authority.
Demotions are handled very different than promotions. First it is important to note that there are 3 common reasons for demotion:
- Insubordination: Any time a unit receives an Official Reprimand, they are put at risk for demotion. This is case-by-case and often depends on the reason for their Official Reprimand, along with history and overall response. The rank they are being demoted from is also a strong factor, as higher ranks have greater levels of expectation which also means higher risk for demotion from Warnings & Reprimands.
- Command Inactivity: As mentioned in the Command Activity section, there are certain requirements and responsibilities that are expected of Command specifically. Unfortunately, when those requirements are not met, the officer is demoted from their position until they are ready.
- Personal Choice: Some members, often officers, will approach leadership for the purpose of being demoted. Although this can occasionally be due to a reluctance for the responsibilities their rank holds, it’s often due to real life-related challenges that prevent them from fulfilling the role’s requirements. This is viewed more as an Honorable Discharge of sorts. Of all the demotions, this is the only one that does not incorporate a Demotion Timer.
Note: It is very important that any unit, facing demotion, is informed as to why they are being demoted. This may be done through private messages in Discord or in a voice chat.
Important Note: To maintain order & stability, Command should not demote Units outside of their Battalion. This preserves the Chain of Command and avoids Conflict or Confusion.
When a unit is demoted, either due to inactivity or insubordination, they are temporarily placed on hold from any further Promotions. The default time for a Demotion is 1 Month, however these can be altered at Leadership’s discretion. During this time, the Unit is unable to change their Rank, Role or Division.
Steps for Demotion are nearly identical to those of a Promotion…
- Demote Unit on Full Roster page.
- Demote Unit in Discord (selecting Role, Rank & Division)
- Announcement of the Demotion is not necessary, but encouraged for the Command Discord channel so other Officers and Leadership are made aware.
- Remove the Command role on RSI Member page
- Remove the Leadership role on RSI Member page (Leadership Division ONLY)
For Commanders, inactivity will most often mean demotion to a lower rank with fewer requirements. However, continued inactivity for regular members can have a different outcome. At Leadership’s discretion, members can be changed to “Inactive” Status on the Roster.
This status is often given when a member has left the Discord or held Rank 0: Novitiate for 12 months.
Inactive status will set the member’s Rank to 0, Battalion to “None” and change their Role to “Inactive”. This is not only to keep members organized on the roster but also to provide additional units for Battalions with limited space. Role limits can also be an important factor in performing this action.
Inactive status can be removed by a member of Leadership at any time but Rank, Role & Battalion will need to be re-established based on prerequisites and role availability.
See Return Protocol section for more Details...
This section gives details in the unfortunate scenario where a Unit must be removed from service to The Galactic Order military. This process may be initiated by any member of Command.
Currently there are 2 types of Discharge from the Org: Honorable Discharge & Dishonorable Discharge (aka: Banned).
This process occurs when a Member of The Galactic Order has voluntarily left the Official RSI Org. When this occurs, their Rank is set to 0, their Role is changed to "Discharged", and they are removed from the Roster with their record preserved in the database and sealed. This applies only to units with a logged service record, as those without will face full deletion from the database, removing the name from Recruit numbers. Only a member of High Leadership (Rank 4+) may restore a sealed record should they choose to return.
See Return Protocol section for more Details...
- Confirm member has left RSI Site.
- Visit Full Roster page on The Galactic Order Website.
- Select Edit Unit button.
- Select Discharge button.
- Enter Unit Battalion and Unit Name, followed by the Remove button.
This process occurs when a Member is being forcibly removed from The Galactic Order and requires specific parameters to carry out...
- Ban member from The Galactic Order Discord server.
- Ban member from RSI Site.
- Visit Full Roster page on The Galactic Order Website.
- Select Edit Unit button.
- Select Discharge button.
- Enter Unit Battalion and Unit Name, select the Checkbox, followed by the Remove button.
Any Commander within The Galactic Order may petition for the Military Discharge of a unit Rank 3 or lower. This petition must be submitted to a member of Leadership, in writing, and must detail the reasons for filing the action.
Commanders may only file a Petition for Military Discharge against a unit with: minimum 1 Official Reprimand on record, or a motion of Reasonable Cause, which requires evidence or documentation to support all claims and arguments to the Petition. Depending on the Petitioned Unit’s Rank, a strong claim might be required in the case of a reasonable cause Petition for Military Discharge of a high authority Unit.
Note: Chain of command applies, so Commanders must submit their petition to a Superior (1st Officer or Captain) of their same Battalion. However, Commanders may Petition Units outside their Battalion.
Any member of Leadership Division may choose to Discharge a unit of their same Battalion, without a petition. This refers mostly to 1st Officers and Captains. However, a Fleet Admiral may Discharge a unit from another Battalion, but only from within their own Fleet.
Warning: Unit Ban will place the Member on a permanent black list, preventing any future applications back into The Galactic Order. Perform this action ONLY when a member is kicked from the Discord & Official RSI Org.
With our specific structure, we recognize that we are not an organization built for everyone. However, the Galactic Order prides itself with welcoming any interested members from all walks of life. This even includes members whom have previously left the org and later decided to return.
Return Protocol applies for members within 2 distinct scenarios:
When a member has been marked as “Inactive”, their record is temporarily locked and they are removed from visible ranks, while still remaining on the Full Roster. Inactive status will set the member’s Rank to 0, Battalion to “None” and change their Role to “Inactive”. When this member returns, any unit of Leadership Division can reinstate the member’s status back to Active, returning them to Academy Battalion where they have a strong potential to reoccupy a previously held Rank outside of Leadership. From there, they may continue regular progression.
When a member has left the org by choice, they are Honorably Discharged which seals their record and completely removes them from the Full Roster. When an honorably Discharged member returns, they must re-submit an Application on the RSI Site and follow the necessary steps as if joining the org for the first time, creating an entirely new Unit Record.
Honorable Discharge records can be unsealed by a member of High Leadership (Rank 4+), with approval from Admiralty. This will restore the individual’s records from before they were Discharged, with exception to Start Date, Promotion Date, Exam scores, and Unit ID (all reset).
Re-enlisted Unit returns to Academy Battalion, starting with a Role previously held (Rank 2 or lower), offered by Academy Leadership. This will also include a Demotion Timer, similar to what is stated within the Rank/Role Demotion section.
Disclaimer: These conditions are absolutely not intended as punishment for returning members. However, the Galactic Order must maintain a fair and just system to value loyalty, establish trust and reward reliability.