Let me start by saying Welcome to The Galactic Order! No doubt you might be feeling slightly overwhelmed so here is a simple introduction to help get you started.
When a new member joins The Galactic Order, following application approval, they are assigned Rank 0: Novitiate. This role has limited armor and zero authority, but gains access to nearly all Division gameplay options within the org.
There are currently 4 Main Divisions which act as different branches of our military:
Combat Division is where you’ll find our Troopers. This Division focuses primarily on operating Turrets, conducting Ground Assaults in FPS combat, enforcing laws, and performing investigations.
Engineer Division is where you’ll find our Pilots and Engineers. This Division focuses primarily on piloting/co-piloting ships, handling cargo, conducting mining and salvage operations, and providing maintenance & repair services.
Medical Division is where you’ll find our Medics. This Division provides combat support along with search & rescue services, and body recovery.
Leadership Division is where you’ll find high ranked members such as 1st Officers, Captains & Admirals. This Division focuses on the organizing and delegating of The Galactic Order’s overall Resources, Government and Military.
To begin their journey, Novitiates report for duty during a Patrol or Event under a Progenitor, Lieutenant (Rank 2) or Commander (Rank 3+), to learn the basics of the org, gather experience, and discover which Division they wish to enter. When on-duty, their completed in-game missions and overall progress is recorded by the person they reported to. When the necessary prerequisites have been achieved, Novitiates will be offered a promotion to Rank 1 in the Division of their choosing, excluding Leadership.
Progress can be tracked, for each member, on the Battalions page. Simply search for names through the Unit Tracker or look through the listed Battalions.
Battalions are how The Galactic Order military is organized. A single Fleet (led by an Admiral) is comprised of multiple Battalions, each led by a single Captain.
Novitiates will always begin in the Academy. Following a promotion to Rank 1, units may then apply for transfer to a Battalion through a formal request to that Battalion's 1st Officer or Captain.
As units climb the Ranks within their chosen Division, they’ll notice an increase in responsibility and authority.
Important Note: Below Command (Rank 3), there are No Obligations forced upon any members within the org. Promotions are also completely optional and only really recommended to those interested in dedicating further time and energy to The Galactic Order.
Disclaimer: Rank Promotions are offered and not automatic or mandatory. They are optional, based on what each individual member wishes to achieve within The Galactic Order. These offers can always be respectfully declined if the new role entails responsibilities that the individual is not interested in fulfilling.
Information about each rank/role can be found on the Rank Information page.
1.1 Communication is likely the most important means for all activity within The Galactic Order, as it maintains structure and keeps things organized in even the most chaotic of settings.
1.2 Regardless of experience, we all know that things can get hectic and exciting at any moment while gaming, especially in a larger group. Through this excitement, it can be easy for the voices to get louder, providing unnecessary information and reducing overall cohesion in communication. In an effort to increase our likelihood of success in future operations & events, The Galactic Order has issued Comms protocol that all units must adhere to.
1.3 There are three condition levels that will vary depending on what the situation calls for. These conditions will often be called out by the highest-in-command within the current voice channel as an occasional reminder for when appropriate. However, other officers present may also suggest a change in the Comms condition level.
Communications Condition 3 (Comms 3)
Communications Condition 2 (Comms 2)
Communications Condition 1 (Comms 1)
2.1 It is important for all members to remain mindful while in voice chats, speaking over others only when necessary. We encourage everyone to be courteous, patient, and respectful with one-another, especially in high populated channels.
If a unit calls out “Comms!”, cease discussion to allow that person to momentarily take the floor.
Voice Chat: Squad - 1
Squad 1 Comms 3
3.1 SRS is an additional form of communication for larger TGO operations. Available to Command, SRS provides outside comms for multiple channels or within largely populated channels.
3.1a When Active, Commanders post "SRS Active" in the | srs-status.
- Original protocol author: Praetorian Patrick "Paternal" Sole
1.1 For new members, here are a few steps to optimize your RP (Roleplay) experience. Currently, we require only 3 emotes to be used, of which we recommend placement on the Number Pad of your keyboard (if available).
Step 1: Select Options menu in Star Citizen
Step 3: Select Advanced Controls Customizations (bottom Left)
Step 4: Scroll to page bottom & Select Social - Emotes
2.1 Reporting for Duty initiates the Roleplay setting and will allow progress to be recorded by the Progenitor, Lieutenant or Commander each Unit reports to.
2.1.1 Units may report for duty in person or through in-game comms.
- Use/Hold Attention emote until acknowledged by Lieutenant or Command.
- Use Salute emote when first addressed by, or addressing, Lieutenant or Command.
- Use/Hold Attention emote after Salute.
- State Rank, Name and "Reporting for Duty".
- Hold Attention emote until Uniform/Equipment inspection is complete or further orders are given.
- Use/Hold At Ease emote when Lieutenant or Command says "at ease".
- Units may resume duties only after Lieutenant or Command says "dismissed" or "as you were".
- Use Salute emote again when dismissed.
- Command will typically Salute back but are not required to, unless reporting to another Commander.
- A Commander is any unit Rank 3 or higher.
2.2 Initiating a Roleplay setting counts as "1 Patrol". Patrols end when a unit either signs off or "Requests Relief". Requesting a relief is when a unit requests to be off-duty, but still intends to be in-game. This follows the same protocol steps used to Report for Duty. Roleplay continues until the Patrol has ended.
Commanders: Command is considered on Patrol (On-Duty) any time they Report to a Superior, a Commander of the same rank, or any time a unit reports for duty to them.
Lieutenants: Lieutenants are considered on Patrol (On-Duty) any time they Report to a Superior, a Lieutenant of the same Division or any time a unit reports for duty to them.
3.1 Command is responsible for tracking progress with any completed Events, Patrols & Missions of a unit that reports for Duty. Commanders then submit all reports directly to The Galactic Order Roster.
3.2 Lieutenants may also track progress, but are limited to Patrols & Missions of units that report for Duty only within their Same Division & Novitiates. These reports are sent to a Superior in Command for review, rather than the Roster directly.
- Combat Division units report to Lieutenant-Trooper or Trooper-Commander
- Engineer Division units report to Lieutenant-Engineer or Engineer-Commander
- Medical Division units report to Lieutenant-Corpsman or Medical-Commander
3.3 If there is no acting division commander, they may report to another Commander that is present.
3.4 Commanders within Leadership are responsible for Registering units and recording # of Recruits.
4.1 Below is a list of all Mission Types that apply to the Progression within each Division. Some mission types apply to multiple Divisions but may apply differently with a slightly altered description.
Disclaimer (1): Missions are earned & distributed typically 1 per contract / operation, with exception to those with either multiple stages or operations that extend for longer periods of time. Missions are assigned based on the primary responsibilities and tasks each unit performed throughout.
Disclaimer (2): For operations that don't require transportation or preparation to complete, only 1 Mission can be awarded every 15 Minutes for the sake of balance. Special operations, with extensive planning, may extend this number with Leadership pre-approval.
-
Squad PvP
- Squad FPS Kills (PvP): Confirmed PvP FPS/ Turret (Manned & Remote) Kills while in a Squad.
- Squad Pilot Kills (PvP): Confirmed PvP Pilot Kills while in a Squad.
-
Combat Division
- Turret: Any operation of a manned or remote turret.
- Ground Assault: Any 1st person mission that involves discharging a weapon.
- Escort: Accompanying or escorting a superior officer as a protective detail for 1 hour.
- Inquiry: Investigation related missions requiring criminal analytics & enforcement of Law & Order. This includes enforcement of Galactic Order Protocol & Conduct.
- Supply (Combat): Providing Uniforms to meet protocol, as well as: Ammo, Weapons and Equipment related to Combat. (Max +1 per Hour)
-
Engineer Division
- Pilot / Co-Pilot: Operating on a ship terminal as co-pilot, operating a remote turret or flying a ship personally.
- Mining: Operating a mining laser to any degree (in a vehicle or on foot).
- Salvage & Repair: The recovery of abandoned resources, materials & items or the restoration of equipment, vehicles & structures.
- Cargo: Any transportation of goods, resources or objects from one location to another (regardless of profit).
- Transit: Any transportation & safeguarding of people, targets or individuals in need of aid.
- Supply (Engineer): Providing Uniforms to meet protocol, resources / supplies, funds, tools and Equipment related to Engineering. (Max +1 per Hour)
- Manage Data: Currently, this refers to Removing, or Aiding in the Removal of, a Crime Stat, handling Data Pads, or performing any Hacking-related acts.
-
Medical Division
- Ground Assault: Any 1st person mission that involves discharging a weapon.
- Escort: Accompanying or escorting a superior officer as a protective detail for 1 hour.
- Transit: Any transportation & safeguarding of people, targets or individuals in need of aid.
- Supply (Medical): Providing Uniforms to meet protocol, quality of life assistance, sustenance, tools and Equipment related to Medical. (Max +1 per Hour)
- Search & Rescue: Unit Recovery from destroyed or disabled vehicles, providing healthcare support on a mission, stabilizing an injury outside the AO, or body recovery. Generally 1 per mission where medical aid has been provided..
Mission Vouchers: These count as free missions that may be applied to any available mission type, excluding Supply (due to its application for all Divisions) and Squad Kills (FPS or Pilot). Units often receive mission vouchers for completing special tasks or attending unique events and operations. Not awarded during Patrols.
Typically, these are distributed randomly when achieved. However, units may request they be applied to specific mission types before added to the Roster.
2.1 This title grants authority to log progress for other units Rank 2 or lower and send Patrol reports to Command, similar to lieutenants. However, unlike a lieutenant, these individuals are not limited to same-Division units.
2.2 Progenitors hold the responsibility for onboarding new Novitiates into The Galactic Order, seeing them through to Rank 1 or higher and ensuring they are properly trained to Galactic Order standards. They act as a mentor, educating units from a place of experience and knowledge, much like a Drill Instructor or Training Officer. There are high expectations for Progenitors regarding knowledge and practice of protocols, rules, and laws. 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 Progenitor can only be gained through a written application (following chain of command) and Leadership approval. Applicant is expected to state their reasoning for requesting the title and how they intend to use it. Similar to a commendation, this requires a vote by Leadership Council before it can be assigned to the applicant. When approved, the title will appear on the Progenitor's Unit Card and the role will be added on Discord.
1.1 With any roleplay game/setting, each person holds the responsibility for playing a character on some level. Of course, this can simply be a reflection of the player themselves but enjoyment can also be found in developing something new. A character unlike one-self that can change and develop over time is always a rewarding experience and brings a lot of unique dynamic elements of gameplay into effect. This can take any form such as a simple bullet point list of traits, a short paragraph of likes & dislikes or a written backstory…or maybe all 3 if you feel ambitious. The only limitations for any of these are based on the established lore of the world or, in this case, the universe of Star Citizen and The Galactic Order.
1.2 It is worth noting that creation of a personal character lore is not mandatory by any means and can be made or edited at any time, at the creator’s discretion. This experience is greatly encouraged though, as it can add a lot of fun and immersion to the overall experience within the org. It is also important to note that there are no expectations on performance or portrayal of one’s character. Expert-level acting is appreciated but absolutely not required or expected.
A Division refers to the field of study or military branch within the Galactic Order that each individual unit may fall under. Currently there are 5 main Divisions & 2 Sub-Divisions:
- Combat Division: This division acts as the main military branch, with a focus on security, protection and maintaining peace through the enforcement of laws, rules and protocol within The Galactic Order’s established territory. Nicknamed “the Trooper division”, these units are most often found operating as foot-soldiers in ground (or zero-G) combat or manning turret-based weaponry. They are also the most heavily armored and tactically re-enforced units within The Galactic Order military, loyal, battle-hardened and ready to defend order at a moment’s notice.
- Engineer Division: This division holds a 3-split focus between battle, logistics, and support. For battle, you have pilots & co-pilots that operate vehicles on the ground, in zero-gravity or in atmospheric flight. For logistics, you have engineers that gather and manage resources to support The Galactic Order military, often obtained through mining, salvaging, or cargo trade. Finally, for support, you have engineers that maintain ships & structures (providing repair, re-arm, refuel, transportation, cargo hauling, or overall resource management services).
- Medical Division: This division has a primary focus on the safety and survival of all Galactic Order members. However, unlike other organization medical branches, these units often engage in combat alongside Troopers of the Combat Division, holding no oaths against committing harm, unless said harm is directed against other members of The Galactic Order military. Some medical units may also act as pilots, similar to Engineer Division, for the sake of providing transportation or medical aid.
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 |
| Ensign Troopers | |
| Lieutenant Troopers | |
| Shock Troopers | |
| Trooper Commanders |
Special Operations Sub-Division: This sub-division, also referred to as "special ops" or "spec-ops", is a branch of the Combat Division with specialized unit roles that incorporate various elements from other divisions (such as Engineer and Medical) for unique missions and tasks of a more covert nature. These units focus mostly on PvP, intelligence gathering, and espionage requiring a great deal of skill, patience and knowledge.
| Outriders | |
| ARC Trooper | |
| Agents |
| Ensign Operator | |
| Lieutenant Engineer | |
| Systems Specialist | |
| Engineering Commander |
| Ensign Medic | |
| Lieutenant Corpsman | |
| Medical Commander |
There are several Battalion Types, each organized to perform specific tasks and hold focused responsibilities based on the chosen primary Ship. Battalions have their own unique blend of units from each division, assigned to accommodate the necessary roles required for optimal efficiency. Listed below are the battalion types currently implemented within The Galactic Order...
Though not an actual Battalion type, the Academy provides basic training for all new members, exisiting outside any assigned Fleet, and managed by members of the Leadership Division. The Academy holds a strong focus on research, development, education, unit training and rank progression. When Novitiates begin their journey here, they'll intern with other Battalions on Patrols & Events until they achieve Rank 1 where they'll choose a Division. Once promoted, Rank 1 units will often request transfer to an actual Battalion that fits their desired gameplay.
These battalions are trained and battle-hardened in all facets of warfare. In times of conflict, Harbinger battalions are sent with the singular purpose of eliminating dissension by any means necessary. First and foremost, they are designed to lead the Order in aggressive combat, utilizing the organization's most destructive assets. This requires all units to be highly trained and highly motivated, setting a unique standard among contemporary militaries. Everything from direct naval action, orbital bombardments, to precision ground assaults, makes the Harbinger battalions near peer to other special operations.
Harbinger battalions are also the military’s greatest protectors, defending TGO regions, cities, outposts, space stations and even other battalions. In times of peace, they are used to patrol established territory and disseminate order, dissolving antipathy with their zealous attitude before it can begin.
Every battalion type has soldiers to address the ever-looming threat of combat. However, Harbinger battalions are built to embark on entire campaigns, as instruments of war in the name of The Galactic Order, with an unwavering duty to eliminate threats through combat.
Primary Ships (common): Destroyers, Carriers, Gun Ships, Corvettes, & Frigates.
Support Ships (common): Repair, Re-Arm, Refuel, & Medical.
This battalion type has a focus on Looting, Treasure Hunting & Trade Agreements, incorporating elements of Intercept, Economy & Expedition Battalion types. Their primary objective/mission statement involves taking itemized order requests, hunting down rare items, performing acts of piracy outside Galactic Order territory (as Privateers), and exploring new regions for rare & unique resources, items & artifacts.
Primary Ships (common): Carriers, Freight, Expedition & Science.
Support Ships (common): Repair, Re-Arm, Refuel, Mining, Salvage & Medical.
This battalion has an expansive focus, featuring the largest array of career positions and fields out of any other battalion type. As the name suggests, the overall purpose of an Economy Battalion is to re-enforce The Galactic Order’s economy by generating funds, resources and supporting progress through all levels of the org’s infrastructure, by any and all means.
Primary Ships (common): Heavy Salvage, Mining, Transport/Touring, Freight, Repair, Refuel, & Construction.
Support Ships (common): Combat related.
This battalion type has a very expansive, yet specific, focus involving the gathering, cataloging and sharing of information & intelligence. As the name suggests, Expedition Battalions focus on new discoveries and expanding the gathered knowledge of The Galactic Order, to further technological advancements and forward the progression of all Divisions/Fields.
Primary Ships (common): Expedition, Touring, & Science.
Support Ships (common): Priority Transport, Repair, Refuel, Refine, & Medical.
The Medevac Battalion of The Galactic Order serves as the front line of emergency medical response, with a primary responsibility to answer medical rescue beacons for The Order across all combat zones and operational environments. Whether responding to battlefield distress signals or deep-space casualty calls, the battalion is built to move fast, stabilize, and extract.
Specializing in triage, combat support, trauma intervention, and revitalization, this battalion is the lifeline of The Galactic Order’s fighting force. As the central hub of all medical activity, it operates with speed, precision, and purpose—ensuring the wounded receive immediate care and safe evacuation from the most dangerous scenarios.
Powered by advanced medical science and hard-earned experience, the Medevac Battalion employs constantly evolving practices grounded in extensive research. Its teams—elite medics, combat specialists, and extraction pilots—are trained to perform under fire, in vacuum, and across hostile planetary surfaces.
The Medevac Battalion doesn’t just support missions—they save them. Every life they bring back is a reminder of their unmatched dedication and unwavering resolve.
Primary Ships (common): Any Vehicle with Tier 2 & Tier 1 Medical Bay + Ship Hangar.
Support Ships (common): Combat capable vehicles.
1.1 All units qualify for transfer from the Academy once they have achieved Rank 1.
2.1 Any unit may request transfer from a Battalion back to Academy.
3.1 All units may also request transfer from one Battalion to another.
4.1 All units may also request transfer from one Division to another.
4.2 Transfers to a new Division require each unit to begin at Rank 1 (regardless of prerequisites).
1.1 As stated in our Rules & Laws, each member must wear their uniform during Patrols & Events in | Enlisted, or other RolePlay voice channels in Discord. However, uniforms are excused in | Public & | Off-Duty voice channels. Unit specific attire is an important part of the Galactic Order’s image, acting not only as a projection of power but also further developing the chain of command, giving visible differences between ranks.
1.2 Each Division’s equipment loadout is designed to match the challenges and tasks that particular role may encounter while on patrol. Lower ranks, with greater levels of risk, will typically have more visible armor and protection while higher ranks have less as they are further burdened by the challenges of command. The only exception to this is observed with the Combat Division which will see an increase in Armor due to an increase in risk.
Note (1): As mentioned on our Exams & Benefits page, Uniforms are provided to Novitiates and Rank 1+ Members. However, these must be requested no sooner than 1 Hour in Advance, from when the Uniform is needed. Requests must be made, in writing, to a Superior, following chain of command.
Note (2): Uniform details for each Rank/Role can be found on the Rank Information page.
Uniform Warning: Every time a unit must be reminded to wear the proper uniform, they might be issued an Warning.
Disclaimer (1): This protocol need only be followed when affiliating with other Org Members in-game.
Disclaimer (2): For special events, or unique patrols, a member of high leadership (Rank 4+) may excuse or substitute uniform protocol after member's have reported in.
1.1 Units outside of the Combat Division are restricted from using the following weapons/items until they’ve passed the Tactical Exam, found on the Exams & Benefits page of the website...
- Missile Launchers
- Railguns
Note: The use of explosive ordinances is strictly forbidden on ships unless authorized by Command.
2.1 In addition to these restrictions, some units have Tool requirements and limitations based on their Division and Role:
- Ensign Operator required to Equip.
- Lieutenant Engineer required to Equip.
- All Units allowed to Carry or Equip.
- Medical Division required to Equip.
- Leadership Division allowed to Equip
- ARC Troopers allowed to Equip
- Novitiates allowed to Equip
- All Units allowed to Carry (not Equip).
Note: As mentioned on our Exams & Benefits page, Weapons, Ammo & Tools are provided to Rank 1+ Members. However, these must be requested no sooner than 1 Hour in Advance, from when the Items are needed. Requests must be made, in writing, to a Superior, following chain of command.
Tool Warning: Every time a unit must be reminded to equip the proper Tool(s), they might be issued an Warning.
Disclaimer: This protocol need only be followed when affiliating with other Org Members in-game.
1.1 This is the only instance when regulation equipment, such as Armor & Tools, are not enforced as there will be times when items may need to be worn or replaced for the sake of performing the task of item retrieval. However, after looting is complete, all regulations are immediately set back in place.
Note: All looting takes place only after a mission has been completed, and not before or during.
1.1 Unit Conduct dictates the behavior that is expected in every Roleplay Setting, after Reporting for Duty.
1.2 Each unit is expected to operate within the functions and responsibilities of their Division Role while also following the chain of command, in all settings. Although they can be instructed to perform duties outside their role, such action requires instruction from Command.
1.3 In preservation of The Galactic Orders code of conduct & morality, there are designated parameters for addressing combat encounters, along with specific practices & knowledge to bolster survival rates of our troops, while increasing efficiency in the elimination of designated hostiles.
2.1 Battle Conduct in relation to combat has 3 primary conditions of focus, granting permission for aggressive action…
- Attack when attacked
- Attack when threatened
- Red is Dead / Weapons Free
All Galactic Order units may freely defend themselves against attackers, firing upon those whom have shot first, or shown strong intent to do so.
With orders from a Superior, Galactic Order units may initiate combat, outside of an armistice zone, in hostile environments or in any scenario where Galactic Order safety is compromised.
All red targets, excluding org members & designated allies, may be freely targeted unless ordered otherwise by a superior.
2.2 Org members are forbidden from recklessly harming, disabling, or incapacitating one-another unless otherwise ordered to by a superior with probable cause. This strongly applies to any harmful actions performed on a superior, which may result in severe punishment.
- Permanent Jump Point: Attack when Attacked
- Orbital Marker (OM): Attack when Attacked
- Armistice Zone: Attack when Attacked
- Settlement: Attack when Attacked
- Station: Attack when Attacked
- Outpost: Attack when Attacked
- Permanent Jump Point: Attack when Attacked
- Orbital Markers (OM): Weapons Free
- Settlement: Weapons Free
- Stations: Attack when Attacked
- Outpost: Weapons Free
- Permanent Jump Point: Attack when Attacked
- Orbital Markers (OM): Weapons Free
- Settlement: Weapons Free
- Stations: Attack when Attacked
- Outpost: Weapons Free
3.1 The following are special circumstances for Weapons Free...
- High Value Location: Weapons Free
- Pirating / Privateering
- Quantum Snaring
- Claimed Territory: Weapons Free
- Leadership Established
- TGO Claimed Territory
- Blockade Defense / Offense Points
- 100 km (minimum) from non-hostile
- Hacking Location: Weapons Free
- Comms Arrays
- Security Posts
- Trespassing: Weapons Free
- Illegal Operations
- Crime Stat (CS) Activity (AKA Running Red)
4.1 Welcome to The Galactic Order PSA for Elevator Conduct. If you are reading this then that means our ancient enemy has reared its ugly head to claim more of our inocent troopers...the dreaded Elevator!!!
4.1a As silly as it sounds, elevators have claimed the lives of more Galactic Order Members than the Vanduul and UEE Combined! In this document, we will go over simple & effective techniques to help mitigate the loss of life from these metal boxes from hell.
4.2 The anatomy of these cold death machines can be quite simple in their appearance. Elevators often consist of at least one set of doors (minimum), and no less than one exterior elevator call button. Once called and opened, there is typically one simple panel on the inside to operate the contraption and request a location.
4.3a Before entering, units MUST call out their intended positions, to remove any confusion and avoid additional risks. These are as follows:
- Buttons (Operates elevator)
- Back Left
- Back Right
- Front Right
- Center
Note: Center (position) is ill-advised, and only for the most battle-hardened and steel-nerved amongst us.
4.3 To mitigate loss of life, The Galactic Order has standartized assigned designations within each elevator, including methods for approach, entering, and exiting.
4.3a When entering the cursed box, units are highly encouraged to reduce their walking speed (mouse wheel) or enter crouched to avoid colliding with one-another and unintentionally sending someone into the void between worlds.
4.4 To Exit the murderous prison, units are encouraged to do so one at a time in a calm and orderly manner. If all steps are followed to the letter, YOU TO MAY SURVIVE THIS DEADLY OPPONENT!
This message is brought to you by the Commissariat of Leadership division.
- Original protocol author: Commissar Cactite
Casualty: Any injured or Incapacitated Unit in the Area of Operations.
AO - Area of Operations: A predetermined area established for missions or specific Operations. These often measure within the boundaries of signature detection range from primary objectives.
On-Site: Reference to location being inside AO.
Off-Site: Reference to location being outside AO.
SOP - Standard Operating Procedures: Base doctrine for carrying out a complex task.
RTB - Return to Base: Typically to Repair, Re-Supply or Treat injuries.
EVAC - Evacuation: Any vehicle used to remove/evacuate units from an AO.
Weapons Free: Fire at desired Targets.
Fire for Effect: Fire at designated Target.
Conduct Warning: Every time a unit must be reminded to follow proper Battle Conduct, they might be issued an Warning.
Disclaimer: This protocol need only be followed when affiliating with other Org Members in-game.
"Only YOU can protect the innocent troopers!" - Admiral Holland
1.1 Ship Conduct dictates the behavior that is expected in every Roleplay Setting with a Battalion Primary Ship, Support ship or Fighter. These apply to all units, even before reporting for duty.
Important Note: Responsibilities associated with ALL Boarding/Departing will typically fall on the Ship's Bridge, unless a Security or Control Room is present. In that instance, the Security and/or Control Room will merely consult the Bridge, but handle the details in protocol.
2.1 Statistical research into unit reaction times has shown that a battalion's crew, capable of bringing their vessels to full combat readiness, see a significantly higher survival rate, even when faced with considerable oppositional forces.
2.2 Leading from this, the Science Division Defense laboratory compiled a fleet wide implementation of ship protocols governing the behaviour of Battalion Units operating in combat zones to increase overall reaction times.
2.3 As Battalion Units are already heavily burdened with decision making during a ship combat engagment, the following protocals seek to reduce the work load required by any single member of the crew by aiming to maintain a minimum personnel level in critical areas of the ship.
Condition Green
All units may move about freely. All ships Default to this condition until stated otherwise.
- Setting: This condition is used only in confirmed safe locations (docked/landed/idling).
- Weapons: Limited to pistols only. Restrictions lifted for Combat & Leadership Division.
- Board / Depart (Personnel): Permission not required.
- Board / Depart (Vehicles): Permission required.
Condition Yellow
Level 1 essential units to Command-assigned Stations, ready to respond to possible combat engagement. Other units must remain near their stations.
- Setting: This condition is used outside confirmed safe locations.
- Weapons: Limited to pistols only. Restrictions lifted for Combat & Leadership Division.
- Board / Depart (Personnel): Permission required.
- Board / Depart (Vehicles): Permission required.
Condition Orange
Level 2 essential units to Command-assigned Stations, ready to respond to possible combat engagement. Other units must remain near their stations.
- Setting: This condition is used in unconfirmed or potentially unsafe locations.
- Weapons: Limited to pistols only. Restrictions lifted for assault/defense units, Combat & Leadership Division..
- Board / Depart (Personnel): Permission required.
- Board / Depart (Vehicles): Permission required.
Condition Red
All Units to Command-assigned Stations FULL battle preparedness: Ready for combat engagement and Equipped for possible boarding action or ship abandonment.
Important Note: Command holds responsibility for declaring the current Ship Condition.
3.1 For situations with ship-to-ship docking, permission must be requested through comms, prior to making a docking request. For ship-to-ship landing, such as on a Landing Pad or in a Hangar Bay, permission must be requested through comms before landing. This applies to Ground Vehicle boarding/storing as well.
Note: Discord Voice Channels may currently act as a substitute for in-game comms.
- Permission to Dock, Land or Board any Vehicle onto a Ship must be requested by stating: Rank, Name and "Permission to Dock".
- Permission to Undock, Take-off or Depart any Vehicle from a Ship must be requested by saying: Rank, Name and "Permission to Disembark".
Note: Permission to Dock automatically gives permission to Board, unless stated otherwise. If permission to Dock is granted but permission to Board is denied, Docking vehicle crew must await confirmation to leave the vehicle and board.
Note: Permission to Disembark can only be granted after disembarking vehicle crew has been fully loaded and accounted for.
4.1 The protocol is specific to vehicles that incorporate Carrier Gameplay, a unique classification defined by the docking & departing of multiple vehicles from a single source within a Squad formation. Due to the complex nature of these operations, distinct protocol is needed to establish guidelines and consistent practices to ensure overall structure is maintained.
4.2 Carrier-assigned Pilots are often expected to manage all exteriors for Board/Depart actions during carrier operations. For this reason, it is recommended that the open & close (toggle) keybind be established. In instances when this option is dangerous or less beneficial for Carrier Operations, Gate Operators may be assigned.
4.4 After mission is established, prior to initiating final Approach / Quantum Jump, CC will call “Ship Condition Red”, and await squad readiness confirmation from all units before final jump.
4.4a All Squad units verify readiness by stating Squad ID, followed by “standing by”. Example: “Red 2, standing by”.
4.4b Squad readiness is highly encouraged before initiating Deployment to limit the duration a Carrier remains open (further preventing infiltration).
4.5 After initiating final Approach / Quantum jump, CC will initiate hangar opening and give the command: Squad Name, followed by “clear to disembark” when vehicles are clear to depart. Example: “Red Squad, clear to disembark”
4.5a For Flight vehicle deployment, 20 Kilometer distance (minimum) is recommended.
4.5b For Ground vehicle deployment, 2 Kilometer distance (minimum) is recommended.
4.5c All vehicles must verify departure confirmation by stating Squad ID, followed by "is clear” once they’ve deployed. Example: "Red 2 is Clear”.
Note: Some encounters may not give the option for distant deployment, in which case the Squad is expected to launch at a moment’s notice.
4.6 Once squad has deployed, members will form up on CP Leader who will give operation commands until mission complete.
4.7 After mission is complete, CC will initiate hangar opening and give the command: Squad Name, followed by “docking approved" when vehicles are clear to board. Example: “Red Squad, docking approved”.
4.8 Once a squad member has completed docking, they will verify by stating Squad ID, followed by “docked with engines off" or “on and off". Example: Red 2 docked with engines off".
4.9 Depending on the carrier, CC may need to implement a Board/Depart (Vehicle) order to avoid unintended collisions and ensure greater efficiency.
- Original protocol author: Ensign Operator Chocula
5.1 High-value mining operations are crucial for the Galactic Order’s funding and security. These operations involve higher risks and more complex procedures. To minimize risks such as piracy, solo hauling, rival organizations, and loss of materials or crew, the following tactics and conduct are highly recommended. This protocol requires squad formation for mining operations to incorporate specialized roles, and it is also advisable for personal use.
5.2 The Galactic Order classifies mining operations into two categories: Low Yield and High Yield.
Note: Deposit equity (referencing the total estimated value of a rock cluster) can be spread across multiple rocks within a cluster.
5.3 Low yield mining operations require a designated Convoy Commander. Position assignments are established with squad IDs, along with safety measure responsibilities and the cargo value sub-category.
5.3a No minimum required roles.
5.3b Deposits are non-essential.
5.3c Refinery Transport is not limited to the closest viable location, but proper preparation is advised.
5.4 By Galactic Order standards, the minimum safe staffing for high yield mining operations includes the following:
- 1 Resource Pilot
- 2 Resource Operators
- 1 CP Operator
- Optional: 1 Scout Pilot
6.1 High value cargo operations are an important aspect of the Galactic Order’s operational funding and security. As such, the proper tactics and conduct are advised during these operations to maximize profits while minimizing risks, such as pirating, solo hauling, UEE, or rival organizations. When managing Cargo outside of a specialized Economy Battalion, this protocol requires Squad formation for Cargo Operations to incorporate specialized roles.
6.2 Currently, the Galactic Order places cargo operations under 1 of 2 Categories: Low Yield & High Yield. Low Yield refers to any Cargo/Freight Ship with a cargo capacity of 1,000 SCU or lower, and High Yield refers to anything above 1,000 SCU.
6.3 Low Yield cargo operations require a designated Convoy Command (CVC). From there, position assignments are established with Squad IDs, along with safety measure responsibilities, and the Cargo Value sub-category; placing the operation under one of two options: Low Value or High Value.
6.3a With Low Value, there are no minimum required roles as the cargo is considered non-essential in the context of a Low Yield cargo operation. For safety, cargo hauling is often limited (in travel) to a single planetary system, traveling through different stations, outposts, settlements or cities surrounding a solitary planet and its moons. Travel to other planetary systems is not restricted but instead discouraged without precautionary measures.
6.3b With High Value, there are 3 required unique roles for minimum safe staffing: 1 Cargo Pilot, 1 Escort Pilot, & 1 Recon Pilot. Cargo hauling is also not limited (in travel) to a single planetary system, with precautionary measures in place.
- Original protocol author: Praetorian WhatIdo
7.1 There are specific stations that may be present on a ship, each with distinct protocols with regards to access and authority, some of which may be off-limits to particular Units based on Rank & Division.
Note: Off-limit stations require Permission to enter.
Note: Only the Ship Stations mentioned below are restrictions.
These ship stations/rooms have established access limitations based on Role, Rank or Division. All protocols are enforced in restricted areas and access, not freely given, must be requested and approved by the highest ranking Officer at that station (or nearby).
These ship stations/rooms have lower established access limitations than Restricted Areas based on Role, Rank or Division. All protocols are enforced in moderated areas.
These ship stations/rooms have lower restrictions to protocol and do not limit access unless otherwise stated. Equipment (Armor/Uniform) protocols are not enforced in unrestricted areas unless Ship Condition changes from Green to Yellow, Orange or Red.
Conduct Warning: Every time a unit must be reminded to follow proper Ship Conduct, they might be issued an Warning.
Disclaimer: This protocol need only be followed when affiliating with other Org Members in-game.
1.1 Squads are considered temporary team assignments, often reaching outside battalion structures, and formed for specific operations. These involve unique roles and positions that are assigned for optimal squad performance to ensure the highest chance for operational success. When an operation has concluded, the squad is dissolved but may be referenced or repeated (in structure) with later operations of identical or similar nature.
2.1 Squads can be formed by any Lieutenant or Commander, with primary responsibility falling on the highest ranked unit present. Squads can be formed for simple Patrols with designated categories of focus (such as bunker infiltrations or ship bounty hunting), although they are best utilized for Events and large Operations.
3.1 The task of establishing roles within a squad will typically fall on the highest-ranking unit present when a squad is formed, although this can be delegated to any unit Rank 2 or higher.
This Squad Role is the main operational leader, responsible for all macro level organization and decision making for squad operations. Operation Commanders also appoint Squad Roles for delegating additional responsablities, while offering oversight to ensure those leaders are executing their assigned duties.
This Squad Role is expected to avoid participate in direct action, to maintain focus on all moving parts of an operation.
Note: If other units of Command (equal rank or higher) take part in a Squad Operation, Operation Commanders may ask them to take on delegating roles.
This Squad Role is a secondary operational leader for Convoy Operations, responsible for some macro level organization and decision making in their assigned convoy. Convoy Commanders share an onus to appoint other Convoy Squad Roles for delegating additional responsablities, while offering oversight to ensure those roles are executing their assigned duties. Convoy commander also assists the Operation Commander by making a detailed travel and safety plan for the movement of high priority cargo, whilst following Cargo Protocol.
This Squad Role is expected to participate in minimal direct action, to maintain focus on all related moving parts of an operation.
Note: If other units of Command (equal rank or higher) take part in a Squad Operation, Convoy Commanders may ask them to take on delegating roles.
This Squad Role is a secondary operational leader for Carrier Operations, responsible for some macro level organization and decision making in their assigned Carrier. Deck Officers share an onus to appoint other Carrier Squad Roles for delegating additional responsablities, while offering oversight to ensure those roles are executing their assigned duties. Deck Officers assists the Operation Commander by appointing Vehicle assignments & postitions, Ship Conditions, and handling requests for Docking & Disembarking.
This Squad Role is expected to participate in minimal direct action, to maintain focus on all related moving parts of an operation.
Note: If other units of Command (equal rank or higher) take part in a Squad Operation, Deck Officers may ask them to take on delegating roles.
This Squad Role is responsible for leading a ground assault team. Squad Leaders appoint other (limited) Squad Roles based on tactics and formations needed.
This Squad Role is expected to participate in major direct action with their troops, and may even split their squad into smaller fireteams.
This Squad Role is responsible for the overall Safety and integrity of the Squad. Security Officers perform patrols on their assigned ships or stations, performing inspections of: Squad members, Cargo, and Squad Vehicles to ensure safety, secuirty, and compliance to protocol.
This Squad Role is expected to participate in moderate direct action, to maintain focus on their responsablities.
This Squad Role is the first off any vehicle, and first into any entryway. First On acts as the initial eyes and ears for their ground assault team, taking point to gather immediate intelligence and relaying critical information back to the Squad in a timely & effective manner.
This Squad Role is the last off any vehicle, and last into any room or entryway. Last Off ensures that all vehicles are buttoned / closed upon disembarking, hightening security & safety while also covering the ground assault team's potential immediate exit. They remain mindful of the Squad's rear, and keep the squad in a cohesive, moving element.
This Squad Role is responsible for conducting patrols and securing an assigned location from possible threats. Patrolman can be found on an assigned Vehicle, assigned to protective detail of a priority target, or with a ground assault team. They remain mindful of their surroundings, relaying critical information to the Squad or providing status updates during an operation.
This Squad Role is often assigned in addition to another Squad Role, giving the added responsibility to relay vital information between different teams or squads during Squad Operations. Comms Officers often communicate with each-other, when more than one is assigned for large operations. They are expected to communicate effectively within protocol and with plain speak so as not to overburden communication channels.
- Ship Cockpit/Bridge
- Control Room
This Squad Role is often assigned in addition to another Squad Role, giving the added responsibility to effectively maintain designated entrances/exits of an assigned station. Gate Operators often communicate with Operation Command directly, serving a vital role in operation efficiency & safety. They are expected to communicate effectively within protocol and with plain speak so as not to overburden communication channels.
"They push button!" - WhatIdo
- Ship Cockpit/Bridge
- Control Room
- Engineer Station
This Squad Role is responsible for Piloting and leading teams in flight operations. CP Leaders appoint other (limited) Squad Roles based on tactics and formations needed.
This Squad Role is expected to participate in major direct action with their pilots, coordinating any ancillary flight maneuvers for mission objectives.
This Squad Role is responsible for Combat Piloting in operations. CP Operators can be found in an assigned Vehicle, acting as protective detail of a priority target, or performing ancillary flight maneuvers for mission objectives.
This Squad Role is responsible for Piloting and intelligence gathering in operations. Scout Pilots can be found typically in an assigned stealth Vehicle. They act as the initial eyes and ears for the Squad, jumping to mission objectives and taking point to gather immediate intelligence and relaying critical information back to Squad Command in a timely & effective manner.
This Squad Role is responsible for Piloting, providing safe & efficient transit during operations. Drop Pilots can be found typically in a designated Drop Ship, assigned to protective detail of a priority target, or transporting a ground assault team. They will often remain in communication channels with ground assault teams while maintaining communication with Comms Officers or Operation Command.
This Squad Role is responsible for monitoring the loading & unloading of cargo during Convoy Operations. Load Masters ensure that cargo is managed safely and efficiently, whilst following Cargo Protocol.
This Squad Role is responsible for Piloting during Convoy Operations. Convoy Pilots can be found in an assigned Vehicle designed for gathering, transporting, or processing resources, typically related to Mining or Salvaging.
This Squad Role is responsible for resource management during Convoy Operations. Convoy Operators can be found at ship stations in an assigned Vehicle designed for gathering, transporting, or processing resources, typically related to Mining or Salvaging.
4.1 Squad identifications require assignment of a color or name, followed by number positions for each station or role. This greatly improves squad efficiency with callouts and designations.
- Red Squad: CP Leader's fighter is assigned as Red 1.
- Alpha Squad: Last Off is assigned as Alpha 4.
- Wampa Squad: Hammerhead Front Port Turret is assigned Wampa 2.
- Bantha Squad: Hammerhead Front Starboard Turret is assigned Wampa 3.
1.1 This section details Medical Conduct, Practices, and added Authority for Medical Division units as they provide support for Galactic Order missions & operations.
- Blurred Vision & muffled Audio
- 14% of Max Health (lost)
- Ocular Inflammation
- Concussion
- Increased Visual & Auditory impairment
- 25% of Max Health (lost)
- Ocular Inflammation
- Concussion
- Severe Visual & Auditory impairment
- 35% of Max Health (lost)
- Ocular Inflammation
- Concussion
- Impaired Mobility
- Average 60 BPM (Beats Per Minute)
- Minor Stamina reduction
- Audible Wheezing
- Average 84 BPM
- 18% of Max Health (lost)
- Respiratory Damage
- Moderate Stamina reduction
- Severe Wheezing
- Average 107 BPM
- 32% of Max Health (lost)
- Respiratory hemorrhage
- Impaired Mobility
- Major Stamina reduction
- Severe Wheezing
- Average 130 BPM
- 43% of Max Health (lost)
- Respiratory hemorrhage
- Impaired Mobility
- Aiming difficulty
- Weak Melee
- Sometimes asymptomatic
- 10% of Max Health (lost)
- Muscle Fatigue
- Major Aiming difficulty
- Very Weak Melee
- 18% of Max Health (lost)
- Muscle Fatigue
- Unable to hold Weapons or Tools
- Unable to Pilot Vehicles
- 25% of Max Health (lost)
- Muscle Fatigue
- Impaired Mobility
- Partial Paralysis
- Slow Movement
- 10% of Max Health (lost)
- Muscle Fatigue
- Noriceable Limp
- 18% of Max Health (lost)
- Muscle Fatigue
- Impaired Mobility
- Unable to Walk/Stand (crawl)
- 25% of Max Health (lost)
- Muscle Fatigue
- Impaired Mobility
- Partial Paralysis
To avoid Overdose, drugs should ONLY be used to EVAC a CE Red, excluding Hemozal.
Overdose may cause collapse, similar to incapacitation. In this state, damage is gradually sustained while BDL levels remain between 100% - 200%.
At 0 health, patient becomes incapacitated, requiring Hemozal to revive them & Resurgera to lower BDL. Patients will require constant care to maintain their health until Overdose has been overcome.
BDL reduced by:
- Waiting over time.
- Administering Resurgera
- Medical Bed (any Tier)
- Rapidly reduce BDL
- Rapidly replenish Hunger & Thirst (applies degenerative de-buff)
This Tab of the Medical Care screen shows the patient Status, indicating the presense of Injuries (if any) and recommended options for Treatment.
- Injury Select option(s)
- Injury Severity
- Recommended Action
- Prescribed Drugs for Symptoms (& syptoms relieved)
This Tab of the Medical Care screen manages Treatment for injuries, initiated automatically after a course of treatment has been selected.
- Available Options
- Location of Injury
- Checkbox Interaction
- Button Interaction "Perform Treatements (X number of times)
This Tab of the Medical Care screen manages administration of medications to aleviate symptoms, used primarily for injuries of a greater Tier than the Medical Bed is able to properly Treat.
This screen manages the patient's Regeneration location, allowing user to set current location or default location (Home Planet/City).
Regenerating, or logging on, when the primary regeneration point is no longer in the patient's server will reset the location to default.
This screen manages all saved regeneration imprints.
- Only applicable on Vehicle Medical Beds (Currently).
- Only accessible by the Vehicle Owner.
- Hospitals (Planet-side)
- Clinics (space Stations)
- 890 Jump
- Carrack
- Polaris
- Terrapin Medic
- Cutlass Red
- Pisces C8R
- Rover Medevac
- Project Director
- Assisted with in-game testing over multiple sessions
- Assisted with writing and editing of medical document
- Assisted with in-game testing in a single session
- Participated in initial discussion of medical material to be covered in the guide
2.1 Lieutenant Corpsman & Medical Commanders are expected to establish these reports during Events and Squad Operations to track all injuries for units that have reported for duty. This chart is used to monitor Combat Effectiveness and assign treatment priority at medical facilities.
2.2 Medics will issue each Unit a Combat Effective (CE) rating of Green, Yellow, or Red based on their condition and Medic's judgement. This rating may also be issued to a Squad, as a whole, following similar guidelines.
CE Green: Little to no injuries. Fully combat effective.
CE Yellow: Tier 2 injury or multiple Tier 3; Drugs not required. Partially combat effective.
CE Red: Tier 1 injury or multiple Tier 2; Drugs required. Not combat effective, EVAC essential.
2.3 To avoid a dangerous BDL, drugs should ONLY be used to EVAC a CE (Red) patient, excluding Hemozal. Visit the ParaMed Adv. Settings section below for more details.
2.4 If a Medical Division unit designates CE Red for a unit or squad, they must immediately clear comms to relay this info to the Squad Leader.
Note: These reports can be made using any preferred format (Example image below).
4.1 This protocol covers the 6-Line Medical EVAC service provided by The Galactic Order military. Requests can be made by any TGO ranked member (Rank 0+). To get started, follow the steps below within each of the 3 phases provided.
Post a 6-line in the | medical-evac Discord channel (details below). If written correctly, this will alert all members of the Medical Division.
- Incapacitated - EVAC is completed when Patient is revived.
- Injured (Tier 1-3) - EVAC is completed when Injury is cured.
- Extraction needed - EVAC is completed when Patient is extracted.
This protocol is meant for emergency and critical use only. Examples of such situations are when a TGO member is in life or limb threatening danger away from other org or party members, or the situation has become so extreme that it requires more support to complete rescue.
This protocol is NOT meant for use when TGO or party members are close by and easily able to render aid.
After a 6-line has been posted, EVAC responders will confirm by posting “Responding to request” within the forum post. There is no limit to the number of responders per request, as some may require multiple units.
Note (1): View Line 4: Security Risk Level for further details on EVAC completion.
Note (2): Additional EVAC Requests can be made, after one is completed, based on the patient's condition.
Note (3): As the rescue is underway, open communication within the forum post (or inside a Voice Channel) is strongly recommended.
Once the Medical EVAC request has been completed, the patient is expected to remove the Active (Tag) and add the Complete (Tag), and stating the names of the responders involved.
To ensure patient safety while also maintaining order with Medical EVAC requests, Mission Vouchers are awarded based on time from the initial 6-line post.
- EVAC (Complete): +2 Mission Vouchers - awarded to patient.
- EVAC (Complete): +1 Medical EVAC (Service) - awarded to responders.
- EVAC (Complete) within 45 Minutes: +5 Mission Vouchers - awarded to responders.
- EVAC (Complete) after 45 Minutes: +3 Mission Vouchers - awarded to responders.
Note: For details on Mission Vouchers, visit the Mission Types sub-section of the Patrol Conduct section on this page.
Those who partially assist, or attempt to assist, with a Medical EVAC can receive +2 Mission Vouchers if their efforts are noted (by the patient) when closing out the Request, stating “EVAC Assist:” followed by their names.
Note: Medical EVAC Assist do not gain +1 Medical EVAC (Service)
Assistance must be provided before the EVAC Request is completed in order to apply.
(Relevant to S&R)
Casualty: Any injured or Incapacitated Unit in the Area of Operations.
Patient: Any Casualty being evaluated and Treated by Medical Division Unit(s).
6-Line: Information structure provided when requesting for EVAC.
On-Site: Reference to location being inside AO.
Off-Site: Reference to location being outside AO.
AO - Area of Operations: A predetermined area established for missions or specific Operations. These often measure within the boundaries of signature detection range from primary objectives.
SOP - Standard Operating Procedures: Base doctrine for carrying out a complex task.
S&R - Search & Rescue: Unit Recovery from destroyed or disabled vehicles, providing healthcare support on missions, Stabilizing an injury outside of AO, or recovering a body.
CCP - Casualty Collection Point: A pre-determined and easily identifiable location, within the AO, for responding Medical Division Units to treat and EVAC casualties.
(Relevant to S&R)
FS - Fighter Support: Light or Heavy fighter ships tasked with Patrolling On-Site or Off-Site during missions & operations.
RTB - Return to Base: Typically to Repair, Re-Supply or Treat injuries.
EVAC - Evacuation: Any vehicle used to remove/evacuate units from an AO.
Conduct Warning: Every time a unit must be reminded to follow proper Medical Conduct, they might be issued an Warning.
1.1 ALL Galactic Order Ranks & Roles can make Lab Proposals & submitting Lab Reports for Research & Development (R&D).
Step 1: Concept Phase (Optional)
2.1 R&D studies are posted in the | science-bureau channel on Discord.
2.1a The initial Draft must follow a specific format:
2.1b This will auto-generate a thread for the R&D project. Further notes can be posted within that thread, along with all related comments, questions, suggestions, and concerns.
2.1c Completion of this phase awards +1 Manage Data to Author.
Note: The purpose of this Step is to enter the Research Phase where additional assistance and org resources can be openly obtained and better organized.
Step 2: Research Phase (Optional)
2.2 Patrols, Events, and/or unique operations may be organized for the purpose of gathering Intelligence for the Lab Proposal.
2.3 R&D project are posted in the | science-bureau channel on Discord as a Lab Report. If attached to a previously established Lab Proposal, simply link the initial post and follow the steps below.
2.3a The Submit post must follow a specific format:
1.1 All Science Division members may engage in policy drafting, a unique practice that allows units to essentially submit changes or additions to Protocol directly to Leadership Council for final review and possible implementation.
Similar to other division-related privileges, this process follows specific steps for proper consideration and application…
1.2 Although only Science Divison units may draft policy proposals, units from any division (regardless of rank) may make suggestions for changes in protocol within the | ask-or-suggest channel on Discord.
1.2a Science Division units may also adopt Lab Proposals into a Policy Draft, simply by following the steps listed below, as a reply to the Lab Proposal with "Phase: Submit".
1.3 For the purposes of this protocol, "Collaborators” are defined as members of the Science Division who make significant contributions to a Policy Draft and are listed as such by the Main author of said draft.
2.1 Science Division Unit(s) submit a written Protocol proposition in the | science-bureau channel on Discord. This will auto-generate a thread where additional details may be provided for the Policy Draft, following any format. Further posts can be made within that thread as progress notes to incorporate any and all related discussion around the proposed protocol to catalog comments, questions, suggestions, and concerns.
2.1a The initial Draft must follow a specific format:
2.1b Completion of this phase awards +1 Manage Data .
2.2 Patrols, Events, and/or unique operations may be organized for the purpose of testing the proposed protocol. However, Events must be organized officially by any Division Officer (Rank 3+) who must be noted within the progress notes (Discord post thread), and the proposed Protocol must be mentioned within the event’s description.
2.3 Once the proposed protocol has been properly tested, it may then be submitted as an initial complete draft to Leadership, similar to Concept Phase. This must be done in writing (drafted as it would be intended to appear on the Protocol page), as a reply to the initial post and must tag @Leadership Division to be valid.
2.3a The Submit post must follow a specific format:
2.3b This will auto-generate a Threat where the final draft can be posted for review.
2.4 After the submit phase, Leadership Council will move forward with a vote on the protocol’s final implementation, following standard Deliberation. If the vote passes, the protocol is implemented but can be modified from it's most recent submitted draft. However, if the vote fails, the protocol is then dismissed with an added thread statement from Leadership Council (if applicable). Moving forward, a new policy draft can be added as a reply to the most recent related Submit Phase as a new Concept Phase for further testing or resubmission of a proposed protocol.
Note: When available, Expedition Battalion Captains may issue Leadership Council meetings specifically for the expressed purpose of reviewing Policy Drafts.
1.1 Warnings are temporarily issued for any repeated, or willful, violations of Protocol, laws or rules.
1.1a While active on a unit's record, Warnings may inhibit promotions and remove authority based on the warning's condition for being issued.
1.1b With 3 Warnings active on-record, an Official Reprimand will automatically apply to that individual’s service record on the Roster.
1.1c Warnings may be issued by Lieutenants & Commanders that deem a violation to be purposeful or negligent by nature.
1.1d Additional Details for Warnings are given under each related Protocol section.
Disclaimer 1: Exam scores can be reset if deemed appropriate or necessary in relation to the subject matter of the issued Warning.
Disclaimer 2: Overall, Lieutenants & Commanders try to avoid issuing warnings, typically initiating multiple conversations before taking things further. However, at times, warnings have proven to be necessary for constructing the importance of our laws, rules and protocols. More often than not, Warnings are issued for poor reactions to constructive criticism or after numerous attempts have been made to communicate to an individual without any signs of improvement. Higher Ranked units also face a greater risk for Warnings given the expectations of their standing.
1.2 Warnings may be removed from record at leadership's discretion. This often occurs only after improvements have been observed or a duration of time has passed. However, Reprimands remain on permanent record.
2.1 An act of insubordination is a defiance towards authority and a refusal to obey orders.
2.1a For insubordination, units can be issued a private message and Reprimand. As stated in our Rules & Laws, members will often receive 1 Reprimand before facing demotion or harsher punishments.
2.1b For Novitiates, "harsh punishment" will most often mean termination. The Galactic Order will not tolerate disobedience and will not dedicate time & resources towards the progression of an individual whom has shown no interest in remaining among our ranks or improving the organization.
2.2 Reprimands are typically issued after Warnings have failed to produce the intended result. These remain on permanent record.
2.2a An official Reprimand can produce any number of outcomes, often highly dependent on how they are received. In some cases, the Reprimand will remain as just that, a Reprimand to avoid repeating past mistakes. In other cases, Reprimands have served as a cautionary tale, resulting in a demotion or removal from the organization completely.
2.2b Similar to Warnings, Reprimands may be issued by Lieutenants & Commander that deem a violation to be purposeful or negligent by nature.
2.2c There is currently no established limit to the number of Reprimands an individual can hold on record.
3.1 In extremely rare cases, units may face sudden dishonorable discharge if Leadership Council deems warnings and official Reprimands an inadequate solution to correct behavior. This act is executed in situations where significant damage or impact can be observed over a short period of time, and only with the final authorization of a Vice Admiral or Admiral.
Visit our Command Info page for more details.
