View this email in your browser

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, March 1st, 2020 at 20:00Z | duration: 3 hours.
Be sure to double check the start time for your local time zones. 

Welcome to the first 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.[1] The other four will remain in dry dock being offline.

Command Station located at Deep Space One [CIC]

  1. TSN-Bluenose III 
  2. MSN-Galissoniere
  3. TSN-Lambert
  4. TSN-Vanguard
  5. TSN-Colossus (offline)
  6. TSN-Odyssey (offline)
  7. TSN-Serenity (offline)
  8. TSN-Thames (offline)

Our objectives at the Combat Information Centre (CIC) are:

  • to keep cost of delays minimal throughout the whole Artemis fleet experience.[3] 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.

Game Version:
Since to minor releases became available within 60 days, both versions should be accessible by your crew. [8]

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. 

Communication on the day:
We are using the 42nd Fleet's Discord Server as the primary long range communications system. Ensure the Discord client is installed and configured on your Message Relay Officer's console.

We are encouraging everyone to socialize in the lobby before and after. 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" when you arrive.

There are two main channels of communication on the 42nd Fleet's Discord server, the first is the lobby for general discussion and chatter. The other is a secure channel on Deep Space One (DS1), which is used for orders for in game play. This will become available a day prior to deployment.

Each ship should have a Message Relay Operator (MRO) who's in charge of just communications on the secure channel to DS1 and other ships. They are responsible for monitoring the secure text channel #ds1-text and the voice channel DS1. The MRO will have privileges to speak on voice and view #ds1-text content only. Everyone else will be able to listen on the voice channel only, and the #ds1-text channel will not be visible or accessible to them.

The staff on Deep Space One (DS1) will be operating as the Combat Information Centre (CIC) [2]. You'll need to get yourself authorized and have your security clearance performed on the fleet's open channel to get the server's Internet Protocol Address or host name for your crew to connect. Each ship should have one message relay operator, who will be cleared for communication to DS1 and other message relay operators only in a secured voice and text channel. That Discord username would have already be assigned during the confirmation process. 

IP/hostname will be provided to MROs through a secure channel only

Internet Protocol Address or host name of 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 layers of security to keep game operations on-going. 

The Server's Internet Protocol addresses or host names will be transmitted on the #ds1-text secured channel only. Once your comms/Message Relay Officer receives it, they will provide that information to all members on your bridge internally. Since the event is being 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. 

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.

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.

Photos and Videos (Optional):
For posterity and social media fodder, assign someone to take photos of the crew in action, and at the end with everyone in a group shot. We would love to see everyone we all played with. 

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 DS1's CIC operation.[7] The Discord user 'A1ON5678' will be audio only recording account. Each crew will be responsible for their own broadcast stream, noting their URL in the registration form.  

Broadcasting To The World:
This effort is to provide semi-active engagement with the general Artemis gaming community worldwide. Be sure to let your crew know that their 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.7.4 and 2.75 stock
Discord client, "42nd Fleet [2020]"
High Speed Internet Access (Minimum of 15 Mbps download, 5 Mbps upload for six computers)

Tips and things to know:
Please welcome a new fleet from France and Belgium to the game. The Marine Stellar Fleet/Marine Nationale Stellaire is led by Cmd. Ophicia. See their page on the Registry for more information.

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... 

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 your local text channel for most appropriate Nebula Server Topology configuration.

There is typically a 3 minute window in between game server crashes, it will give your crew members time for any comfort breaks. If you have extra attendees/crew members at your location, have them fill in at times like this. 

The Message Relay Officer (MRO) can also operate off of a mobile device if they wish instead of a computer. Any messages sent into the #ds1-text will alert their device with a sound or a buzz. The MRO can also be the Comms officer, instead of a separate player on the bridge.

The entire session will be recorded from the Combat Information Centre's perspective, including communication on the voice channel. If this is an issue with the Message Relay Officer, it is recommended someone else take that role. Crews from other bridges are planning to stream their interaction online. The recording will most likely be uploaded and shared to the general Artemis forum and various social media platforms.

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. 

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.

We at TSN Command wishes everyone a great game day in your respective communities. I hope you are all excited to play, while we remaining inclusive, and keeping the safe space for current and new players. 

RAdm. David Trinh
The 42nd Fleet, 1st Battle Squadron

The Combat Information Centre will be using information gathered from the TSN Registry for game day. We will put all your ship information into our cloud server for automation. Ensure it is all up to date as soon as possible.

We have scheduled nine (9) fleet games for 2020. We were aiming for at least 4 dates where the 9th and 42nd fleet continue with joint forces operations. We've open up the games now to the International Artemis Community to participate. 

This idea of a Joint Forces Operation was finalized in 2018. Here was the order that was issued by the office of High Command. 

The 2020 Schedule:
April 5, 2020
April 19, 2020
June 7, 2020
July 5, 2020
August 30, 2020
October 11, 2020
November 15, 2020
December 6, 2020

Do you know of other Artemis Spaceship Bridge Simulator crews who would like to join in our fleet training and missions? If so, forward them this newsletter and get them in touch with us.

Once again, thanks you for your interest and willingness to participate in this attempt to coordinate and operate an eight ship fleet game. If you do not wish to receive anymore communications regarding this, select the unsubscribe link below.

1. TSN Vessels Specifications - 2020-03-01 Tab
4. 42nd Fleet Discord Server for Communications
5. Mobilization
6. Phases of Mobilization for Reservists
7. A1ON5678's Broadcast URL
8. Artemis Spaceship Bridge Simulator 2.74 and 2.7.5
Copyright © 2020 TSN 42nd Space Fleet, All rights reserved.

Want to change how you receive these emails?
You can update your preferences or unsubscribe from this list.

Email Marketing Powered by Mailchimp