The USS Malinche is a Proud Member of
http://www.bhsimms.com

The Malinche Simulation Guide

(Still, and always, under construction)

What is a PBeM or Simulation?

  • The definition of a PBeM or Simulation as it pertains to this group
    • Simple definition: A group of people who gather over electronic mail to collaborate on a storyline -- in this case residing in the Star Trek Universe. The intent is to create a flowing story full of action, suspense, intrigue, and interpersonal intereaction with people in a guise other than their own selves.
    • We are essentially a fan club that has decided to create its own 'show'. Each of the PCs is a 'main character' in that show, regardless of rank.
  • The role of the simmer at the Malinche
    • You are where the main actions reside. Without you, the GM would simply be a rambling fool with a email account. You are the heart and soul of this simm. I'm simply the facilitator.
  • The role of the GM at the Malinche
    • The GM acts as a "Q", as it were, creating the environment around which the universe of the Simm resides. He/she ultimately decides where the simm is going to go.

Back to the top

What are the rules for posting?

  • Posting Minimums
    • Each member of the Malinche is expected to submit at least two significant posts per week, significant being determined as being more than just a one-paragraph post intended to keep the character alive. A post should either tell a sub-plot story, or add significantly enough to the main storyline. Characters are expected to remain up-to-date with all posts... if you miss one, you can choose to check the archives at eGroups.com.
    • Also, be sure to always place a [Malinche] at the beginning of each IC post... there are a number of ships using the list... this allows us to keep track of our own. If multiple posts are a problem for you, simply set your list options at eGroups.com to "Digest Mode".
  • The Four Types of Posts
    • Joint Posts
      • These will typically be run as sub-plots, although they can correspond to a main storyline. To be considered a joint post, there must be at least two people working on the post off-list. One person then sends it to the list as a whole. Examples of this sort of post abound on most AES ships, although we chose to stray from that sort of limiting post style. These will count as one 'single' post for all parties involved. It may count as more than one depending on the case.
    • Continuous Runs
      • This will most likely be the most common post seen on the list. These tend to run shorter, and depend on others to read them and respond to them, rather than being (as in the Joint Post) a singular story with a beginning, middle, and end. These will most often contain sudden shifts/twists in plot, emergency situations, that sort of thing. Keep on top of these posts, and if you need a specific person to respond to it, mark an OOC note at the end of it with their name.
    • Personal Logs
      • Just like it says, this is a post that encompasses a personal log made by your character. This can be written independant of a storyline post, or be contained within one. We encourage these so that players express their character's emotional reactions to situations outside of an interactive setting. Personal logs can count as up to one of your weekly posts.
    • NPC Posts
      • Although these will not always count towards your personal post minimum, there is room on the ship for simming as another character that you've created... an established NPC on the ship. You can only do this if said NPC has already been submitted to the CO beforehand, and the NPC _has_ to be owned by you. These cannot be used like a regular character, in that a normal PC can have and effect on the outcome of a mission or major problem, whereas an NPC (otherwise known in movie and TV terms as an 'extra' or 'walk-on') can have no such effect. This is simply to add flavor to the run of the PBeM. This sort of post will more often than not be used by the CO or XO of the ship.
  • When you fail to post:
    • Sometimes, people decide to leave a simm, or tragedy strikes, or they simply lose interest. That's all right... let us know, don't just drop out. As well, sometimes someone has to go on vacation, or take time off the internet to deal with tests and studies. If you let us know about any of these, we'll not have a problem with it. However, sometimes a character simply stops posting for a while. The reasons may vary... but for some reason the GM isn't told. If you fail to post the minimum for two weeks, you will recieve a private, emailed warning, and a question as to the reason why. If, within a week, you do not answer, your character will be moved to MIA status in the obituary, with your position held on reserve. After two weeks, your position will be reopened to the general public, and your MIA status will become permanent. In other words, you have four weeks to tell us why you've been gone -- not a bad deal.
    • We do realize that sometimes things just go haywire. This is _why_ we have the obituary section of the webpage... if you come back after a long time, and explain that unavoidable circumstances kept you from coming back... and you'll be reinstated in some fashion. We will _never_ kill of a PC without your expressed, written consent. Never.

Back to the top

What are the rules for IC play?

  • PC interaction
    • Very simple. Just remember that the simm only works if we all work together, and that if one of us isn't happy, the entire simm suffers. With this in mind, don't monopolize the action... don't assume you can win every fight... and don't try to be Superman all of the time. Sometimes, it's okay to let your character get wounded in battle. Sometimes, it's okay to fail at a mission.
    • Remember that behind every non-human, electronic character there is a living, breathing, emotional human being. We're all creative souls here, and sometimes things may go haywire. Just remember that you're hurting a real person if you attack them.
  • More to come

Back to the top

What are the rules for OOC interaction?

  • Copyright issues
    • Be careful when introducing plotlines, ideas, characters, NPCs, you name it, to the list. We need to be extremely conscious of the fact that we are playing in a system that is protected by copyright. Our play here first and foremost is out of a love for the concept and works of Gene Roddenbury and Paramount Studios. Respect them.
  • OOC Postings
    • OOC chatter needs to remain on the OOC list... the [STSE-RPG] list is for IC communication only. The only allowance for OOC speech on the [STSE-RPG] list is short quips before or after a post to indicate who needs to go next.
    • NEVER post spam to either list. Do so, and you'll either be penalized severely or kicked out for it... we're that serious.

Back to the top

What are the basic rules and regulations for play on the Malinche?

  • The point of rules
    • Let's face it... you put a bunch of people in a room, chaos will ensue. Rules simply work to place a groundwork on that chaos. Keeping them helps us all stay sane.
  • Use of other Player's characters
    • Unlike a lot of PBeMs out there, we are not as stringent on the idea of using another person's character in a post. When you use the continuous run format that we do here at the Malinche, it sometimes would be ludicrous to have to wait for a person to respond to every question asked them... especially when the answer would be a simple "no."
    • Because of this, we think it necessary to allow minimal use of another person's PC, but only under a certain base of rules:
      • Try not to have them speak more than 20 words.
      • Never do something that would be obviously out of character for them.
      • Be certain that you know how they would react.
      • Be willing to rewrite the post if the PC's player feels you screwed up.
      • Never do anything that would seriously alter, traumatize, or otherwise mangle that character.
      • Again, keep it to a minimum... simple comments are best.
  • NPCs and their uses
    • NPCs are those rarely-seen extras or walk-ons that are used to create depth in a story. Sometimes you can't depend on just PCs to do a job with you. There are never going to be as many nurse PCs as will be needed in a crisis situation. As well, you always need those crewmen-expendables to tag along with you on uncharted planets.
    • NPCs can be used within a post for a PC to interact with.
    • Player-created NPCs not found on the website are pretty much free-for-alls which can be used in any way (within reason) by any player.
    • Player-created NPCs that have been submitted to the webpage cannot be killed, and at the request of the owner may not be available for common use.
    • NPCs as a whole do not need to be approved unless their background is highly irregular, or if the player wishes to make an NPC post.
  • The language/content of this PBeM
    • I have decided to keep this PBeM at a PG or PG-13 level. This means that I would rather not see language that you would not find on a typical ST:TNG episode. Words such as "damn," "hell," "crap," whatever are fine... but don't go beyond that. Remember, a PG-13 movie becomes R if the f-word is used more than three times. Keep the same thing in mind here.
    • No sex. Sorry, kiddos, if that's what you're looking for, but I'm not interested in reading it, and neither are the millions of parents out there who don't want their children reading it. For their sake, we'd like to keep it off of here. Again, I'd say keep it to PG-13 level, but considering what is acceptible in that rating these days, try to keep personal, romantic relationship messages to "would have had a PG rating if he hadn't said 'damn' in the last scene" level.
  • Personal or sexual harrasment
    • You know what both are, I won't bother to define them.
    • Sexual harrassment will not be tolerated, and in most cases will be dealt with harshly, up to and/or including demotion or removal from the simm.
    • Verbal harrassment (flames, et al.) will likewise not be tolerated, especially on the public channels. If a situation of this sort cannot sort itself out, someone will have to leave the simm, simple and plain. We're here to have fun, not to tear each other down.
  • In-game (OOC and IC) conflicts
    • Sometimes things won't work out right, and players will get upset. This is understandable, and expected. You put too many people together, and someone will get angry. However, try to keep conflicts to a minimum. If you can't sort it out yourselves, contact the CO, XO, and offending party with your complaint. We will attempt to deal with the problem there.
  • The introductions of new technology
    • This is a hard one, but for the most part never introduce technology that isn't accepted as 'standard issue' in ST canon. If you have a new gadget, great! Submit it to the CO and XO for approval. They will then send it to the upper brass, with comments, who will give the thumbs up or down on the project.
    • Never introduce new tech into a post without the consent of the XO and CO.
  • If you need to take a vacation
    • Just let us know, so we can make the needed adjustments. We won't say "no" unless it's completely silly. This just keeps us on top of things, so we don't assume you've dropped out.
  • If you must quit
    • We realize that this will happen. For the ease of everyone in the simm, please tell us if you plan to quit. As well, if you do so plan, please let us know how you wish your character to leave, or have a departing message approved. If you wish it so, we will aid you in leaving. You will _never_ be hounded by the command for your choice to leave, although we will be sad to see you go.
  • Romantic relationships on-ship
    • See the content rules for guidelines
    • We as a Organization and as a PBeM see nothing wrong with creating such relationships... in fact, in some cases we suggest them. However, we ask that you not make it your focus as a player (we've seen some characters do nothing but write posts about their current love affair). There is simming to do, after all, and chat rooms for that other type of thing. =)
    • Always remember that this simm is open to teen-agers. Some of those folks will have parents behind them. NEITHER should have reason to be offended at the nature of this simm.

Back to the top

What are the rules about characters?

  • Basic rules to follow when creating and playing your character
    • BE REASONABLE -- you can't be a superhero all of the time.
    • Be flexible -- sometimes what you want to do just won't cut it.
    • Be competitive -- don't just wait for other people to do stuff for you... do it for them.
    • Be assistive -- other folks may need your help... help them.
    • Be aware -- sometimes it wouldn't be proper for your character to jump into a close situation. Use your better judgement.
    • Be reasonable again -- don't always be the first to figure out a solution to every problem. Sometimes someone else should get the glory.
    • Be smart -- remember your station on the ship, as well as your rank.
  • A healthy crew relies on teamwork
    • We are not "Peter Bates and the Members of his Starship Simm".
    • We are not "The Old Cast vs. The New Cast"
    • We are not "Enlisted Crew vs. Civilains"
    • We are a team, regardless of rank, position, length in the simm, or whatever. We are "The Cast of the Malinche" and need to work that way. If all of us participate in this simm, life will that much better on-board.
  • Our policy on killing main characters
    • On the most part, we don't kill main characters. It's bad for morale, makes for bad storytelling, and doesn't work well in this genre. As such, avoid killing PCs (and even some NPCs) at any cost.
    • We will never kill off a PC whose player left the ship unless s/he expressly requests it.
  • If you must request a transfer
    • Don't just leave... let us know so that we can hook up with the proper channels, and help you keep the ICness of your character intact.
  • Interacting with NPCs, or playing NPCs
  • Rules for Character Creation
    • Some races simply are not feasible on a Federation Station, as we are either at war with them, or they have not joined the Federation yet. Examples of this are:
      • Ferengi, Cardassians, Romulans, Breen, Vorta, or Jem-Hedar as Commissioned Officers (They _may_ be civilian characters -- And Ferengi and Cardassians _may_ be accepted as Ensigns or Cadets, ONLY)
      • 'Impossible' or 'implausible' half-breeds from Dominion races (which currently would only be 5 years old): No mixing Vorta (clones can't procreate), Jem-Hedar, Changelings (who can't procreate with solids anyhow), Breen (who wouldn't taint themselves anyhow), etc.
      • Half-breeds of just about any other humanoid race are acceptible, given one half is from a Federation-allied race.
      • Recovered Borg drones are a _rare_ occurance, and although they are not disallowed on this ship, you had better do a really good job of convincing me that you deserve and can run the character well.
      • Dittoes go for Artificial Intelligences, or Characters from the "Dark Mirror" world.
      • Races that cross over from another series or genre are not acceptible. (No Talons, Wookies, Harpies, etc. -- Reasonable facsimilies may be acceptible, but they have to be far enough removed from the other genre that I won't recognise it as a copyright infringement.)
      • No supernatural beings. Period.
      • Q and other omnipotent charatcers are also not acceptible, even as 'half-breeds' -- it puts too much power in the hands of one character.
      • Do note that although I will accept many 'odd' characters, half-breeds, illogical assignments, etc., I do reserve all rights to reject a character outright simiply based on the fact that I have 1) too many characters of that generic type, or 2) I feel that that character does nothing to improve the simm.
    • Creating your own race
      • There are doubtless many different races out there in both the federation, and outside of it. Not all are humanoid, although it appears that a vast majority of them are. Why confine yourself to humans, or the rest of the canon races of Trek? You may have a racial idea that would work well within our system. As well... the longer this ship is out exploring the galaxy, the more likely we are to enter a situation for the insertion of your character. As long as the race idea is well thought out, it is likely to be approved.
      • If this happens to be the case, feel free to apply for a character within the race that you specify. However, there are a few extra things that I require of you on your Application:
        • Basic racial information must be added on TOP of your own descriptions in the Physical Description.
        • A short history of your race needs to be added to your Character's History.
      • Multiple characters on one ship
        • Simply for the purpose of keeping things in some semblance of order, I will personally not accept request for multiple characters on this ship. One character per player only.

Back to the top -- Back to the Character Application Page

What responsibilities are there for my department?

  • Commanding Officer OOC responsibilities
    • Help those who are having trouble posting
    • Resolve any problems that people may have between players
    • Create missions for the players to follow
    • Be a liaison from your crew to the upper brass of Star Fleet Intel and ASQC
    • Handle Promotions (up to the rank of Commander), Demotions, Reprimands and Transfers.
    • Motivate People to post.
    • Recruit people for the ship.
    • Report to the upper brass about the situation and current storyline of the PBeM
  • Executive Officer OOC responsibilities
    • To keep up-to-date records of the posting levels of all crewmen.
    • Notify the CO if any person has failed to post the minimum amount for more than two weeks.
    • Assist in disciplinary hearings should a member of the crew be a problem to ensure fair proceedings.
    • Take charge in crew performance evaluations (taken once every 4 months, IRL) -- suggest promotions, awards, etc.
    • Officially allowed to take charge of a vessel temporarily should the CO be unexplainably missing for more than 2 weeks.
    • The IC purpose of the XO is to assist the CO in ship's day to day operations.
  • Second Officer OOC responsibilities
    • To keep a record of all posts, to be put into logs for the webpage at a later date. Will require HTML knowledge. (Note, this is not absolutely necessary. If you have no HTML knowledge or website experience, something can be arranged.)
    • To gather and keep track of player birthdates, special events, emaill addresses, contact information (via ICQ, AOL IM, or whatever).
    • To prepare monthly "Ship's Status reports" for the STSE Newsletter. This includes:
      • Basic Roster (Character names, ranks, and positions only)
      • Birthdays/Special Events in the crew for said month.
      • A basic rundown of the current mission, in one-paragraph form
      • A short synopsis of the 'story so far', in two-paragraph form
  • Marine C.O. OOC responsibilities
    • Recruit Marines.
    • Recruit more Marines.
    • If possible, create a separate homepage for our marine detatchment.
  • Departments IC responsibilities
    • Command
      • Commanding Officer
        • The CO is normally a command rank character. He or she is the titular head of the ship, answerable to the Admiral and his/her executive officers for the proper execution of Starfleet Intelligence rules and orders for the entire crew. The CO sets the tone and demeanor of play on the mission. The permanent CO has the power to promote crew to ranks below the first officer's, to assign and/or change all positions on the ship including the appointment of second officer, except for the CO and XO on his/her own authority.
        • The CO has the responsibility to keep the ship organized and the crew motivated and trained. He/she should post frequently enough to keep the action moving. He or she has primary responsibility for setting up a good RPG environment and cooperating with the GM to achieve this. It is the CO's responsibility to provide a defined amount of information to the administration for overall club continuity. It is specifically allowed for the CO to distribute those duties to volunteering crew members at his discretion.
        • Dramatically, the CO is responsible for choosing from among the various options that are presented, the one which best contributes to the successful completion of the mission and provide insight into the "big picture" of what the ship is doing.


          It is considered poor RP to write decisions on behalf of the CO without prior consultation - it usually is the only involvement into the mission the CO character can achieve without interfering with a player's area of responsibility.

      • Executive Officer
        • The position of First Officer is to act as the deputy commander of the ship and to be prepared at any time to take over the duties of the CO if necessary. He/she is second in command and will normally be one rank beneath that of the CO, for officers new to the position or commodores on ship the difference might be two ranks. The responsibilities include making sure that the crew is ready at all times to carry out the mission.
        • He or she is primarily responsible for making sure the CO's orders are being carried out. The XO is also responsible for making sure that the Captain is aware of all of the various options that are available for successfully completing the mission.
        • The XO has primary responsibility for the safety of the CO and will normally command the primary away team. The XO is also responsible for the development of the officer's careers in Starfleet Intelligence (as discussed below). XOs may have a specialty and devote extra attention to that area of the mission, especially on smaller ships with no dedicated officer for this field of expertise. The XO is the ship's personnel officer and all new recruits and transfers should report to the XO (dramatically, the Captain is too busy).
      • Second in Command
        • Takes over the responsibilities of the XO, should the XO become incapacitated or killed in the line of duty.
        • If both the CO and XO are gone, the Second in Command takes over the responsibilities of both.
    • Chief of Security/Tactical
      • The Tactical Officer or Chief Security Officer (TAC/CSO) is primarily responsible for the security of the ship and its crew. He or she handles the ship's weapons and shields. Also this officer is responsible for most sub-space communication. In addition, dramatically, this position is responsible for taking a hard-line, short-sighted, even a touch paranoid approach to problems. He or she presents this view to the Captain who must decide to what degree to follow it.
    • Chief of Counseling
      • The position of counselor (CNS) handles the ambassadorial functions including dealing with alien races and trying to make peace. Dramatically, the officer offers an optimistic, starry-eyed approach to problems to contrast with the TAC/CSO. CNS is secondarily in charge of general communications and - if present- civilians aboard. This officer has a major responsibility for the morale of the crew and can report problems to the XO. This person should assist in getting new recruits settled into the routine of the play. May also back up the CMO and one player may hold both parts if necessary.
    • Chief of Operations
      • His or her job is to allocate the ship's resources in an efficient manner so as to meet the demands of the mission. The OPS handles the ship's sensors and thus functions as the CO's eyes and ears. This person has primary responsibility for the ship's library and computers.
      • They act as the back up for the Science Officer or Chief Engineering Officer. The officer can supply information from the computer on essentially any subject including alien races, unusual phenomena, etc.
    • Chief of Medical
      • The ship's doctor (CMO) handles all medical matters, plagues and other medical emergencies as well as exotic injuries are common on ships with a CMO. The CMO is secondarily responsible for the same work as the counselor and may serve in both capacities. The CMO handles investigation into biological matters and may develop biological solutions to problems.
    • Chief of Engineering
      • The Chief Engineering Officer (CEO) is responsible for the repair, maintenance and proper functioning of the ship's physical components including engine, shields, life-support, transporters, replicators, holodecks, and shuttles. This position has secondary responsibility for energy and resource allocation which is normally handled by OPS. The CEO handles investigations of problems of a mechanical and technical nature. Dramatically, the CEO handles the invention of special gadgets needed for the story and is especially involved with helping whole civilizations, planets, space stations, etc. with large scale problems.
    • Chief of Science
      • The Science Officer (CSciO) is responsible for investigations into all manner of scientific problems, both mechanical and biological. This officer also acts as a back-up for both the CMO and the CEO and either of those positions may also act as CSciO. The Science Officer acts dramatically as an advisor to the Captain on technical matters. The CSciO is an optional position for most ship classes, only explorers are required to have a PC CSciO.

Back to the top

How do I get promoted?

  • Specifics to be announced
    • Suffice it to say, we will look over your performance every four months. For now, promotions will be given on the express suggestion of the XO. Exact reasons will be given later, as we're given examples of what makes one promotable.
  • A word of advice...
    • Never ask for a promotion... in all likelihood, you're shooting yourself in the foot by bugging the GM or XO about it. Let it come naturally -- if you deserve it, trust me, you'll get it.

Back to the top

Terms and Acronyms to learn

  • OOC -- Out Of Character communication
  • NRPG -- "Non-roleplaying game" (meaning an OCC communication in an IC post)
  • RPG -- "RolePlaying Game" (used after posting an NRPG in an IC post)
  • BIC -- "Back In Character" (also used after posting an NRPG in an IC post)
  • IC -- In Character communication
  • IRL -- "In Real Life"
  • PC -- Player Character
  • NPC -- Non-Player Character
  • GM -- Game Master, in this case the Commanding Officer
  • *JP* -- is used to signify that a post is a "joint" post.
  • *CR* -- is used to signify that a post is a "continuous run" post.
  • *PL* -- is used to signify that a post is a "personal log" post.
  • *NPC* -- is used to signify that a post is an "NPC" post.
  • CO -- Commanding Officer
  • XO -- Executive Officer
  • CMO -- Commanding Medical Officer
  • CEO - Commanding Enlisted Officer
  • Any others? Write me at PBates@javanet.com.

Back to the top

[ main ]|[ navigation ]|[ roster ]|[ ranks ]|[ uniforms ]|[ episodes and comments ]
[ specifications ]|[ application ]|[ story ]|[ simm guide ]|[ roleplay logs ]|[ about the GM ]

webpage design and original layout courtesy of Joshua D. Smith, (c) 2000
used by permission