Messages

Starship Avalon has a state of the art duty comm system.  Rather then having to find out who's running a station/section at a particular moment you simply whisper our comm system and it will determine whom to send the whisper to.  Below is the list of prefixes and an example of how the message system works.

/comm <prefix> <msg> (ex: /comm XO Finished the task sir.)

CO - Commanding Officer	XO - Executive Officer	3IC - 3rd In Command
HELM - Helm	TAC - Tactical	OPS - Operations
Aux1 - Bridge Aux Station 1	Aux2 - Bridge Aux Station 2	CE - Chief Engineer
MDC- Marine Detachment Commander	SCI - Science	MED - Medical
IC - Imperial Command	SRV - Crew Support (Servers)

Logging In

When you arrive at a duty station such as the helm and are the senior helm officer you would either relieve the operator or take control of the station.  To do this whisper comm:

/comm LOGIN <prefix> (ex: /comm login XO)

Note: Positions such ESF and Chief Engineer don't have a particular station.  As such they may log in anywhere on the ship.  Positions with a station like helm should be AT the station so as to be able to take commands when issued.

Logging Out

When you have completed your duties and are going off duty or have to leave the station please log out by whispering comm:

/comm LOGOUT <prefix> (ex: /comm logout XO)

Onduty Check

If you'd like to see who's onduty at what station whisper comm:

/comm ONDUTY

Public Address System

In the event of emergency or required use you may use the comm bot to make a shipwide announcement.  To do this whisper comm:

/comm PA <msg> (ex: /comm PA Medical Emergency in Shuttlebay!)

NOTE: Abusing this feature (or any other feature in Starship Avalon) will result in disciplinary action.  If you abuse it seriously enough you will be immediately removed from membership and forbidden to reapply on ANY characters.

Bridge Emit

In order to facilitate communications on the bridge the bot will emit any conversation not in []s to the entire bridge crew.  As such Bridge conversation should be longer posts rather then a series of short posts and OOC conversation is restricted to []s  Off topic short posts can use [] as well and private conversation can use [] as the bot will not auto-emit this.  (NOTE: Conversation is ONLY emitted to the bridge unlike the PA system which is shipwide.)

Ship to Ship Communication (New and Experimental)

NIOTE: This System is still in Development and may change at any time Donot attempt to use this System unless is has been Authorized by your Ships Commanding Officer.

This system links two Ship's using the SAC Bot System. Once Ships are established in the ship Registry, Bridge Stations can /comm Hail Start [Shjip|Name] [Optional Priority] . This will Prompt Members on the receiving Bridge to respond with thier Comm bot IE /comm Hail Open.

Once the Channel is Linked. an Emit is displayed and a sound plays to simulate the "On Screan" effect. At this point the Comm ssystem works like the Bridge Emit.. Bridge Personell Speak and Emote as Normal where the E-Mit Repeater Echos each Message to the reciving Ship. Like the normal Emit OOC Brackets "[ ]" are ignored. Unlike the Emit Repeater, This Doesnot ignore Logged in Duty officers for obvious reaons. IE Ships CO needs to communicate to the receiving vessel

/comm Hail Close closes the Channel enabling other Authorized Vessels to communicate.

Online Detection: If any point the connected Uploader goes offline Or it's CommBot Goes offline.. The Channel Closes with "Communications Lost"

Conclusion

The Comm system is mainly for finding out who's onduty and messaging the senior staff member onduty in a particular area and emitting bridge material.  PLEASE do not overload the bot as it will lock it out from being able to be used by members and result in disciplinary action.  If you have a large series of commands to give it please wait a second or two between commands.  Thanks.