Terran Stellar Navy 42nd Space Fleet
Phase III - Movement to Home Stations
Mobilization is the act of assembling forces for active duty. Crews across Canada and Europe are assembling in their home town or city and have begun active duty.
There's a lot of information in this correspondence, we hope you'll take time to read this. Be sure to ask questions in the lobby channel through Discord, the group's collective knowledge will be available to anyone.
Instructions for Sunday, April 19th, 2020 at 20:00Z | duration: 3 hours.
Be sure to double check the start time for your local time zones.
Welcome to the third fleet wide game of 2020. We are glad to see everyone who registered and confirmed their crew's participation, here are the four ships that will be ordered to deploy for our training and missions in real time. The other four will remain in docked at the ready in the event we have more people who turn up.
Command Station located at Deep Space One [CIC]
We at TSN Command wishes everyone a great game day in your respective communities. I hope you are all excited to play, while remaining inclusive, and keeping the space safe for current and new players. Let's physically distance ourselves, but not socially for these fleet games by staying engaged in what ever way works best for you.
- CAP-Farside (confirmed)
- MSN-Galissoniere (confirmed)
- TSN-Bluenose III (confirmed)
- TSN Hopper (confirmed)
- TSN-Vanguard (ready)
- TSN-Colossus (ready)
- TSN-Odyssey (ready)
- TSN-Thames (ready)
RAdm. David Trinh
The 42nd Fleet, 1st Battle Squadron
Our objectives at the Combat Information Centre (CIC) are:
Table of Content (TOC)
- to keep cost of delays minimal throughout the whole Artemis fleet experience. So, be sure to read all the instructions so you know what to expect before you and your crew connects.
- bring together and manage information of all ship's status and its surroundings, and supplies this to the Admiral for orders. The Combat Information Centre is to function as: information ordering, gathering, and presentation to the decision makers. They are typically broad orders and at times, CIC staff will check in to see how you're doing.
- CIC staff members for this duty shift includes Starry and Davis, members of the international Artemis community. They will be overseeing a good majority of the operations from CIC during the game, and advising the Admiral.
I. Game Version
II. Latency and Network Topology
III. Communication on the day
IV. Using TeamSpeak
V. Training and Mission Schedule
VI. Photos and Videos (Optional)
VII. Streaming and Broadcasting (Optional)
IX. Tips and things to know
X. Auditing for improvement
The game version is the most recent, this should be accessible by your crew. 
II.Latency and Network Topology:
Since we are now expanding across to oversees from North America, moving the server to different region and scaling it up is not a problem. We want to ensure your crew don't get drop out due to latency which is annoying during real time game play. Be sure to send your latency report to CIC or post it in your Discord channel by geography.
III.Communication on the day:
We are using the 42nd Fleet's Discord Server as the primary long range and persistent communications system. Ensure the Discord client is installed and configured on your computer. The host name or Internet Protocol Address will be automatically posted into the lobby channel as soon as the server comes online.
For in game play, players shall use a TeamSpeak client to communicate with their crew, pilots and CIC staff.
We are encouraging everyone to socialize in the Discord and TeamSpeak lobby before and after game play. Be sure to read the #Welcome text for acceptable use. Recommend you update your Discord nickname to the following format, ie: "Joe Smith|TSN Lambert".
There channels of communication on the 42nd Fleet's Discord server are the lobby for general discussion and chatter. The other is a secure channel [RP] #cic-text, which is used to connect to the both the TeamSpeak and Artemis Server. This information may be in the form of an Internet Protocol Address or a host name, that information will become available typically one hour prior to deployment. It is important to refer to that text channel to find out where the two services are provided. Both the Artemis and the TeamSpeak server can change throughout the duty shift.
When you connect to the TeamSpeak Server, you will appear in the Lobby. Be sure to check your microphone and sound settings and update your name so we know who you are.
Report into your Commanding Officer if they are about. If you don't have one, do not worry as we will assign you to a bridge after each game. If you have preference, let the duty officer know that you'd like to play on a bridge that has an open role. Keep in mind that not all bridges speak English as we are now an International game service.
The Message Relay Operator (aka MRO).
Each ship should have a Message Relay Operator (MRO) who's in charge of just communications on the secure channel to CIC and other ship's MRO.
They are responsible for monitoring and transmitting verbal communication on a separate and secure audio channel on behalf of their bridge. The MRO will have direct lines only through a Server Group using a hot-key they define on their console.
Everyone else will be able to communicate only on the voice channel they are in when on the ship, and they will not be able to hear the communication between MROs and CIC.
The staff on Deep Space One (DS1) will be operating as the Combat Information Centre (CIC) where communication will be in English .
Internet Protocol Address or host name of TeamSpeak and Artemis servers should be treated as a secret code to the fleet's operations. It is imperative everyone understands these are processes which should naturally lend itself to providing added layers of security to keep game operations on-going.
The Server's Internet Protocol addresses or host names will be transmitted on Secure Channel [RP] #cic-text only. Since the event can be streamed online and recorded, we request that sever addresses or host names are not spoken or typed in the other channels to maintain secure access to the hosting server. Server addresses can change after each game to ensure both operating stability and security.
Self Assign as MRO
1. Right click your name in TeamSpeak, select "Set Server Group".
2. Select "MRO[Test]" to enable this role.
3. Select again to disable this role.
Once you've enabled this, you will hear all communications between CIC and MROs.
Hot Key Assignment
1. Select "Tools" in the menu, or press ALT-P on your keyboard.
2. Select "Whisper" in the left column of options.
3. Press the button "Whisper Lists".
4. Press the "New" button in the bottom left corner.
5. Decide your Hot Key to hold in order to speak to CIC and MROs and press it when prompted.
6. In the "Whisper to:" option, change the option to "Groups".
7. In the "Group Whisper Type" option, change the option to "Server Group",
8. In the next option box below, change the option to "TSN 42nd Fleet Comms Server".
9. In the next option box below, change the option to "MRO[Test]".
10. In the "Group Whisper Target", change to option to "All Channels".
Once this process is completed, you will be able to speak directly to CIC and other MROs; however the people in your channel will not hear you.
The Hot Key you decided in step 5 needs to be held down in order for this function to work.
Each ship will be docked at a Deep Space station when your crew arrives, where the Captain will give the orders to release the Helm, Weapons and Engineering controls over to the ship's bridge crew. CIC staff will release the docking clamps thereafter and transfer command over to each ship.
V.Training and Mission Schedule:
45 minutes prior to duty shift - CIC will be online, where the Admiral will be doing final vessel inspections. This is where you can test your server connections, fly around with your crew on your ship in open space. We are moving to a more casual drop in and play instead of readying all ships to play at once. The hopes to minimize delay and have more in game time than just waiting around like in the real Navy.
30 minutes prior to duty shift - Establish communication to CIC and other ships. Practice coordinated rendez-vous with each other, run battle drills with friendly ships or the fauna.
Start of Duty Shift.
CIC will assess and then configure the difficulty level and scenario based for each game.
5 minutes - Formation flying of all ships for screen shots and photo taking on your bridges.
Duty shift debrief and dismissal (End Role Playing)
After the scheduled time, people are welcome to continue chatting in the lobby, we encourage you to have crew to crew video chat with each other.
VI.Photos and Videos (Optional):
In the past, our game session took place as a full in person bridge crew, where a group photo is taken and use for posterity and social media fodder. We would love to see everyone we all played with still, so I would encourage you to think of a ways you could represent your crews online in some creative way.
VII.Streaming and Broadcasting (Optional):
Those who plan on streaming their bridge in action, you can do a live stream on various services. Be sure to broadcast that URL so people can pop on to watch. You'll need to ensure your accounts are approved to stream, so test that our prior. We plan to broadcast CIC operation. The Discord user 'A1ON5678' will be audio only recording account. Each crew will be responsible for their own broadcast stream, noting their URL on social media or Discord.
Broadcasting To The World
This effort is to provide semi-active engagement with the general Artemis gaming community worldwide. You and your crew should know that your voices and game play are being used to promote Artemis in general, the role playing group representing the Terran Stellar Navy crews and affiliates.
Artemis Spaceship Bridge Simulation 2.75 stock
Discord client, "42nd Fleet " https://discordapp.com/
TeamSpeak client 3.5.2
High Speed Internet Access (Minimum of 15 Mbps download, 5 Mbps upload for six computers)
IX:Tips and things to know:
Please welcome crews from the registry.terranstellarnavy.ca. This is a place where we have been accumulating crew information for fleet games.
Remind everyone to ensure their Windows Update Settings are configured, it should not run leading up and during the local duty shift times.
Enable and configure Quality of Service (QoS) on routers on Transmission Control Protocol (TCP) port 2010 to high priority.
Note your ship number when connecting to the server. It is recommended when a role call is performed on your bridge, each player should report their ship number and station is ready to their captain or first officer. ie: "Ship five, TSN-Thames, Science officer ready". Due to the openness of Artemis, you can accidentally take control of another ship's essential system if you don't confirm your ship number, name and station... MROs should be able to sort that out.
Open as many instances of Artemis, in case of console crash you can switch over quickly. We want to load the nebula server to capacity.
Send your latency statistics online to the Discord channel MAIN[RP]/#lobby and state your general location for most appropriate Nebula Server Topology configuration 2 hours prior to duty shift.
There is typically a 3-5 minute window in between game server crashes, it will give your crew members time for any comfort breaks. We will most likely reconvene on Discord in that event. Be sure to check the #cic-text for possible new ip/hostname.
The Message Relay Operator (MRO) can also operate off of a mobile device if they wish instead of a computer. The MRO can also be the Comms officer, instead of a separate player on the bridge in addition. TeamSpeak client on mobile devices may need a license for a fee.
The entire session will be recorded from the Combat Information Centre's perspective, including communication on the voice channel. Crews from other bridges are planning to stream their interactions online. The recording will most likely be uploaded and shared to the general Artemis forum and various social media platforms. It is common courtesy to ask the crew if that recording and streaming is alright verbally.
Social media campaign of the fleet game will continue and be ongoing. Please share your photos in your respective Facebook Artemis groups and on Discord.
X.Auditing for improvement:
The recording will help us audit the service. The information provided will help decide and prioritize which points to enact for future fleet games.