|
|
| Line 86: |
Line 86: |
| === Communications === | | === Communications === |
| * Members active in the community space should ideally be on Mumble, even if you don't intend to talk (if you are hearing impaired, let us know). | | * Members active in the community space should ideally be on Mumble, even if you don't intend to talk (if you are hearing impaired, let us know). |
| ** Community communications are by default “OPEN COMMS”, so you may join mumble if you are not actively participating in community activities, however you MUST follow combat comms when they're active. | | * Please familiarise yourself with our [[Communications_Policy|Communications Policy]] and [[Voice_Communications_Etiquette|Voice Communications Etiquette]]. |
| ***Open comms are usually only suspended for two reasons:
| |
| ****Someone calls “Break Break” or "Check Check" over mumble, which indicates a new threat or that a fellow Unista is in immediate danger or has important information to announce. Please allow the pilot to speak.
| |
| ****"Combat Comms” is called over mumble. This indicates a fight is underway and non-combat related chatter should pause for the duration. Prolonged combat should be moved as soon as is practical to the HSC PvP sub channel in order to leave the main comms open for general learning.
| |
| **** When first entering a community mumble channel. please wait briefly before speaking (unless it is very urgent) to ensure "Combat Comms" is not in operation.
| |
| ** If you are operating in a fleet when there is a lot of general chat in comms, you may wish to move to a separate Mumble sub-channel where it will be easier to communicate with your fleet.
| |
| | |
|
| |
|
| === PvE === | | === PvE === |
