IE11 is no longer supported
We do not support Internet Explorer 11 and below. Please use a different web browser.
Roberts Space Industries ®

Pyro Freelancer Corps / PFCS

  • Syndicate
  • Regular
  • Freelancing
  • Piracy

Bodies for hire across the ‘verse, no questions asked.

Join our Discord!

IG: @pyro_freelancer_corps

Facebook: Pyro Freelancer Corps


Pyro Freelancer Corps has been providing the highest quality of service to those seeking their own form of justice since Stanton evolved into a privately-owned star system. Our strict code of honor assures a job well done, and as advertised. And don’t worry about the law. We’ve got it covered.

04-12-2953 – Star Citizen Alpha 3.18.1 is released. Progress beings again as players are able to join the live gaming environment. Plans to build FPS combat curriculum continues with the Avenger Spartans.

03-10-2953 – Star Citizen Alpha 3.18 is live, and infrastructural progress is halted due to tremendous bugs on release.

01-18-2953 – Star Citizen Alpha 3.17.5 is released, and anticipation for Persistent Entity Streaming grows. More events are run with Avenger Spartans, building partnership and rapport. Baracuda876 is promoted to Commander.

11-17-2952 – Star Citizen Alpha 3.17.4 is released. Pyro Freelancer Corps narrows its market to gun running and rare armor trading, and excels. Plans arise to form dedicated ground unit with Avenger Spartans in tandem. Requisitions Division is formed.

10-06-2952 – Star Citizen Alpha 3.17.3 is released. Pyro Freelancer Corps begins experimenting with player-driven economies and markets.

07-29-2952 – Star Citizen Alpha 3.17.2 is released, and with it, Siege of Orison, and increased player capacity on servers.

04-29-2952 – Star Citizen 3.17.1 goes LIVE

02-03-2952 – Rhaenwen is promoted to Commander

01-01-2952 Aegis is promoted to Commander

12-31-2951 – bigwreck is promoted to Captain

12-30-2951 – Judy-Alvarez steps down as Captain

12-22-2952 – Alpha 3.16 goes LIVE

11-10-2951 – Alpha 3.15 goes LIVE

11-08-2951 – bigwreck is promoted to Commander

11-07-2951 – Judy-Alvarez and OwnTarzan are promoted to Captain

11-07-2951 – Fleet Admiral RevAthiest steps down to Admiral.

11/07/2951 – PFC restructures, outlining new rank requirements.

08-06-2951 – Alpha 3.14 goes LIVE

06-05-2951 – PFC website goes live, and the Issue 001 of [REDACTED] is released

05-30-2021 – PFCS Guilded Server goes live

04-22-2951 – Alpha 3.13 goes LIVE

04-20-2951 – Pyro Freelancer Corps partners with the Wreck Raiders

04-20-2951 – Pyro Freelancer Corps hosts their first ever event, the Daymar Games, a battle royale style deathmatch

01-14-2951 – Devoidsaren and RevAthiest founded the Pyro Freelancer Corps and begins recruiting

12/19/2950 – Fleet Admirals Devoidsaren and RevAthiest enlist and begin their journey in the Stanton System.


Pyro Freelancer Corps is an anti-UEE Federalist Organization. Our goal is self sufficiency and the eventual downfall of the notion of company-owned planets and star systems. We believe the system upon which systems like Stanton are governed is heinous. Democracy has been allowed to die, but the PFC will not let that take their honor.

As law enforcement agencies across the universe continue to uphold the corrupt and unjust laws protecting those who seek to tyrannically rule over the free peoples which inhabit it, Pyro Freelancer Corps steps up to combat them and do what is right while protecting and governing the people of Pyro to the best of our ability, assuring liberty to all who inhabit the system.

Where we specialize in arms dealing and ground based combat, as Freelancers, our skills range far and wide. Maintaining industrial autonomy is foremost in our operation. Though, for a little coin, theres no job too small


Article I – Purpose

The Pyro Freelancer Corps (hereafter referred to as “the Corps”) is a group of individuals who have come together to provide aid and support for one another in performing both legal and less than legal ventures. The Corps’ primary purpose is to provide a fun and engaging gameplay experience for its members as well as breed self sufficiency as game features are released.

Article II – Structure

The Corps is structured as a paramilitary organization with a rank structure based loosely on old earth navies.

2.1 Rank Structure

Fleet Admiral – Fleet Admiral is the second admin-level rank, fourth officer rank and highest rank overall. This rank is reserved for the founders of the Corps. Fleet Admirals overlook the entire operation of the Corps and maintain all responsibilities of all underlying officers, as well as any additional duties that may present themselves.

Admiral -Admiral is the first admin-level rank, third officer rank, and fifth rank overall within the Corps. This is the highest rank a non-founding member may reach. This rank is reserved for those the Fleet Admirals trust to oversee the Organization in their absence. Admirals word is final, overruled by none but the Fleet Admirals. Maintain the highest responsibility within the Corps, including all Captain duties as well as:
-Taking steps necessary to prevent inter-organizational hostility, including removing non-officer members from the Org and the Discord channel.
-Active participation in structuring the Corps as membership increases.
-Will be tasked with leading one or more Divisions as more gameplay features (Salvage, Mining, Farming, Piracy, etc).
-Performs any other necessary actions within the Corps to maintain smooth operation.
-May be assigned specific tasks or duties by Fleet Admirals as seen fit.

Captain – Captain is the second officer rank, and fourth rank overall. Reserved for Commanders who show authority, respect and reason consistently within the Org, as well as active participation and medium-to-high level commitment and activity within the Corps and Star Citizen. Maintains Commander responsibility, as well as the following:
-Active recruitment duty in between personal play sessions and events.
-Active authority within the Corps, mitigating squabbles and other disagreements with grace.
May be tasked with leading a new “task force” and new gameplay mechanics are implemented during development (mining, salvage, piracy, farming, etc.).
-Active participation in planning events hosted by the Corps.
-May be tasked with other duties as admin-level officers see fit.

Commander – Commander is the first officer rank in the Corps, and the third rank overall. Reserved for Corpsmen who show outstanding dedication to the Corps, as well as demonstrate potential to be a voice of authority within. Maintains a reasonable amount of responsibility within the Corps, including, but not limited to:
-Wearing PFC uniform full time.
-Seizing opportunities to recruit players when they are presented.
-Maintaining fairly consistent activity within the PFC Discord server.
-Active participation in player-driven events hosted by the Corps of their affiliate Organizations.

Lieutenant – Lieutenant is the second rank of the PFC, and is for newer members who have had a significant play session with an officer, or for other members which may not choose to commit to an officer role. Lieutenants maintain no official responsibility in the org, aside from wearing the PFC uniform when playing in events where the Corps is participating.

Ensign – Ensign is the first and lowest rank after officially becoming a member of the PFC. Reserved solely for new members who have yet to have a meaningful play session with an officer, Ensigns are few in numbers. Though it is asked, Ensign members are not required to wear the PFC uniform, and maintain no official responsibility within the Corps.

2.2 Division

A division consists of one or more squadrons. Divisions are led by an Admiral, who also leads one of the member squadrons. Divisions report to the Corps leadership directly.

2.2.1 Squadrons

A Squadron consists of 2 or more wings under the command of a Captain. A squadron reports to their flight leader.

2.2.2 Wings

A wing consists of 2 or more fighters under the command of a Commander. Pilots report to their Wing Commander

2.2.3 Crews

A crew consists of two or more people operating a multicrew ship, and operate under the command of a Captain. Crews report to their captain.

2.3 Platoon

A platoon consists of two or more teams led by an Captain who also leads one of the member teams. Platoons report to the Corps leadership directly.

2.3.1 Teams

A team consists of two or more foot soldiers under the command of a Commander. A team reports to their team leader.

Article III– Rules of Conduct

  1. Members of the Corps are to respect other members of the Corps as a brother. There is no class within the Corps. There are only those who are in the Corps… and those who are not.
  2. Although the Corps has no objection to piracy, greifing is not acceptable. Any freelancer engaging in piracy is expected to follow Corps doctrine regarding such.
  3. When members of The Corps make a deal, they are expected to follow through with their deal. Reneging on a deal will be dealt with harshly.

Article IV – Partnered Organizations

Official partners of the Corps are listed in this subsection. Being listed as a partner organization does not imply any obligation on the part of the partner organization. Partner Organizations are protected and may not be targeted by members of the Corps for personal gain, unless an official bounty has been posted.

4.1 Official Partners

Wreck Raiders

Article V – Changes to the Charter

Changes to the chart can be made by consensus of the Fleet Admirals.

Appendix: Change History

11-08-2951 -Updated h4 2.1 – Rank Structure to reflect the changes made effective 11-07-2951 -Updated h4 2.2 – Flights to h4 2.2 – Divisions to reflect changes made effective 11-07-2951 -Updated h4 2.2.1 – Squadrons to reflect the changed made effective 11-07-2951 -Updated h4 2.4 – Platoons to reflect the changes made effective 11-07-2951 -Updated h2 – Article IV – Affiliate Organizations to h2 – Article IV – Partner Organizations to reflect changes made effective 11-07-2951 -Updated h4 2.1 Rank Structure to remove redundant repetition from other relevant documents -Updated h4 2.2 – Divisions to h4 2.1 – Divisions to reflect changes made effective 06-05-2952 -Updated h4 2.2.1 – Squadrons to h4 2.3 -Squadrons to reflect changes made effective 06-05-2952 -Updated h4 2.4 -Platoons to h4 2.2 Regiments to reflect changes made effective 06-05-2952 -Updated h4 2.3.1 -Teams to h4 2.4 Fireteams to reflect the changes made effective 06-05-2952 -Updated h2 Artice III Rules of Conduct to reflect changes made effective 06-05-2952 -Updated h2 Article I Purpose to reflect more clear description of such.