ATR Players Handbook: what no cadet can do without
Bogdan Baliuc
Starting Out in the ATR An Ensign's Handbook
Original by Lawrence S. VanVactor-Lee Modified for use in the atr
1 - Introduction
1.1 - How to Use this FAQ 1.2 - Other Resources
2 - Life at NTC
2.1 - Bio 2.1.1 - Basic Bios 2.1.2 - A Sample Bio - Esau Telek 2.2 -
Posting 2.2.1 - Mailing Lists 2.2.2 - Subject Lines 2.2.3 - Stardates 2.2.4
- Beginning a Post 2.2.5 - NRPGs 2.2.6 - Signing Off 2.3 - Preparing for
Life after NTC 2.3.1 - Shaping the Bio 2.3.2 - Choosing a Position 2.3.3
- What Kind of Ship? 2.3.4 - Reporting to the Lieutenant 2.3.5- Write Well
3 - Commonly Used Jargon
3.1 - Communications Symbols 3.2 - Common Abbreviations 3.3 - Grins
and Giggles
4 - Styleguide
4.1 - Re-active vs. Hyper-active 4.2 - Solitary vs. Inter-active 4.3
- Plot-driven vs. Character-driven
5 - In Closing...
1. INTRODUCTION
Welcome to Starfleet!
This FAQ was originally written by Lawrence VanVactor-Lee, for his Holodeck
students and it has been changed to accommodate all the incoming NTC trainees.
The Head Instructor at NTC is played by "Tatya" Holmes <pers...@poboxes.com>.
It's her job to make sure everything runs smoothly while you, the trainee,
are there at NTC.
Once in her office, the HI will assign you to one of the numerous holodecks
on board NOVA. There your Holodeck Instructor will assist you and answer
any question you may have. If, however, you can't contact your Instructor
or he/she is unable to help you with something, don't hesitate to contact
me.
Your Holodeck Instructor's job is to get you ready for your first post.
This is the best place to make This is the place to make mistakes, ask
a lot of questions, and have fun. (Remember General Order Number Two --
Have fun!!!)
This FAQ is a supplement to the ATR Manual, which you should have received
by now. If you haven't, ask your instructor for one, get one from the newsgroup
or at browse it from our Web site (http://www.interport.net/~tomlee/atr/).
No officer should be without one!
1.1 How to Use this FAQ
The ATR FAQ is designed in order of importance. The most detailed and
practical information is up front and the more theoretical, ponderous material
is tucked safely in the back. When first reading this FAQ, study this
section
and section 2 (Life at NTC) carefully. You might want to scan section 3
(Commonly Used Jargon). Section 4 (Styleguide) is optional and mostly reflects
the musings of the author. You can save that for later.
1.2 Other Resources
There is always the alt.games.atr.rpg newsgroup itself. You should check
that out now if you haven't already.
Take a look at the ATR Web Site (http://www.atr.home.ml.org/) maintained
by Seth Winberg and Jason Lee. There is lots of information there for the
beginning player as well as resources for the veteran player.
There you can find the ATR Manual as well as a lot of other useful information.
Once again, if you don't have the manual, get it NOW!.
The web page also lists information on ships, crew rosters, administration
stuff, and much more! It also has links to stuff of interest to Starfleet
folk.
2 Life at NTC (NOVA Training Center)
NTC is a Starfleet training facility on Starbase NOVA. By now you should
have already posted to the Personnel Office and received approval for your
character, then posted your shuttle ride from Earth to NTC, reported to
the NTC HI, pers...@poboxes.com and been assigned to a Holodeck for instruction.
If you have missed one of these steps, stop reading this and let your instructor
or the NTC HI know right now because something has gone dreadfully wrong.
Done? Good .. wait for a reply and come back later. That's an order, Ensign
..
2.1 Biographical Data
Your bio (biographical data) is your friend. Your character's bio tells
other people what you think your character is like and it is a record of
your career in Starfleet. When your character joins a ship, your bio is
the first thing they will want to see. It's a résumé and
a character sheet all wrapped up in one. Keep your bio handy and update
it periodically.
2.1.1 Basic Bios
No two bios are exactly alike. Like many things in Starfleet, they aren't
regulated. This allows for much creativity on the part of the player (that's
you). Some basic information, however, should be contained in every bio:
character name physical description age education species home planet
current assignment current position
But that would make for a very boring (not to mention lousy) bio. However,
you may add additional information that might include:
traditions beliefs siblings quirks place of birth spouse ambitions children
annoyances parents hobbies service number religion psychological profile
letters of recommendation disciplinary record honors bestowed
Also, you should indicate any limitations on your character that other
writers should know about.
There may be some things that you may want the players to know but not
their characters. We accomplish this by making a Classified Section in
your bio.
A good suggestion, if you are having difficulties, is to look at other
bios. They can sometimes also be found in the newsgroup. Or you can request
them from the HI of NTC.
2.1.2 A Sample Bio - Morak
Here is a bio of one of our officers, Mr. Morak. Comments are throughout
the bio and are italics
********************************************* Personal BioFile *********************************************
Subject : Morak Rank : Lieutenant Commander (You'll be starting at Ensign.
(See the ATR Manual for more on ranks.)) Current Assignment : USS Pulsar
Current Position : First Officer Race : Klingon (You can be whatever race
you want to be. Some races are easier to play than others. I say Klingons
would be best for more experienced players, but you can be a Klingon if
you really want to ) Sex : Male Age : 25 Height : 1.8 m Weight : 125 kg
(Yeah, Starfleet is metric, but you can use feet and pounds if you like
:)) Eyes : Black Hair : Light Brown Skin : Light Brown Home Planet : Kralar,
Klingon colony near Romulan Border Place of birth : K'Hatan Outpost, Kralar
Parents : father -- Kual (deceased) mother -- B'Jan (deceased) Relatives
: None living Education : Klingon Warrior Academy -- 2 yrs -Area of Study-
Security Procedures/Tactical Operations NOVA Training Center -- Graduated
top 20% of Class -Major- Tactical Operations and Security Procedures -Minor-
Field Medical Technician
****************************************************** Service Record
SD 20901 Leaves Klingon Warrior Academy SD 30515 Enters NOVA Training
Center. Studies include : Security Procedures Tactical Operations First
Aid and Field Medicine Introductory Diplomatic Studies Advanced Weapon
Design Shield Modulation Mechanics Self Defense -- Armed and Unarmed Command
Officers Scenarios SD 80228 Graduates NOVA Training Center. Top 20% in
class. SD 80301 Assigned to the USS Pulsar, Katuba Fleet, Funji Sector
SD 80324 Arrives at SB NOVA, Funji Sector. USS Pulsar en route to pick
up crew transfers. Participates in simmulation exercise for crew readiness.
Is placed in command of exercise. SD 80328 Assigned as Cheif Security Officer
(CSO) and Second Officer (2O) aboard USS Pulsar. SD 804XX Promoted to Lieutenant
Junior Grade after completion of first mission. SD 80427 Promoted to Lieutant
Commander and re-assigned as First Officer of USS Pulsar. (Note the use
of StarDates. See section 2.2.3 for more information on StarDates.)
****************************************************** Psychological
Profile Compiled by K'Harenna Counselor, Klingon Warrior Academy
SD 20703.0802 Cadet Morak is having trouble adjusting to his parent's
death. He believes that the K'Hatan Outpost Raid was a government sanctioned
military action. He mentioned leaving the Academy, and I might feel that
this is best, unless he comes to terms with his loss. He believes everybody
to be involved in a conspiracy to remove his family from our society. This
belief is bordering on paranoia. Up until this incident, he looked very
promising for a command position. He is adaptable for the most part. However,
he do es take some things to the extreme. Hopefully he will reconcile his
loss and be able to return to his life. - K'Harenna (Everyone has their
little quirks .. Nobody is perfect! Don't make your character like Superman
in your bio. Not everyone can be the Valedictorian when they graduated
from NTC. Give your character some background and problems they have to
deal with. It doesn't make your character weak. It makes it interesting.)
****************************************************** Letter of Recomendation
SD 80301.0712 Ensign Morak contacted me on his journey to SB NOVA, in
the Funji sector and asked that I write a letter of recommendation. I am
very pleased to hear that he graduated from NOVA Training Center. He is
an excellent, capable person. He is also very loyal, but not to the point
of being blindly obedient. He will question orders he does not agree with,
but if proven that these orders are required, he will execute them to the
best of his ability. He has studied Security Procedures under my tutelage,
here at the K WA. I must say that he ws one of my top students. It is a
shame that he decided to leave our institute after his second year. His
knowledge of self-defense is adequate, but I have not sparred with him
in over four years. He does enjoy learning new techniques. You are gaining
a very competent officer, so use him to hte best of your ability. Qa'pla
Adm K'Gor Kurgos Director of Security, Instructor, Klingon Warrior Academy
(You need some friends in high places, right? Anyway, its always good to
have a bad side as well as a good side. They usually balance each other
out)
********************************************* Personal BioFile *********************************************
In addition to the comments above, you should be aware that there are
some limitations that you should follow in creating your character. These
are not meant to limit you in your play, but to provide game balance (to
keep any one character from overwhelming all others). Experience have taught
us the importance of these limitations.
Special abilities also need to be limited. Psionics, if used, must be
limited by both physical and cultural limitations. Any character who wantonly
reads minds or affects others with psionic powers is subject to severe
disciplinary action. Limitations also need to be placed on the use of cybernetics
and other special powers and abilities. You will find that it is much more
fun to play a character who has to work to overcome problems than it is
to play one who is able to solve things with a simple th ought.
2.2 Posting
Posting is what Starfleet is all about. It's where the characters interact,
the story is formed, and the fun happens. The creative part is up to you.
But there are a few conventions you should be aware of for posting here
at NTC and out in the fleet.
2.2.1 Mailing Lists
Role playing posts, in which the story occurs, should go to the newsgroup
for everyone to read and via e-mail, to each player aboard your ship or
base. It is usually up to the FO (First Officer) aboard whatever ship you're
serving to provide you with a mailing list with the addresses of every
player aboard the ship. This is frequently listed in the Ship's Roster
that you should receive upon coming aboard.
Pay attention to your mailing list and update it as necessary. Mailing
lists change fairly regularly. Often as much as once a week. Probably at
least once a month. Your FO (First Officer) or CO (Commanding Officer)
is responsible for informing you when a change is necessary.
All Role Playing Game (RPG) posts need to be posted to the newsgroup
as well mailed to everyone on your ship. It can be a hassle if you newsreader
won't mail and your mail reader won't post to newsgroups. An e-mail to-news
gateway may help with this. There are several, but not all of them work
for everyone, nor do they all give error messages if they don't work. So,
make sure that, if you use one, your posts are actually appearing on the
newsgroup.
2.2.2 Subject Lines
Okay, this is going to sound like a little thing, but it's actually
pretty important. In fact, subject lines are one of the things we are required
to teach you at NTC and if you do it wrong, your Holodeck instructor will
tell you. So don't do it wrong, okay?
The subject lines of all posts should always begin with your unit. For
now that's NTC. Other Examples are USS PULSAR and SB NOVA. Note that unit
names are always in caps.
If the action takes place in a specific location or plot line, then
the identifier for that should be attached. For example, on the above mentioned
ship, action on an Away Team mission would be posted under the heading,
USS PULSAR:Away Team.
You can add a further title for the post, if you wish, as well. For
example: USS PULSAR: Away Team John gets caught
There is usually a special location for Non-Role-Playing posts and bios.
This thread will typically be created by the Captain or First Officer,
and usually called, for example, USS PULSAR NRPG or USS PULSAR Bio.
So the basic format is: UNIT: Location : Whatever you want to tag the
subject line with.
The specific format guidelines are as follows:
a. General locations are always typed in FULL CAPS. This includes ship
names, Starbases, threads and special locations like NTC and SPACE PLACE.
b. Specific locations or threads which follow the ship name are typed
in Single Caps.
c. Transfers are incidated with arrows, --> For example, SB NOVA
SA ASHE --> USS PULSAR
d. Dashes, slashes, underscores, and other punctuation marks other than
a colon following the unit should be avoided. They only add to the confusion.
e. If a thread appears with an improper format, DO NOT follow-up on
it. Place your responses in the CORRECTED subject line, and let the incorrect
one die. Don't ignore the post, however. It is still valid.
Some examples of good subject lines:
NTC Holodeck 11: Morak plays poker. NTC Holodeck 11: NRPG (Hey, what's
going on?) NTC --> SB NOVA: Ensign Jones reports for duty. USS PUMA:
Bridge --> Ready Room Fred gets told off. USS YOSEMITE: Away Team Beaming
down to the planet. USS YOSEMITE: NRPG Change of Mailing Address SB NOVA:
Laundry Room
Some examples of bad subject lines (comments are bracketed in italics
) :
NTC (No location.) NOVA Training Center: Holodeck 2 (Should use abbreviation.)
Holodeck 11: NRPG (No ship/base/unit.) NTC: NRPG -- WHAT IS GOING ON!!!
(Using all caps is considered rude. It's like shouting. Try to be polite,
even if you're frustrated.) NRPG NTC - Holodeck 11 (NTC should go first.)
PUMA: Bridge --> Ready Room Fred gets told off. (No USS.) USS Yosemite
Away Team (Yosemite should be all caps.) Laundry Room SB NOVA (Unit name
should go first.)
It's really pretty easy once you get the hang of it. Pay attention to
subject lines when you get ATR mail. It should tell you a lot about what
is contained in the post.
2.2.3 StarDates
This is one thing that is regulated fleetwide. Stardates are a tool
used in the alt.games.atr.rpg game to keep track of time. In the game,
stardates are defined as follows: YMMDD.hhmm
Y is a number for the year. The current year in the game is 2498 (aproximately
90 years from the beginning of Star Trek: The Next Generation), thus stardates
for 1996 begin with 8. Stardates change at the beginning of each year regardless
of the amount of 'game time' that has passed, thus 1994=6, 1995=7, 1996=8,
etc.
MM is the number for the current month. 01=January, 02=February... 12=December.
Don't forget the 0 as a place holder.
DD is the current day. The first of the month is 01, the second is 02,
etc. Again, don't forget the 0.
hh is the current hour on a 24 hour clock. 8 AM = 08, 6PM = 18, etc.
If military time confuses you, just remember that if it's after noon, add
12 to the hour. 1:00 pm = 1300 hrs, 2:00 pm = 1400 hrs, 3:00 pm = 1500
hrs, etc. Midnight is 0000 hrs military time.
mm is the current minutes.
Then February 15, 1995, 8:58 PM would have been: 70215.2058 December
25, 1996, 12:24 AM will be: 81225.0024
Note that stardates are always in GMT.
2.2.4 Beginning a Post
Posts should start with the Stardate. Also, many players use a Scene
or Location to orient the reader.
The Stardate should be the date and time the post was written. Don't
worry about game time. Game time will pass much slower. In my experience
it can take as much as a month of role playing time to do a single day
in the game.
The Scene, if used, should tell the reader where the post takes place,
and, perhaps, even when in game time. A good Scene tag should quickly get
the reader into the post.
For example, a post that is written on February 15th, 1995 at 8:58 PM
that takes place in Sickbay right after the Away Team returned from the
planet's surface could start like this:
SD 70215.2058 Scene: Sickbay (right after the Away Team returned)
Then, with the scene set, you can start right into the post.
2.2.5 NRPGs
Often it will be necessary to break out of role playing mode and talk
directly to the reader. Whenever this is done, it should be preceded by
the letters NRPG to distinguish it from the role playing.
Posts almost always end with an NRPG section for general statements,
questions, and clarification. Here you can request for other players to
follow up on parts of the post or explain parts that might seem obscure.
Captains will often use NRPG sections to give instructions to players,
so pay special attention to it.
It is best to place all NRPG comments at the end of your post, rather
than breaking up the post by placing them in the middle of the post. NRPG
comments in the middle of the post tend to be distracting and sometimes
annoying. There is no reason that you cannot refer to a specific place
in the post when making your comments at the end.
2.2.6 Signing Off
When ending a post, always give your name and your character's name
to identify the writer. This may seem superfluous, and perhaps it is, but,
hey, it's a good way to end.
The following format is suggested:
Some Nicety,
Your name, Character Name Billet, Location, Registry Fleet or Organizational
Unit <email address>
Submitted respectfully by,
Frank Peters, Captain Yetmi Commanding Officer, USS ERNIE, NCC 15453
Katuba Fleet <fr...@whatever.com>
Some players develop elaborate sigs (signatures) which contain all of
their characters and positions as well as some spiffy saying or thought.
This is up to you, of course, but remember to keep them short.
2.3 Preparing for Life after NTC
NTC gives the new player the opportunity to sit back and prepare with
his or her Holodeck instructor for their career in Starfleet.
2.3.1 Shaping the Bio
As was said before, your bio is your friend. A good bio is important
to have before leaving NTC. Use your instructor as a resource and look
at other bios located on the newsgroup or on the web page.
2.3.2 Choosing a Position
Though many players come in with a specific position in mind (CMO, SEC/TAC,
FCO, etc.), others are uncertain. If you fall into the latter category,
now is the time and this is the place to figure out what you want your
character to be. Again, use your instructor as a resource and monitor posts
on the newsgroup.
All players will need to inform Commander Azael (in charge of personnel),
when they graduate from NTC, what kind of position they desire. You don't
have to narrow it down to one choice, but make certain that you'd be happy
with all the alternatives you give her, you may just have to live with
it.
There are usually many CNS (Counselors) and CMO (Chief Medical Officers)
positions open in the fleet. If you want a fast posting, these might be
good choices.
2.3.3 What Kind of Ship?
Not all ships are the same. Each has its own unique flavor and character.
Ultimately, you will be assigned a ship. But that doesn't mean that you
don't have a say in where you go.
Read the newsgroup. The best way to do this is to find a ship, start
at the top and read it all the way through, NRPGs and all. Later, choose
a different ship and do the same.
You may find a ship that you think is a good match for you and has an
open position. If so, request it when you go to the Lt. Don't approach
any member of the desired ship directly. This is a breech of SF etiquette.
If you want to discuss ships you are reading, talk to your instructor.
2.3.4 Reporting to the Lieutenant
When you have graduated from NTC, you will be told to report to Commander
Azael Starbase NOVA. When you do so, include your bio and be sure to tell
her what positions and ships or type of ship you would like to be assigned
to. Please cut out the following form, fill it in and include it with your
post:
--------------------------- cut here ------------------------- STARFLEET
DUTY PREFERENCE SHEET
PLEASE LIST YOUR TOP 3 CHOICES FOR DUTY: (ship or type of missions you
would prefer) 1: 2: 3:
PLEASE LIST DUTY ASSIGNMENT PREFERENCE: (position) 1: 2: 3: ---------------------------
cut here -------------------------
2.3.5 Write Well
Seems obvious, doesn't it? Writing well includes both technical and
creative aspects. In addition to the things already discussed here, there
are a few other technical aspects you should be aware of.
1.Most people will have trouble reading your posts if the lines are
longer than 80 characters. Please be sure that you keep line lengths to
a maximum of 80 characters. 2.Control characters are always a problem.
Avoid using them. DOS machines use a carriage-return(^M) - line-feed(^J)
sequence. You will need to make sure that you do the proper conversion
to get rid of the extraneous ^M. Other problems that often crop up is the
use the wrong type of quotes. Whatever you use to write your post in, be
sure to convert the document to standard ASCII text before you send it.
3.Posts are always easier to read if you leave a blank line between each
paragraph. Please remember to do so. 4.Also, it is better to write in third
person than first person. There are times when first person is appropriate,
such as in log entries, but, in general, your posts should be written in
third person.
You should know that Captains who need crew members often pay close
attention to the NTC postings on the newsgroup. Yes, you have an audience.
Often these Captains will request certain ensigns out of NTC from the Lt.
They should not contact you directly. If they do, inform your instructor
immediately.
3 Commonly Used Jargon
Every group has their lingo, their jargon, their special way of talking
to each other. Like it or not, newcomers are often judged by how quickly
they can adapt to the standard banter. Here are some conventional things
you'll run into in Starfleet.
3.1 Communication Symbols
[ ] or [[ ]] is often used to denote communications or computer voice.
For example:
Tea, Earl Grey, Hot, Picard said to the replicator in a huff. [Insufficient
parameters,] the computer responded. Picard hit his commbadge. Picard to
LaForge. I want a repair crew in my Ready Room immediately. [Aye, Sir,]
Geordi responded.
<> or << >> is sometimes preferred to denote a computer
voice, and to reserve the [ ]s for communications.
* * is often used in a similar way to denote telepathic communication.
3.2 Common Abbreviations
These aren't all the abbreviations used, but it's a good sample. Note
that these abbreviations are not standardized. For definitions of these
terms, see the ATR Manual or ask your Holodeck Instructor.
2O - Second Officer BA - Branch Admiral Capt - Captain CEO - Chief Engineering
Officer CINC - Commander in Chief Cmdre - Commodore Cmdr - Commander CMO
- Chief Medical Officer CNS - Counselor CO - Commanding Officer CSciO -
Chief Science Officer CSO - Chief Security Officer Ens, Esn - Ensign FA
- Fleet Admiral FC - Fleet Commander FCO - Flight Control Officer FO -
First Officer HN - Head Nurse LA - Line Admiral Lt - Lieutenant LTjg -
Lieutenant, junior grade LtCmdr - Lieutenant Commander NPC - Non Playing
Character NRPG - Non Role Playing Game OPS - Chief Operations Officer padd
- Personal Access and Display Device PC - Player Character PRO - Chief
Protocol Officer RL - Real Life RP - Role Playing SA - Senior Admiral SB
- Starbase SCI - Chief Science Officer SD - Stardate SEC - Chief Security
Officer SF - Starfleet SO - Second Officer TAC - Chief Tactical Officer
XO - Executive Officer (same as First Officer - FO)
NTC - NOVA Training Center
3.3 Grins and Giggles
These are abbreviations that people often use that aren't really directly
associated with the game, but they are common enough that they warrant
pointing out.
<G> - Grin <BG> - Big Grin <EG> - Evil Grin <BEG>
- Big Evil Grin <VBG> - Very Big Grin <VBEG> - Very Big Evil
Grin
You get the idea. <G>
4 Style-guide
Writing styles and expectations differ across the fleet. This style-guide
is not intended to be the definitive work, but, hopefully, it will provide
a useful framework for thinking about group writing. If it makes sense
to you, use it. If it doesn't, leave it. You won't hurt my feelings.
Because this is group writing, not simply writing for the individual,
each writer must keep in mind the other writers on the ship. Consider this
the golden rule of posting: Post unto others as you would have them post
unto you. <G> In other words, be considerate.
Posting style can be usefully discussed using the following three axes:
Re-active vs. Hyper-active Solitary vs. Inter-active Plot-driven vs. Character-driven
In each of these, the aim for is for moderation.
While some posts will, out of necessity, need to be weighted one way
or the other on any of the three axes, over the course of play, posts should
even out. Persistent imbalance will prove problematic for the writer and
unit alike.
4.1 Re-active vs. Hyper-active
A re-active post is one that simply responds to a post before it, usually
in a plain and unimaginative manner. It doesn't develop the plot or the
character. It doesn't add to the situation or take anything away. It is
simply there - an innocuous piece of prose that says nothing, demands nothing,
and leads nowhere.
A hyper-active post, on the other hand, changes everything. In the extreme,
a hyper-active post would create new characters, new obstacles, new races,
new worlds, new threads, new everything. It doesn't settle for the status-quo,
but injects lots of things for people to deal with. These are the posts
that every CO dreads because it means sidetracking from the plot in order
to deal with all the new developments.
The middle road would be one in which the writer takes what has gone
on before and uses it as the foundation on which to add something new and
consistent. A good post should develop plot, character, and such, but not
at the sake of continuity. Plot twists are fine. Plot alterations or detours
are problematic.
4.2 Solitary vs. Inter-active
A solitary post is one which involves only one's character. They touch
on no one else in the ship, except maybe NPC's. They generally are character
building pieces, and are fine as such, but, as a rule, they don't develop
the plot much.
An inter-active post touches on many player characters in many facets
- whether through dialogue or action or both. The writer develops relationships,
creates conflict, develops characters, and, very likely advances the plot.
The problem with a post that is too inter-active is that it can involve
other people's characters beyond the other writer's comfort zone. If you
are unsure how a character might react in a situation, it is better to
let the character's player decide than take a chance and be wron g. When
writing an inter-active post, don't resolve all the conversations or situations.
Leave room for the other writer to respond.
The middle road of these poles would be one in which the writer, while
concentrating on his or her character, contacts a few player characters
on the way. Note that in this medium the player characters are the featured
players and should take precedence in consideration over NPC's. The interaction
with the other characters should be in the idiom and style the charcters'
players have already set out. The character development that is done should
be concerned mainly with the writer's character, and not others.
4.3 Plot-driven vs. Character-driven
Character-driven posts develop the character to the exclusion of the
plot. The plot only serves as a foil against which the character can unfold
and become. This leads to some interesting characters, but leads nowhere
for the rest of the players.
In a plot-driven post the character is secondary to the story that is
being told. The story encompasses the whole of the writing, and little
or no attention is given to developing the character through the post.
The story, not the character, is developed. The character is simply an
observer or conduit for the writer. The problem with this is that it leads
to flat, unimaginative characters who stand like paper cut-outs before
whatever confronts them.
The middle road is, of course, to develop the plot as well as character.
The plot can be developed through the character, or the character can be
developed through the plot. Both are possible and equally valid. The idea
is that neither the plot or the character are to remain untouched. Each
should change when they come in contact with each other and help the writer
write. Indeed, a well-developed character suggests many plot pathways to
the observant writer. Likewise, good plot development can't help bu t impact
upon the character who is in the midst of it. In good writing character
and plot dance an intricate dance of interdependence.
5 In Closing...
This is but one resource available to the beginning player. Take advantage
of your Holodeck Instructor while you're training. Out in the fleet, don't
be afraid to ask questions of your First Officer and Commanding Officer.
Above all, POST POST POST
Cmdr. Azael NTC Commandant
From the original ASR ALB FAQ. http://www.nmt.edu/~gpetrie/asr/alb/FAQ.html