Overhaul Complete!

I have finally completed the work on the TSN RP Mission script (also known as the Sandbox mission script) to create automated Jump Gates and Nav Points. It has been a long and arduous process, and it required a re-write of a number of elements in the script. In the process, I was able to refine some of the script so that in the future, it will be easier to add in new systems and sectors to the map. The script is now all tested, and ready for use (although of course, I will always be adding to it and tweaking it here and there!)

The overhaul has removed the need for client key presses entirely. Although it is something I was reluctant to remove, it has been necessary to ensure that the script works properly. In tests, the client key presses were unreliable. As client keypresses were a requirement to use the script, when they didn't work the script was unplayable. 

The script focuses on the area in which the TSN 2nd Fleet operate. In total, there are 8 systems that can be accessed and two waypoint sectors. Each system has between 2 and 6 sectors, giving a massive number of areas to explore (the whole script has 27 sectors in total). Navigation is through Jump Points and Nav Points. The new jump gates are something I am particularly proud of. They are large rotating structures in space. As you approach, the gate activates, spinning faster until fully online. To enter, you have to fly in to it. The visual effect of such a large rotating structure in space is pretty cool. And all that has been used is generic mesh files and image files from the game folder itself. I have also designed a "Refuel Point" that floats alone, rotating on its axis. When a ship come close to the refuel point, it will begin transferring energy to that ship, almost like a station. It is an alternative to the Fuel Collection System which had to be removed because of the removal of client key presses.

The next phase is going to be adding more features to sectors in the script. I have already added a second sector to the Phoenix system. I am going to further develop the system to make it into a main trading port, with lots of traffic coming and going from neighbouring alien system. Using generic meshes, I will also be able to add in some different "bases" for both visual effect, and to act as points for ships to travel to and from. Osiris system is also going to have a number of additions and will be developed into a 'tourist destination'. From their, the Poseidon Rift can be accessed, a sector that I go into in more detail on the wiki pages.

I also want to start adding in the Mission Packs again. There have been requests for more missions in the Sandbox, and I have a few ideas about one to write. Originally, a crew was able to accept or decline a mission using key presses. Without them though, I am going to have to think of another way to allow crews to pick up missions. One option I am considering is having a "mission waypoint" that broadcasts a message when a ship comes new. The ship could then move into close range to accept the mission, or stay clear to leave it for another time. 

The mission script will be accessible on the Artemis Forums, under the Mission Scripting sub-forum.

The RP Mission Script & Comms Officer to Operations Officer

The mission script, tailored specifically to the TSN RP Community has continued to developed, and is starting to be used more frequently to run official missions. So far, those missions have been relatively straight forward, focusing mainly on invasion style scenarios where the enemy just need clearing out of a sector. Really, it has just been a test of the script to make sure it is all working properly, and so far there have been few bugs encountered. 

The mission script itself is purely a Game Master script. Taking the ideas from the Sandbox mission script, and adapting them to allow multiple bridges to play together, I have managed to create an open sandbox specifically for the RP Community. A Game Master can then add in enemies, allies, creatures, send messages and a number of other functions in order to take the crews through a mission or story line. I took a couple of volunteers recently and showed them the controls for the Game Master console in the hope that soon they will be confident enough and practised enough to run official missions. 

In the missions I have run recently, something that has been sorely missed was the Fuel Collection System. There have been a couple of missions that dragged on due to every ship having critical energy levels and no way to recharge. Until now, I have not included the code as it was only set up for one vessel. Today however, I have reworked the Fuel Collection System code and added it to the RP mission script. Although the code is simpler (the cascading damage effect has had to be removed), the restrictions on speed and shield state still apply, making it something that must be used when the situation allows. I have also moved the activation and deactivation keys to the Comms console.

As I completed writing the code, I realised that the role of Comms officer has been gradually evolving. During missions, they no longer sit passive, relaying standard messages that arrive and have no real consequence or bearing on the mission at hand. Instead, a Comms officer must send out instructions to activate the jump points, selecting the correct gate codes. They are responsible for activating and deactivating the Fuel Collectors. They also have to relay key mission information such as when lifepods are picked up as well as open hailing frequencies for voice communications (the voice comes over teamspeak, but a GM can hold off until the Comms Officer hits the key that puts up the "Hailing Frequencies Open" message). In a recent mission I ran, I also typed in garbled messages that the Comms officer had to decode.

With all the extra work, it means the Comms Officer role is becoming more of an Operations Officer role. There is potential for further expansion on the role too. I have ideas about how to simulate standard outgoing text messages, using a similar system to the GM controls that I developed for the script. I would have to make a few minor alterations to the script and add in a couple of new events, but I think it would be possible to generate a system for a Comms officer to send messages that a GM could then reply to. Simple messages could be Yes/No, but there could also be specific messages for different scenarios, which communicate different things. It would then be possible to play out diplomatic scenarios. Another idea I was considering bringing back was the ability to deploy extra sensors, or activate a sensor sweep. This could give extra information about the local area, or intelligence reports. These are for the future, but there is a lot of potential! 

Cronus System and Transfers

After recent patrols in the Cronus system, it would seem that the enemy precense is being steadily increased. The last patrol, conducted by the TSN Osiris, met with a heavy ambush by enemy forces. It is evident that they are now truely aware of our presence in the system. It would also seem that this is yet another system that the Kraliens will claim as their own, and I am in no doubt that they will contact us soon with surrender demands, or demand tithes in order to transit the system. Neither of these are options that I will pursue.

The engagment between the TSN Osiris and the enemy forces means that an escalation in the defence of the Cronus system will be required. The captain of the TSN Osiris and her crew performed admirably, but had to fall back due to supply issues. They did manage to cripple the enemy fleet enough to allow two TSN Destroyers to be depatched and assist in clearing up the enemy forces.

This recent action has promted me to send a request to Fleet Command for additional support in the defense of the system. I have submitted a request for an observation post as well as more Destroyers and Escorts. It is my intention to deploy a forward observation post in the system, acting as an early warning system, as well as a supply post for any TSN vessels operating in the area. I have also requested authorisation to extend our patrols and explore more of the Cronus system in order to find any links back to TSN space, or links in to Hegemony territory. This will give us a more detailed map of our local systems, and will allow a more coordinated defensive plan to be implemented.

For now, patrols in to the Cronus system will be increased and any patrols will consist of multiple vessels, formed in to a battlegroup. I have a number of TSN Destroyers and some escorts already at my disposal, and the addition that number will hopefully increase.


Back on station, the system for tranfers has been developed further. A Tranfer Request form has been created in order to allow officers to apply for transfers between ships. This will allow officers to gain more experience serving under different captains.

Operating on different crews and under different commanding officers is important for officers who wish to advance in rank. Although all commanding officers are trained to the same standard, each one brings their own personality to commanding a ship. Each one has different strengths and areas of expertise and the tranfers allow an officer to see these and learn from them. It will also allow officers to work with different crews, sharing what they know with other ranking officers, and learning from one another.

Not only this, officers will learn how different ship types operate. Currently we have only Light Cruisers and Battleships, but these ships have to operate differently to oneanother. When we have more ship types operating, differences will become clearer too, such as how a scout operates, or how a dreadnaught operates. Although it is easy to know how they work in theory, in practise it can feel very different.

I am hoping, with an easier system for transfers, officers will take the opportunity to move around crews and gain greater experience.

The Command Staff and Senior Officers

With the Division growing at a steady rate, the work required to effectively manage the Division has also increased. Promethean is now home to almost 100 TSN Officers, and there are 3 fully crewed TSN ships in service, all under my command.

Now that I have a trusted core of Senior Officers, I have started delegating some of the tasks required to manage the Division. The first responsibility assigned was the management of the Officer Records. Each ship captain has an assigned crew, and all those captain have access to their officers' records. The responsibility for keeping them fully up-to-date is now that of the captains. So far it has worked well, and the captains are showing me that I can trust them with such tasks.

There has been an overall general restructuring of the way that Senior Officers work too, particularly those in command. I regard the current Senior Officers as being a "temporary" command staff, in that they are given assigned tasks, or involved in making decisions about the running of the Division. As the number of Senior Officers grows, only a small selection of them (around 5 or 6) will make up the actual Division Command staff. Other Senior Officers will be involved in Senior Officer meetings, which are a relatively new idea to allow regular meetings before a duty shift, however it would be the Command Staff who make the final decisions about the Division.

Until now, much of what I have done to manage and develop the Division has been done solely by me, and I have kept a tight control over the Division. I have always intended giving others greater responsibility, but only to those who have proved to me that they can do so in a way that will not compromise what has been created. The current 'temporary' Command Staff have progressed from cadet through each rank. At each point, they have fulfilled the requirements of that rank virtaully to the letter. They have become close colleagues and proved that they can be trusted with some of the most important tasks. They have not tried to contradict, change or compromise the current systems in place, but instead have given ideas and worked to develop the Division. And when an idea has been dismissed, they have not been deterred, or taken it personally. The trust that I now place in them has been earned over time, and now I hope they can prove that that trust is well placed.

Examinations & Wiki Pages

During the last duty shift, the first Ensign examinations based upon the new training documentation were held. The examinations were challenging for those who took them, but they tested the most essential information that an Ensign needs to know. The process worked well for the Ensign examination, and both the Commanders agreed that it was a suitable way to test new officers.

The examination questions were quite challenging, testing an officers knowledge of systems and roles on a TSN vessel. Although we were not expecting the candidate to answer every question perfectly, we were expecting most questions to be answered to a satisfactory level. After each examination, we discussed the answers given and made a decision based upon how well they had answered, as well as what we had seen of that officer.

With the success of the first examinations, there will be time scheduled to make the examinations more regular, perhaps held fortnightly, or on a monthly basis. It should be possible to examine three to four officers during a duty shift, perhaps more.

Now that the basic training documents have been completed and examinations process established, the next level of documents and examinations can be addressed. These will be the Lieutenant-Junior and Lieutenant level examinations. At this level, officers are expected to begin developing expertise in certain roles. The new Advanced training documents will focus on tactical considerations and more advanced thinking behind the roles; for example, the Helm training document will include details on manoeuvring the ship and tactical choices; the Communications training document will include detail on organising and directing allies.

Testing and training for command roles will differ slightly. At this level, there will be a greater focus on practical experience and coaching from senior officer, looking at more advanced tactical considerations. Examinations will feature less, and observations of the officer will be the main method of assessing their suitability.

I have continued work on the TSN RP Community wiki pages, updating them and organising them clearly. They are almost completely up to date now, however I will continue to manage and alter them to keep them maintained. On the TSN RP Community page, there is a brief paragraph about the RP Community and then four main sections; Getting Started - for new people joining the RP Community; The TSN Universe - giving background detail of characters, systems and technologies; Officers of the TSN - created to provide all the information a TSN officer will need; and finally The TSN Library - collecting together all the documents, handbooks and other written reference material.

Each of these sections are divided in to sub-sections with extensive information for members of the RP Community. They have been carefully presented and organised to make them easy to navigate and find all the necessary information. There are some bits just to finish up, however the majority of the pages are complete. It is my hope that all members will use the pages extensively for reference and that members will begin suggesting additional information to include, or submitting additional reference documents. To ensure consistency in format and presentation, and that information is appropriately organised, the Command Staff will review and format all new submissions for the wiki, before they are added, or authorisation given to them member to allow them to add files and information.

New Recruits, Communications and Fleet Orders

TSN Command reported that a number of new recruits would be shipped out to Promethean to boost our numbers in this system. Now that there is an established core of professional officer, they felt that we could handle the training of larger numbers of new recruits. Last duty shift, I assigned Commander Feltes and Commander Corwin to train the new cadets. With 12 new recruits arriving on a shuttle, there were two full crews to man the academy ships. Both Commanders went through all the basics about how we run things on station with all the new cadets. Although most cadets come with some training, it is our job to show them how a real TSN crew operates. Many have little awareness of the Combat Orders, or procedures aboard station, and this final stage of their training is to ensure that they learn these.

Whilst the Commanders trained the cadets, I took the full officers and conducted simulations to further refine the Fleet Orders and operations. The simulations went well. Lt. Jr. Alice, who I assigned to command the Osiris, quickly picked up the Fleet Orders, and was able to closely coordinate with the Falcon. Due to the Lt. Jr.s performance, I decided to promote her at the end of the evening to full Lt.

The final simulations of the evening saw four ships, the Falcon, Pegasus, Gallant and Osiris, fighting in the same sector. To make things more manageable, we paired off; the Falcon and the Osiris working together, and the Pegasus working with the Gallant. Although the Pegasus and the Gallent were unable to coordinate as closely due to the crews being training crews, they were able to successfully work together in an area of the sector to defend it from enemy fleets. The Falcon and the Osiris, with more experienced crews, worked in close coordination with one another to eliminate a number of fleets.

The simulations were yet another test of the Fleet Orders. Before the simulation, a way to communicate with all the bridges had to be established (until now, we have only had two ships working in a sector). This was discussed with the senior officers and the links between the ships were decided upon. All the captains had direct links to one another on a private comms channel. Each captain also had individual links to each bridge for a more open broadcast. The system worked well as ships could communicate actions clearly on the open broadcast. Captains also had the private channels to discuss finer tactics or issues without having to broadcast openly to the bridge.

With such an influx of new recruits, the Ensign examination documents are being finalised and made ready for the next duty shift. I have started to set up the examination suites aboard Promethean Command, and have been uploading the examination software for the practical simulations. The examinations themselves will include general questions about each role aboard a TSN vessel. There will also be more difficult questions specific to their own area of expertise. For certain roles, the cadet will also have to conduct a practical examination to test their skills.

There are a few cadets who are eligable to take the examination. The requirements are that the cadet must have served in all roles aboard a TSN vessel (whilst on duty), ahave a more indepth knowledge about their specialist area, know procedures on station during duty shifts, have a working knowledge of the Combat Order, and have served on at least 2 -3 duty shifts.  I think I may allow them to put themselves forward for the examination if they feel they are ready, however to pass the examination, the cadet will have to answer the questions, demonstating very secure knowledge. Only those that answer the questions in a satisfactoy way will be promoted to a full officer. It may result in a few failing to meet the mark, but it will also result in the Light Division having the best officers.

I have continued to work on the Sandbox mission script, but rather than focus on adding to the mission packs, I have started to tailor it to meet the needs of the RP Community. I have devised a way to significantly increase the number of GM keys that I can set, and have started working on creating more functions for a GM console. Once completed, I want to run missions using the GM console for the RP community, with missions starting at Promethean Command. With the addition of a number of new systems and a waypoint sector, I have managed to link Promethean system to Atlantis system. I want to add a number of other systems that are not under TSN control; "badlands" which have dangerous anomolies and phenomena (blackholes that bounce around for example); and areas which are "contested" where it is likely that the ship will meet enemies, or where nagotiation missions might take place. I think though, that I will develop the Sandbox script for more for GMs. I'll still write in the odd mission for crews to play without a GM, but I feel that it has much more scope and potential as a GM controlled script.

Updating the Wiki Pages

Recently, I started work to overhaul the TSN RP Wiki pages. The original pages had a lot of information on them and it was mentioned by a member or two in the community that they were a little overwhelming for new players. I have therefore started making them easier to navigate for new and current members.

I have created a new "homepage" that can be reached from the main Artemis wiki page. The information includes a little about the community, then several links to other pages; Getting Started, The TSN Universe, Officers of the TSN and The TSN Library. Each of these is going to be constructed to make it easier to find out about the RP and find all the relevant documents that any member might need.

The Getting Started pages have recently been completed and details all the most basic and most useful information for new people joining the community. There is a little about how to join up, how the session runs and some information about the rank system.

The TSN Universe pages are going to be updated eventually. They will have similar background information and layout to the current TSN Universe pages. All I will do with them is just give a quick revamp and update any information.

Officers of the TSN pages are going to be specifically designed for current members of all ranks. They will include detailed information about training and promotions, extra background information on the Division, and anything else a full officer might need to know. 

The TSN Library is going to be a single page with links to all the documents created by the RP Community. Included here will be handbooks, training documents, and any other reference material.

In the meantime, I will continue to work on the other training documents that I have been creating. My aim is to complete the Communications Basic Training document first giving the RP Community a complete set of training documents for Ensign level. I'll then move on to the Duty Officer document. Examination documents are currently being put together by other senior officers of the RP. They need to be reviewed, but examinations should soon be back up and running, along with a form of training programme (the basic training documents forming the base of such a programme).