Expectations of all aboard either DS11 or the Nogura are very high. All are expected to follow the rules and regulations of DS11, the Nogura and their home Fleet at all times. By joining the either of these crews you affirm that you will write in a proper and adequate manner. Members who choose to make ultra short posts, post very infrequently, or post posts with overly sexual content will be removed immediately, and by continuing, you agree to this. It should be noted that whilst neither DS11 or the Nogura is set in a time of war there may be cases of extreme violence written and applicants should be aware of this. As such, it is the judgement of the command staff of both simulations that both DS11 and the Nogura will accept no player under the age of 16. There will be violent content from time to time and all players should be prepared for this. Any players found to be under the age of 16 will be immediately removed without question and banned from the relevant sim. By agreeing to these terms, you are also saying that you are at least 16.

==The Ten Commandments==

All CO’s desire their crew to have fun when on their simm and the staff here are no different. Follow these 10 rules for a stress free simming career!

  1. Creativity is key, creative entries give life to your character.
  2. Pay attention to detail. Keep up with what others write in their entries – it just might affect your character!
  3. Be flexible because when you’re writing with a group of people, anything can happen.
  4. Remember the Golden Rule – treat others in your entries the way you want to be treated in theirs – with respect.
  5. Post, post, post. You never write too many entries.
  6. Words are powerful, use them carefully, and write so others understand what you’re doing.
  7. Communicate; talk out of character (OOC) with other crew members via email, instant messengers and the OOC threads. It builds cohesion and can add to creativity.
  8. Stay involved, you can’t always be the center of attention… but that doesn’t mean your character can’t do anything. It is a big ship.
  9. Develop your character. Make sure you use traits about your character in your entries. Don’t write a BIO and then play your character completely different.
  10. Be consistent, that way others know what to expect of you.

==Disciplinary Procedures Policy==

Instant Player Removal

The Command Staff may, at any time, remove any player(s) from the simulation with immediate effect, if they pose a risk to the safe simming environment provided. Any person removed under this rule will be banned from joining or being associated with this simulation permanently.

Strike Policy

In times when the safe simming environment is not at risk but a player is deemed to have not followed the rules, a strike against their name which in turn will limit awards, promotions or positional advancement within the simulation for a period of time.

A strike instantly places a crewmember on Probation for a period of 60 days after which time the strike is automatically removed and probation ends. For each additional strike awarded whilst on probation, an additional 30 days will be added on to the original 60 days. If an additional strike is awarded, this automatically resets the 60 day period of probation for the first strike, so for example, at the time of receiving a second strike, the player will be put on probation for 90 days.

A player can only have a total of three strikes (and thus, 120 days of probation) at any one time. If the player reaches a point where three strikes is not enough, their removal is automatically sanctioned. Player removal on these disciplinary grounds is to be carried out by the officer in command at the time, be it the CO (or should the CO be on LOA/ELOA) or the XO. In the event that both the CO or the XO are unavailable, player removal is to be discussed by the player currently in command and the Task Force Commanding Officer. Further fall out from this will be discussed upon the return of the CO or XO – whoever returns first.

Any player who is removed under the strike policy will be banned from applying or being accepted to the simulation for a period of 180 days (roughly six months), which is equal to the time required for the three strikes to be automatically removed and an extra 60 day cooling off period.

Strikes will be rewarded for the following reasons:

  • Failure to follow the sim rules, as agreed upon acceptance to the sim.
  • Failure to follow the Bravo Fleet Rules and thus, bringing the sim into disrepute.
  • Non-compliance with official DS11/Nogura Policy Documents (Posting Policy, NPC Usage Policy, LOA Policy)
  • Making alterations to the mission that negatively impacts upon the story of the sim without first discussing such impacts with the command staff.
  • Violating the Sim Age Restriction of 16 or older. Exceptions may be granted by the command staff only, on a case by case basis.
  • Additional, exceptional reasons, yet to be determined, as discussed by the command staff.

==LNPC/NPC Creation and Usage Policy==

The Command Staff actively encourages players to explore their simming world and develop their characters in the greatest depth possible and as such, this guideline on PNPCs and NPCs should hopefully go some way to helping players to develop environments, storylines and characters.

At present, the rule of the fleet is that each player may only have one active ‘player’ character on each sim and that is something which the Command Staff are very much in favour of. However, we believe that players should have the freedom to create a number of NPCs and PNPCs in order to make the game richer and more vibrant.

On a ships and stations such as these (which have crews of between 1000 and 1500 at any one given time) it is important to make sure that there are reference points throughout the game for people to use. For reference, the following abbreviations are used throughout this document:

  • PC – Play character
  • PNPC – Linked Non-Player Character
  • NPC – Non-Player Character

That is why the following PC/LNPC/NPC guidelines are in effect:

  • Players will be permitted 1 main character. This will be your highest ranking character and will be the one you work with most often.
  • Players will be permitted 2 protected Linked NPCs. These are characters that you hope to develop and advance beyond just someone whose name is occasionally mentioned. There will be a desire to expand these characters beyond the usual realms of an NPC and these characters may ONLY be used by the creator. Anyone wishing to engage with a PNPC that is not of their own creation should do so via a JP. These characters should have full, complete biographies including character pictures.
  • These PNPCs and will be interchangeable (just in case you don’t like them) but this must be done with the approval of the Commanding Officer and the two creators involved.
  • In addition, players will be permitted to create 3 additional NPC characters for their department. These are characters who appear in the stories and may occasionally have dialogue but are largely there as “window dressing”. They can be used by any player at any time. A full biography is not required, but is preferred.
  • Any position occupied by an PNPC or NPC must remain vacant at the same time to allow for applications from outside the crew.
  • No PNPC or NPC will hold a Department Head or senior officer position unless permission has been granted by the CO. These positions are left open to encourage applications.

Players are requested to pay attention to ranking structures and look to bring in PNPC/NPC’s of differing ranks, and in differing departments. No player will be permitted an PNPC/NPC character who outranks their main player character unless they have been requested by the CO to play a mission-specific NPC.

The player’s main character will be the priority. It will be frowned upon if players start posting more with PNPC/NPC characters than their own.

Submission of NPCs

All players are quite within their rights to create their own NPCs in the game but must ensure that they send information on the NPC to the Executive Officer of the relevant simulation so that s/he is able to link NPCs to their player and ensure that they are not misused. The CO/XO also reserves the right to alter the rank of any NPC after discussion with the user.

==LOA Policy==

We acknowledge that upon joining our sims, all members give up a portion of their free time to join us and share in our story telling.

It is entirely possible that, during your time with us, you will be distracted by real world events such as illness, lack of internet or computer access or other reasons. It is your responsibility to inform the command staff that you will be unable to meet the regular posting requirements by requesting an LOA (Leave of Absence). You can do this one of three ways.

  • Semi-LOA: A Semi-LOA indicates that you have limited access and availability for a portion of your time, but will still be able to check in. Semi-LOA’s are granted for a maximum of 10 days. If the same conditions apply but for a longer period you must apply for a full LOA.
  • LOA: An LOA indicates that you will not have access to the internet, or will be unable to arrange some sort of access to the internet, in order to post and carry out sim related functions. LOA’s can be granted for a maximum of 30 days. They cannot be extended.
  • ELOA: An Extended LOA is required if you will not have access to the internet, or will be unable to arrange some sort of access to the internet, in order to post and carry out sim related functions, for a period longer than 30 days. An ELOA can be granted for a maximum of 60 days and may not be extended beyond that.

Any player that is involved in a situation where they are likely to be absent from the sim for a period of more than 60 days will be asked to consider their position on the sim and may be asked to resign. This is to ensure that posts are not occupied when new members in a position to post could be active and helping the sim to progress. There are, of course, exceptions that may be made, in discussion with the CO and XO. These are handled on a case by case basis.

==Posting Continuity Style Guide==

With the recent influx of new members to the sim, it has become essential to consider the issue of continuity in writing and formatting of posts. It is too easy for one person to write or style a post one way and for another to do it a different way. This make the posts look messy, especially if they are joint posts with both doing things differently.

As such, we have created this page, the “Posting Continuity Style Guide”. I expect everyone to follow it and to start formatting their posts as needed.

Time Stamps and Locations

The one of the things people tend to write in their posts are timestamps and locations. This is not needed as the post form allows you to fill in the timeline of the post and the main location where it takes place. However, from time to time, characters may be required to move locations, or may be in different locations before meeting up somewhere. Please don’t be afraid to use timestamps or locations to move on to different parts of the story. Just ensure you use squared brackets at either end of the tag.

Characters Thoughts

In posts, it is sometimes difficult to distinguish between the thoughts and the actual speech of a character. To combat this, it has been decided that thoughts will be put in italics with single inverted commas. You can achieve this by doing the following: Start off by writing < i > ‘and then writing here whatever the thought is, and ending with’ < / i >. When you do this, it is important that you do not leave any spaces between the arrows.

An example would be:

Gor pondered the woman’s actions for a minute. < i > ‘What if she really did love me?’ < / i >

Would become the following without any spaces:

Drayton pondered the woman’s actions for a minute. ‘What if she really did love me?’

It is important to remember to use the arrows and not squared brackets as the brackets do not affect the formatting in the same way.


It is common in posts that different characters must get into contact with people around the ship and they do this by using their commbadge or ship to ship transmissions. But lots of people just write it as normal dialogue. It is important to distinguish between the two so it is easy to see who is actually present in the place where the post is taking place and who/how the people are interacting. What we want to see is people adding a commbadge to the start of the dialogue that they are using for communications. The commbadge we add is made up of = / \ = with no spaces, which looks like this: =/\= An example of using the commbadge in dialogue would be as follows:

“=/\=Medical teams report to the bridge,” The Captain spoke over the internal comm before switching attention elsewhere. “Ops, give me details on the enemy ship.”

It is a highly effective way of showing what communication is done with characters not in the same location as your own character.

Ship/Starbase Designations and when to use 10 or Ten

This guide is all about ensuring continuity and a common inconsistency we come across is the writing of starship or Starbase designations. We see lots of people writing names as U.S.S. Lexington or USS Lexington. We will write them as USS Lexington, USS Nogura etc. Alternatively, a good way of getting around this, if the wording of your paragraph allows it, you can refer to the ship as the starship Lexington, or the starship Nogura – meaning you don’t have to use USS at all.

A more common problem comes when we are referring to different Starbases and Outposts. I see people write SB375, when if you think about it, you would never hear a character say “when we get to SB375,” they would say “when we get to Starbase Three-Seven-Five.” So, the problem here is to know when to use the abbreviation and when not to. The basic rule is use the abbreviation in prose, but not dialogue. Example:

Commander Azulas had thoroughly enjoyed her time on SB375, but knew her time was coming to an end. The Solaria would be transporting her to the next base on her tour soon. “Thank you, Admiral. Your facility is lovely but I should head back to the Solaria, we’re due to depart for Starbase Seventy-Four in an hour and we have things to prepare.”

As always, there are exceptions to the rule and they mainly come with Deep Space Stations, such as DS10. We often heard the crew of Deep Space Nine refer to the station as DS9, which is fine. So, it is reasonable to refer to it as DS9 or DS10 in speech.

There’s also the issue of when to write the number as digit or words. The simple way of knowing this is as follows: When using the abbreviation, use digits, when writing the long form, write the word, such as: Starbase Three-Seven-Five or SB375.

The same applies to Task Forces. When writing prose, TF47 is acceptable, but in speech, a character would say “Task Force Forty-Seven,” so the rule applies there also.

Other Abbreviations

When writing prose, there is no reason to write abbreviations for words other than those seen above, or for some pieces of technology. Other words should be written in full wherever possible. The exception of course, is in speech. You would be expected to write the word technology in the main prose of your post, but in speech it is very possible your character might refer to it as “tech”.

Ranks should NEVER be abbreviated. Azulas is not a Cmdr, she is a Commander. Data was not a Lt. Cmdr., he was a Lieutenant Commander. Vice Admiral Ross is exactly that, NOT a VAdm. No one is an Ens, a Lt. JG or an Lt, they are Ensigns, junior Lieutenants or Lieutenants. No one is a CPO, they are Chief Petty Officer’s or “Chief” for short. You get the picture.

==Posting Policy==

It has been deemed that standard Posting Policy aboard the simms is that of an absolute minimum of one post per 14 day period, which allows a minimum of only two to three posts a month. Naturally, more is encouraged, but this is the absolute minimum. Personal Logs do NOT count towards this requirement.

In relation to joint posts, it has been decided that a maximum of 72 hours is allowed as waiting time for tags to be answered, before the post is ‘bumped’ as a reminder and a further 24 hours is granted. A JP is bumped by the person waiting for tags to be answered pressing save once again. This sends another reminder that the post has been edited.

A post may be bumped twice before all authors are given permission to write around or edit out the missing tag wherever appropriate in order to continue with the post.

Naturally, all parts of the Posting Policy are suspended for a player upon the receipt of any form of LOA request. Authors involved in a post with a person who requests an LOA may NPC that character, with the players permission, or with the permission of the Co or XO. This is to ensure that posting continues.

Further guidance below also applies to the sim:

  • All mission posts, personal logs and news items must contain and be written in standard British or American English, with correct spelling, grammar and punctuation. It is advised that posts be written offline, using a word editor and spell checking software before being added to the website.
  • All mission posts (solo or joint) should be a minimum of 500 words. Any post not meeting this requirement will be edited by the CO or XO and returned to the ‘Saved’ area and you will be requested to extend it.
  • Posts should have all necessary information filled out – mission titles, location, time line, tags.
  • Tags in a post should be more than one line of dialogue.
  • No player may overwrite, change or edit the work of another player without permission.
  • This policy has been enacted in order to ensure that the sim and its story continues to progress.
  • Any player that does not follow the Posting Policy is liable to receive a strike.