Option to disable ability to use ocomms

Oct 10, 2024
297
64
41
What does this suggestion change/add/remove:
Have you or a loved one accidentally used ocomms causing a big infobreach? Well do I got the suggestion for you.
This Suggestion adds a option to toggle if you want to be able to use ocomms!

Has something similar been suggested before? If so, why is your suggestion different?:
No i dont think

Possible Positives of the suggestion (At least 2):
Less oopsies
Less me having to explain why ECC is my pet cat on ocomms

Possible Negatives of the suggestion:
Dev time ig

Based on the Positives & Negatives, why should this suggestion be accepted:
This suggestion fixes the common problem of silly goofy mistake
 

Walter Smoth

Well-known Member
Apr 20, 2025
12
0
41
Advil writing this from his jail cell after making fun of the ECC and breaching Class F over O-Comms:

giphy.gif
 
I do think that, at least for F roles, ocomms should not be as easy to use as it is. Ideally, you'd want little slip-ups to turn into RP as a result, but honestly, it's just abused more than anything else by the 15,532nd cadet of the day minging and yelling about how "the O5 council sent A-1 to nuke the 008 zombie virus," which yes, failbreaches like that are obviously handled by staff - But IMO it'd be nice if there was some kind of mechanical limitation to make things better for both the community and the staff, because I can't imagine it's that fun handling the umpteenth cadet failbreach on ocomms when there are other things that staff could be doing at the time.
+Major Support
 

Reputation

Civil Gamers Expert
Jul 17, 2022
273
36
111
mind blowing chat commands to prevent this

use "//" for ooc, instead of using "/ooc"
use "/oc" for open comms

another tip to not send accidental messages in open comms, when meant for ooc
read your message before sending it. i know reading is hard, but i believe you can do it!
 

Reputation

Civil Gamers Expert
Jul 17, 2022
273
36
111
mind blowing chat commands to prevent this

use "//" for ooc, instead of using "/ooc"
use "/oc" for open comms

another tip to not send accidental messages in open comms, when meant for ooc
read your message before sending it. i know reading is hard, but i believe you can do it!
disreguard this

neutral
 
Just rework this suggestion to make all communications between everything faction leadership based, instead of SA+ needing to config everything. This would also make stuff like K/18/AP0 and other commslines also function within gameplay, instead of just being a openly visible commsline with the most easily metagamable RP ever.
IIRC, this kind of thing has been denied in the past for reasons like "it making chat seem dead" and "ruining people's ability to spectate ongoing RP interactions" or something along those lines. I don't have the actual past suggestions in front of me. I think it is about time to resuggest this idea, and I backed it then, I'd back it now.
 
Oct 10, 2024
297
64
41
mind blowing chat commands to prevent this

use "//" for ooc, instead of using "/ooc"
use "/oc" for open comms

another tip to not send accidental messages in open comms, when meant for ooc
read your message before sending it. i know reading is hard, but i believe you can do it!
ok but sometimes brain mush and do stupid stuff just make it brain no worky proof
 
IIRC, this kind of thing has been denied in the past for reasons like "it making chat seem dead" and "ruining people's ability to spectate ongoing RP interactions" or something along those lines. I don't have the actual past suggestions in front of me. I think it is about time to resuggest this idea, and I backed it then, I'd back it now.
I love metagaming active RP scenarios that have nothing to do with me!
 
  • Like
Reactions: Emilia Foddg