24 members
DEFENDING THE EMPIRE FROM VANDUUL & OUTLAW THREATS
RECRUITMENT STATUS: OPEN
BATTLEGROUP STATUS: ACTIVE
CO: Jack Mercer
XO: James Flint
The 173rd Battle Group was authorised in 2930 as a reduced-strength rapid-response formation of the United Empire of Earth Navy.
Its original mandate was to reinforce threatened shipping routes, escort civilian and military traffic, suppress organised piracy and respond to Vanduul incursions where the immediate deployment of a larger carrier force was impractical.
Rather than maintaining a fixed order of battle, the 173rd was designed to expand or contract according to its assignment. A permanent naval core could be reinforced by combat aviation, logistics, medical, recovery and ground-support elements as operational requirements demanded.
The group’s earliest personnel were drawn from escort vessels, patrol squadrons and support commands. Initial deployments exposed weaknesses in coordination and doctrine, but also established the adaptability that would later define the formation.
In 2934, the 173rd was assigned to protect a civilian convoy travelling through a route affected by increased raider activity.
When a superior hostile force intercepted the convoy, Rear Admiral Evelyn Thorne ordered the group’s flagship to hold the attackers while the civilian transports withdrew. The flagship and much of its crew were lost, but the convoy escaped.
The action became the defining event of the 173rd’s early history.
Thorne’s decision established the principle that the protection of civilian life and the completion of the mission must take precedence over the preservation of any single ship or command.
The words Courage Through Sacrifice were later adopted as the Battle Group’s motto.
During the early 2940s, the 173rd developed from a collection of patrol and escort assets into a more integrated naval formation.
Modernisation introduced improved command procedures, dedicated aviation support and a greater emphasis on logistics, casualty response, search and rescue and damaged-vessel recovery.
The Battle Group also began conducting longer deployments against outlaw groups threatening commercial routes and isolated settlements.
Following the Vanduul attack on Vega II in 2945, the 173rd increased its readiness for frontier defence, convoy protection and the rapid reinforcement of threatened systems.
By 2955, the Battle Group required a structure capable of supporting both its current operations and future expansion.
The formation was reorganised around:
The Core Fleet is centred on the UEES Chronos, UEES Castra and UEES Rook, supported by specialist spacecraft and personnel assigned through the Battle Group’s squadrons.
Battle Group Personnel Command was established to oversee recruitment, training, assignments, qualifications, promotions and reserve personnel.
The modern 173rd is a combined-arms player organisation inspired by the traditions and structure of the UEE Navy.
Its members crew capital ships and escorts, fly combat and support spacecraft, sustain deployed forces, treat casualties, recover damaged vessels and conduct planetary operations alongside the Army Detachment.
New personnel enter through recruit training before receiving their first permanent assignment. From there, members may develop through operational experience, formal qualifications and fair promotion boards.
The 173rd does not promise instant rank or an effortless path to command.
It offers something more meaningful: a ship to serve aboard, a crew to stand beside and a place within a Battle Group being built for the future.
The 173rd is a player organisation. This history is original organisational lore written to remain compatible with the published Star Citizen setting.
The 173rd UEE Navy Battle Group is a military-inspired Star Citizen organisation built around teamwork, organised operations and meaningful service.
We operate as a Battle Group rather than a collection of independent ship owners.
Our ships require crews. Our squadrons require pilots and support personnel. Our operations require logistics, medical assistance, intelligence, engineering, recovery teams and ground forces.
Every member should have a purpose beyond simply appearing on a roster.
The 173rd exists to:
We are primarily focused on cooperative and organised gameplay.
Player-versus-player operations may be conducted when they support a legitimate mission, organised event or defensive requirement. Piracy, griefing and the deliberate harassment of other players are incompatible with the identity of the 173rd.
Ownership of an expensive spacecraft does not automatically grant command.
A capital ship is only effective when it has trained bridge personnel, engineers, gunners, flight-deck crews, security teams, medics and support staff.
The 173rd therefore places greater value on reliable people than personal hangars.
Members may serve aboard organisation-provided or member-provided vessels according to the needs of an operation. No one is required to purchase a particular ship to earn a meaningful place within the Battle Group.
Personnel progress through a structured but approachable career system.
Within the 173rd:
Promotions are not automatic rewards for time served.
Advancement considers performance, conduct, reliability, qualifications, available responsibility and the needs of the organisation. Members may be recognised as ready for promotion while awaiting a suitable vacancy.
Commissioned officers and senior enlisted personnel are expected to accept greater responsibility, not merely greater status.
Members may serve within:
Members are encouraged to develop within a chosen career field while remaining willing to support the wider Battle Group when required.
The 173rd uses ranks, billets, uniforms, qualifications and a chain of command to create organisation and immersion.
These systems exist to make operations clearer and more enjoyable. They do not exist to allow members to control, belittle or mistreat one another.
During operations, members are expected to follow the appointed mission command, maintain communications discipline and place team success above personal glory.
Outside operations, we are a community of players and friends.
The 173rd recognises that family, employment, health and personal responsibilities take priority over a game.
Participation is encouraged, but members will not be punished for reasonable absence or for placing real-life commitments first.
We ask only that personnel communicate when possible and avoid accepting responsibilities they cannot reasonably fulfil.
We welcome experienced players and those completely new to Star Citizen.
Prior military knowledge and roleplay experience are not required.
We seek people who are:
Whether you intend to command a ship, maintain its systems, man a turret, treat its casualties or fight on the ground, the 173rd has a path of service.
We intend to build an organisation capable of making full use of Star Citizen’s developing multicrew, fleet and combined-arms gameplay.
We will grow deliberately rather than inflate ranks or create empty formations.
Units will be activated when there are personnel to staff them. Leadership will be appointed when there is responsibility to carry. Qualifications will reflect demonstrated competence.
The 173rd will be measured not by the number of ships displayed on a page, but by the crews able to operate them.
Courage Through Sacrifice.
Enlist. Train. Serve.
This Charter establishes the public standards expected of all members of the 173rd UEE Navy Battle Group.
By joining or representing the 173rd, personnel agree to uphold these rules across official operations, organisation platforms, public communications and interactions with the wider Star Citizen community.
The Charter applies equally to officers, enlisted personnel, recruits, reservists and staff.
All members shall treat others with dignity and respect.
Harassment, bullying, discrimination, intimidation, personal attacks and deliberately disruptive behaviour are prohibited.
Members are expected to:
Banter and humour are welcome, but they must stop when another person makes it clear that they are uncomfortable.
Rank, position and roleplay shall never be used as an excuse to mistreat another member.
The 173rd represents a lawful UEE Navy formation.
Members shall not engage in piracy, griefing, deliberate harassment, pad ramming or unprovoked attacks while representing the organisation.
The deliberate targeting of lawful civilian players for personal profit or amusement is incompatible with membership in the 173rd.
Combat operations may include:
Members must use reasonable judgement and avoid conduct likely to damage the reputation of the organisation.
During official operations, authority rests with the appointed mission commander and designated unit leaders.
Personnel shall:
Members may question an instruction when clarification is genuinely required. Disagreements that do not require immediate action should be addressed after the operation.
Rank does not grant authority over another member’s private life, personal time or activities outside official 173rd business.
Real life comes first.
No member shall be punished, ridiculed or pressured for prioritising family, employment, education, health or personal responsibilities.
Where possible, members who cannot attend an accepted duty should notify the relevant organiser or unit leader.
Personnel holding command, instructional or administrative appointments should communicate extended absences so temporary cover can be arranged.
Leave, reserve service and inactive status exist to manage availability without unfairly penalising members.
Rank represents authority, experience and organisational trust.
It is not a measure of personal worth.
Members shall not:
Positions are assigned according to operational need and demonstrated suitability.
A member may temporarily perform a higher-responsibility billet without receiving immediate promotion. Likewise, completing a qualification does not automatically create a right to a particular rank or appointment.
Promotions and appointments shall be based on merit, readiness and organisational need.
Consideration may include:
Favouritism, purchased ships, personal friendships and popularity shall not determine promotion.
Members who are not selected should receive a clear reason and, where appropriate, guidance for future development.
Members shall only claim qualifications they have legitimately earned.
Personnel assigned to specialist duties may be required to complete appropriate training before operating without supervision.
Instructors shall apply approved standards fairly and consistently.
Training should improve practical gameplay and operational safety. It should not be made unnecessarily difficult, humiliating or inaccessible.
Members are encouraged to assist one another, share knowledge and provide constructive feedback.
Cheating, malicious software, account theft, deliberate exploitation and fraudulent conduct are prohibited.
Members shall not knowingly use exploits or unintended mechanics to gain an unfair advantage during official operations or competitive events.
Bugs encountered during normal gameplay should be reported or avoided where practical.
Members must follow the rules of any organised event, tournament or cooperating organisation in which the 173rd participates.
Victory obtained through dishonest conduct brings no credit to the Battle Group.
Members shall respect private and restricted information.
The following shall not be shared without permission:
Operational information may be restricted until an event has concluded.
Members should report suspected account compromise, impersonation or unauthorised disclosure to an administrator or command representative.
Members using the 173rd name, tag, uniform, insignia or public platforms are expected to represent the organisation responsibly.
Public disagreements should not become personal attacks or prolonged arguments.
Only authorised personnel may issue official statements on behalf of the Battle Group.
Members remain free to express personal views but should make clear when those views are their own.
The 173rd name shall not be used to threaten, deceive or pressure other players.
Members are expected to treat ships, equipment and resources entrusted to them responsibly.
Organisation operations may use ships provided by the 173rd or voluntarily supplied by members.
Personal ship ownership does not create automatic command authority over the operation in which that ship is used. The agreed mission structure remains in effect.
Deliberate destruction, theft or misuse of organisation assets may result in disciplinary action.
Accidental losses arising from normal gameplay will be treated reasonably.
Minor concerns should normally be resolved through guidance, informal correction or additional training.
Repeated or serious breaches may result in:
Severe harassment, cheating, griefing, malicious conduct or threats to member safety may result in immediate removal.
Disciplinary action should be proportionate, documented and based on available evidence.
Members may request a review of formal disciplinary decisions through the appropriate command or administrative channel.
Appeals must be made respectfully and should include any relevant evidence or clarification.
A person directly involved in the original dispute should not be the sole reviewer of an appeal where another suitable reviewer is available.
The purpose of review is fairness and accuracy, not the avoidance of responsibility.
Every member of the 173rd contributes to its reputation and effectiveness.
We expect discipline during operations, fairness in leadership, integrity in conduct and respect throughout the community.
We protect the crew.
We complete the mission.
We do not leave our people behind.
Courage Through Sacrifice.
