Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[SUGGESTION] More Channels for Covenant Comms #3372

Open
SharkLordSatan opened this issue Jan 29, 2023 · 2 comments
Open

[SUGGESTION] More Channels for Covenant Comms #3372

SharkLordSatan opened this issue Jan 29, 2023 · 2 comments

Comments

@SharkLordSatan
Copy link

Currently as it stands, the UNSC has at least 2-3 different channels for comms, available to different roles (not counting the cargo channel). From my understanding, ODSTs get access to standard and ODST comms, and ONI/Spartans get access to ONI comms. I don't recall if a Spartan-specific comms channel exists or not.

Meanwhile, the Covenant get access to only one channel, with no specific channels for different roles. This is somewhat frustrating as it means that when the UNSC gets their hands on Covenant comms and gives it to a person who can speak Sangheili - which happens rather frequently - the entire Covenant Battlenet is compromised with no means of circumventing it outside of having to be mindful of information, or hunting down and killing the people who have access to Covenant comms. (Which rarely happens because most of the time the people who do have access to Covenant comms are ONI Researchers, who rarely - if ever - leave the safety of the ONI base, which basically means the comms are compromised anywhere from the scanning phase onward to almost the entire round from the ODP phase onward.)

Basically, TL;DR Covenant should get different comms channels depending on their role, similar to how the UNSC do. Here's some suggestions for channels and what roles should have access to them.

Battlenet: Basic-level communications. Available to all members of the Covenant.
Cargo: Basic-level communications, but reserved for cargo-related communications. Available to all members of the Covenant.
Obedientary: Comms reserved for certain Covenant leadership roles. These include the following; T'vaoan Commando, Jiralhanae Major, Yanme'e Ultra, Unggoy Ultra, Sangheili Major, Mgalekgolo, Huragok, Lesser Prophet, and all other species roles with ranks higher than the ones listed.
Superior: Comms reserved for high-ranking Covenant leadership roles. These include the following; T'vaoan Champion, Jiralhanae Captain, Yanme'e Leader, Unggoy Deacon, Sangheili Ultra, Huragok, Lesser Prophet, and all other species roles with ranks higher than the ones listed.
Leadership: Comms reserved for the highest ranking Covenant leadership roles. These include the following; Jiralhanae Chieftain, Sangheili Shipmaster, Sangheili Honor Guard, Huragok, and Lesser Prophet.
Spec-Ops: Comms reserved for the Spec-Ops caste, but certain Covenant leadership roles have access to these comms as well. These include the following; Sangheili Ultra, Sangheili Shipmaster, Huragok, Lesser Prophet.

Some of these can probably be mixed with one another (i.e the Spec Ops comms), but overall I think just having more comms channels would help make the Covenant somewhat more secure against some guy in ONI just getting his hands on a Grunt's Battlenet headset and instantly having access to the entirety of the Covenant's communications. The Covenant AI role would also have access to all of these comms channels.

@ghost
Copy link

ghost commented Jan 29, 2023

1)I think Superior + Leadership might be combined into one channel.
2)I think Battlenet + Obedientary might be combined into one channel.
Having a lot of channels is great, but this will at some point make communication harder since it will probably force you to jump from channel-to-channel.

Even UNSC has basically 3-4 channels, not...6.

@Aroliacue
Copy link
Member

I'll have a look at this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants