Communications Policy

General Chat

Talk in the third person.

Use the “Hey [You], this is [Me]...” format if you're talking to someone for the first time. Once you have their attention, you can speak normally.

• “Hey DJ, this is Mil, do you need a turret gunner?”
• "Spartan, this is S7, I have a railgun in this red crate if you want it.”

If you’re talking to everyone or no one in particular, just use “This is [Me]...” format.

• “This is Apollo, I have two extra seats if anyone needs a ride.”
• “This is Mil_freak, I’m incap. Can I get a revive?”

General callouts

If you’ve spotted an enemy, or are taking fire, use the Three D’s (Distance, Direction, and Description) on foot or BRAA (Bearing, Range, Aspect, Altitude) in space to help others locate them/you.

On foot:

• “This is Mil_freak, contact north west, 100 meters, 2 Nine tails.”
• “This is Goliath, taking fire from an Aurora on my tail, just outside of PO.”

In Space:

• "This is S7, have an A2 inbound from 270 degrees, 34km out, 1km high."
• "This is Coyote, Scorpius at 175 degrees, 2km out, below us."

Location/detail sharing while streaming

To minimize the risk of stream sniping, share locations and other critical information (PII) in Discord chat whenever possible.

Try not to broadcast our location, the location of our next mission, or of the client through voice chat or in-game chat.

Utilize the Codewords posted before each event and located within ⁠#codes whenever possible in order to prevent the leak of PII.

Acronyms

ASOP: Airspace Organization & Procedures

Terminal responsible for spawning ships/vehicles.

EVA: Extravehicular Activity

Any activity outside of a ship in a zero gravity environment.

HUD: Heads Up Display

The visible information displayed when in the cockpit of any vehicle or while on foot.

PII: Party Identifying Information

Any information that could pinpoint our location to anyone not in Rescue Squad One.

PTU: Playable Test Universe

Servers available from CIG to test upcoming patches. Nontransferable to PU.

PU: Persistent Universe

Standard “Live” servers.

QT: Quantum Travel

Long distance, faster than speed of light travel.

SCU: Standard Cargo Unit

Standard size of all cargo. Can be instanced in 1/8th SCU boxes carriable by a player, 1 SCU (and rarely 2 SCU) boxes transportable by tractor beam.

SCM: Space Combat Maneuvering

The “safe” speed designated by each ship. Identified as the green portion of the speed bar on each ship HUD.

VC Etiquette

Push to talk (PTT) is highly encouraged at all times, to prevent unnecessary radio chatter.

Once a VC becomes large enough (generally 8-10 members), the senior member of the VC may request that all members move to PTT.

• Failure to abide by this request and continuing to send unnecessary radio chatter or background noise may result in a member being muted, removed from the VC, or disciplined.

Communications Moderator role

The Communications Moderator (Commo Mod) is designated to a trustworthy individual who has shown the ability to monitor and manage Voice Chat permissions within general or event VCs. Once designated, the Commo Mods primary role within the VC will be to enforce VC discipline.

• The Commo Mod role will be an ad hoc position, meaning it will be used as needed and may be given or removed as seen fit by Command.
• Misuse of the Commo Mod role will result in disciplinary measures.
• The role will regularly be scrubbed and may be removed without prejudice.
• For inquiries or requests to be granted the Commo Mod role, submit a general ticket with your reasoning.

Com Stances

"At Ease"

• Free coms, talk at your leisure.

"Battle Coms"

• Keep idle chat to a minimum as we expect combat.

"Critical Coms"

• Maintain radio silence unless necessary to allow for important info to be transmitted to all.

"Hold Coms"/"Interrupt"

• Stop all coms and wait for a priority message.

Encrypted Communications

Codesheets and Code words

Codesheets and Code words are used to reference certain locations, planets, or activities in the 'verse in a secure fashion during certain events.

During high risk events, or during certain conditions, ⁠📖codes becomes active and command will provide a one use sheet accessible to anyone of Medic Recruit rank or above. Citizens will require @Temp Security Clearance in order to access the sheet which will be granted and removed as needed.

Each codesheet has a single word reference to ensure all player's are using the correct one and is formed of 2 sections:

The left section is split into Low/Medium/High risk. Most events will start at low risk.

To use this section lookup the codeword associated with the current threat level and the location, this is the word to be used over communications as needed.

If you are acting as a forward scout, you may elect to use a codeword from a higher threat bracket in order to communicate discreetly that there is something at the area that may pose a threat.

The right section of the codesheet is the immediate action section, with particular reference to the pink section, The codewords in here indicate and response to critical threats to the team. Below that are quick reference codewords to ground locations where vehicles can be spawned and ships can rearm/refuel.

Across both sections, much of the information changes with each codesheet, so please read instructions carefully.

The immediate action section in pink is the most important section in the codesheet, broken down into 3 core alerts:

Streamsnipe in progress - There is someone watching the stream and attempting to grief, be on high alert and follow command instruction, DO NOT ENGAGE IN GLOBAL CHAT

Return to HUR-L1

All callsigns regroup at Hur-L1

Immediate jump to <location>

Emergency jump to first available QT marker then meet at stated location, Air crew should provide cover to larger ships before jumping

In the event of a suspected security issue, all @Temp Security Clearance will be cancelled and a new codesheet generated with a new reference word.

Sharing codesheets outside of the dedicated channel without permission is grounds for disciplinary action

Condition Codes

	Condition Codes will be announced to the Org when the threat to Org members is elevated. Conditions come in three stages, Blue, Yellow, and Red, with Blue being normal, and Red being the highest alert.

Condition Red

For Condition Red, the following text will accompany the announcement:

@everyone Immediate attack expected

All Command and team leads to Mumble

Purge Temp security Clearance

IMMEDIATE fracture of event VC into secure channels with limited numbers per channel

1. All crews to battle stations, all ships should only stay on the ground for as long as needed.
2. Weapons/turrets ready and pointed at all non party members.
3. Scramble all air cover to protect fleet.
4. Ground leaders evaluate whether to proceed or pull back based on threat.
5. Fire-first authority to all medics and above to protect the team.

Condition Yellow

For Condition Yellow, the following text will accompany the announcement:

@everyone based on recent activities, I'm moving the Org to condition yellow. Expect trouble.

All events are to take place in secure channels and with dedicated security until further notice.

1. Codesheets are active and temp clearance roles will be killed daily.
2. Security check to take place in server regularly. Names to watch out for will be provided if possible.
3. Check org status of all rescues before attending. Proceed with caution and expect beacon baiting.
4. Fire first authorized for SM+ should they feel the situation requires it. Keep your teams safe.

When the situation has passed, the following announcement should be made:

@[Everyone], We are returning to Condition Green. The current threats have passed. Please maintain vigilance and report any unusual or suspicious activity or attention towards medics, medical orgs, or RS1 in particular. Stay safe out there.

Condition Green

Normal Org Operations have resumed.