ORIGINS: Writer's Handbook: Difference between revisions

no edit summary
No edit summary
 
(9 intermediate revisions by 2 users not shown)
Line 1: Line 1:
[[Category:Bureau of Information]][[Category:Task Forces/Unit Portals]][[Category:ASR: ORIGINS]]{{Template:header_menu}}
[[Category:Bureau of Information]][[Category:Task Forces/Unit Portals]][[Category:STAR FLEET: ORIGINS]]
-----
{{ORIGINS_header}}


<center>[[Image:Insignia_command_200.png|Starfleet Command Group Insignia Pin]]</center>


 
<center><font size="+2" color="#868cde">STAR FLEET: ORIGINS Writer's Handbook</font></center>
<center><font size="+2" color="#868cde">ASR: ORIGINS Writer's Handbook</font></center>
<center>''Updated SD 2260.148''</center>
<center>''Updated SD 2260.140''</center>




==Introduction==
==Introduction==
The writing environment of ASR: ORIGINS, like the rest of ASR, is one that is often called "shared fiction"- fiction whose development is shared by members of a team instead of being an individual process.  This places less emphasis on the individual writer and more on the unit as a whole.  
The writing environment of STAR FLEET: ORIGINS, like the rest of Star Fleet, is one that is often called "shared fiction"- fiction whose development is shared by members of a team instead of being an individual process.  This places less emphasis on the individual writer and more on the unit as a whole.  


This means that writing in ASR: ORIGINS is much like playing on a sports team or serving in an actual military unit- the importance of the individual is overshadowed by that of the group as a whole.  In the most basic of senses, the crew of your starship is a team first, and an assortment of individuals second.  
This means that writing in STAR FLEET: ORIGINS is much like playing on a sports team or serving in an actual military unit- the importance of the individual is overshadowed by that of the group as a whole.  In the most basic of senses, the crew of your starship is a team first, and an assortment of individuals second.  


Because of this, writers on our starships must always be conscious of their crewmates when writing.  As such, we have to consider things that one normally wouldn't do in a more solitary writing forum.  Some of these things can be found below.
Because of this, writers on our starships must always be conscious of their crewmates when writing.  As such, we have to consider things that one normally wouldn't do in a more solitary writing forum.  Some of these things can be found below.
Line 25: Line 23:


====RP Posts====
====RP Posts====
RP Posts are posts written "in-character" and take place within the confines of the alternate ASR universe we've created for ASR: ORIGINS.  These posts either add something to the develoment of the character (called "CD posts") or move the plot of the story forward.
RP Posts are posts written "in-character" and take place within the confines of the alternate ASR universe we've created for STAR FLEET: ORIGINS.  These posts either add something to the develoment of the character (called "CD posts") or move the plot of the story forward.


All RP posts will have a subject line that looks pretty much the same:
All RP posts will have a subject line that looks pretty much the same:
Line 31: Line 29:
* '''[ORIGINS] SHIP NAME: Post Title'''
* '''[ORIGINS] SHIP NAME: Post Title'''


As you can see, all RP posts- because they will be posted to the [mailto:starfleet-rpg@yahoogroups.com general ASR post archive] as well as your ship's archive- are tagged witht he [ORIGINS] tag.  After that, it looks the same as ASR Prime posts: ship name in all capital letters, and the post title.
As you can see, all RP posts- because they will be posted to the [mailto:starfleet-rpg@yahoogroups.com general ASR post archive] as well as your ship's archive- are tagged with the [ORIGINS] tag.  After that, it looks the same as STAR FLEET: Prime posts: ship name in all capital letters, and the post title.


For example, a proper RP post subject line should look like this:
For example, a proper RP post subject line should look like this:
Line 39: Line 37:


====NRPG Posts====
====NRPG Posts====
NRPG, or "non-role-playing game" posts, are posts written "out-of-character" (as such, these are sometimes called "OOC posts"), in your own voice.  They are not posted to the general ASR archive because they do not take place within the game action.  Instead, NRPG posts are sent either to specific individuals or to the crew as a whole, and they typically deal with things like collaborating on a post, writing a joint post, or notifying everyone of an impending absence.
NRPG, or "non-role-playing game" posts, are posts written "out-of-character" (as such, these are sometimes called "OOC posts"), in your own voice.  They are not posted to the general Star Fleet archive because they do not take place within the game action.  Instead, NRPG posts are sent either to specific individuals or to the crew as a whole, and they typically deal with things like collaborating on a post, writing a joint post, or notifying everyone of an impending absence.


NRPG posts use a subject line like this:
NRPG posts use a subject line like this:
Line 52: Line 50:


===Stardates===
===Stardates===
Stardates in ORIGINS are done differently than they are in the rest of ASR; this was done to bring ORIGINS in line with the dating system established in the 2009 Trek movie.  A stardate is used to locate your post in a specifc point; it helps determine the sequence of events during a mission, which can be very important.  therefore, all posts have a stardate tag.
Stardates in ORIGINS are done differently than they are in the rest of Star Fleet; this was done to bring ORIGINS in line with the dating system established in the 2009 ''Star Trek'' movie.  A stardate is used to locate your post in a specifc point; it helps determine the sequence of events during a mission, which can be very important.  therefore, all posts have a stardate tag.


A stardate should look like this:
A stardate should look like this:
Line 73: Line 71:


===The Signature===
===The Signature===
Every post in ASR is "signed" with the same basic information; in ASR: ORIGINS, we add one extra tag tot he end for clarity's sake:
Every post in Star Fleet is "signed" with the same basic information; in STAR FLEET: ORIGINS, we add one extra tag to the end for clarity's sake:


   '''Character Rank and Name'''
   '''Character Rank and Name'''
   '''Position'''
   '''Position'''
   '''SHIP NAME and Registry Number'''
   '''SHIP NAME and Registry Number'''
   '''ASR: ORIGINS'''
   '''STAR FLEET: ORIGINS'''


Remember that ship names in ASR are ALWAYS written in all caps.
Remember that ship names in Star Fleet are ALWAYS written in all caps.


So, a proper signature at the end of a post would look like this:
So, a proper signature at the end of a post would look like this:
Line 87: Line 85:
   '''Commanding Officer'''
   '''Commanding Officer'''
   '''USS CONSTELLATION NCC-1017'''
   '''USS CONSTELLATION NCC-1017'''
   '''ASR: ORIGINS'''
   '''STAR FLEET: ORIGINS'''




Line 120: Line 118:
==Respecting the Creations of Others==
==Respecting the Creations of Others==


Sooner or later (probably by the time you finish your first real ASR post), all writers of shared fiction have an epiphany: it is impossible to write ONLY for your own primary character. A player will have to include other characters in his or her writing. Sometimes these characters are "NPC's" or non-player characters.  These are generic, rather flat characters which are open for use by anyone.  However, sooner or later, a writer finds him or herself in the position of "putting words in another player's character's mouth."  And it is here that we have to be careful.  
Sooner or later (probably by the time you finish your first real Star Fleet post), all writers of shared fiction have an epiphany: it is impossible to write ONLY for your own primary character. A player will have to include other characters in his or her writing. Sometimes these characters are "NPC's" or non-player characters.  These are generic, rather flat characters which are open for use by anyone.  However, sooner or later, a writer finds him or herself in the position of "putting words in another player's character's mouth."  And it is here that we have to be careful.  




Line 166: Line 164:
===Obscenities===
===Obscenities===


Lastly, a word about obscenities.  ASR has people from many different walks of life, many different cultures, and varying ages.  We must respect this if we are to ensure the happiness of everyone in the unit.  
Lastly, a word about obscenities.  Star Fleet has people from many different walks of life, many different cultures, and varying ages.  We must respect this if we are to ensure the happiness of everyone in the unit.  


As such, obscenities should generally be avoided.  Now, this does not mean that, should your character get hit in the stomach with a bat'leth, it would not be appropriate for him or her to say "shit."  It might very well be- we ARE trying to make the characters behave realistically, after all.  If a character is "hoppin' mad," a stray expletive or two might just be apropos.  But using such language for simple shock value or for no real reason should be avoided, out of respect for those who do not condone such flippant use of language.  
As such, obscenities should generally be avoided.  This does not mean that, should your character get hit in the stomach with a bat'leth, it would not be appropriate for him or her to say "shit."  It might very well be- we ARE trying to make the characters behave realistically, after all.  If a character is "hoppin' mad," a stray expletive or two might just be apropos.  But using such language for simple shock value or for no real reason should be avoided, out of respect for those who do not condone such flippant use of language.  




-----
-----
==Final Thoughts==
==Final Thoughts==


Everything on this page has dealt with the idea of respecting one's crewmates and involving them in our work.  However, remember that no one is perfect here in ASR, and that we do this voluntarily.  This means that, if someone steps on your toes a little bit regarding character or language, the best thing to do is to either let it go (if it's not that big a deal), or just send the offending party a friendly note saying, "Hey, no big deal, but you did this and I didn't like it."  If you do so tactfully and with respect, you will almost always get a positive response.  
Everything on this page has dealt with the idea of respecting one's crewmates and involving them in our work.  However, remember that no one is perfect here in Star Fleet, and that we do this voluntarily.  This means that, if someone steps on your toes a little bit regarding character or language, the best thing to do is to either let it go (if it's not that big a deal), or just send the offending party a friendly note saying, "Hey, no big deal, but you did this and I didn't like it."  If you do so tactfully and with respect, you will almost always get a positive response.  


The WRONG way to go about bringing a mistake to someone's attention is to send out a ship-wide NRPG message and chew the person out in front of everyone; all that will do is embarrass and possibly enrage the offending party who most likely simply made an honest mistake.  Talk to the offending party one-on-one first, without anyone else watching.  If the same mistakes keep happening after that, THEN you contact your CO and XO about the problem.  It is OUR job to take care of it, as it would be in a military unit- it is NOT yours.  To do so is disrespectful, and we don't operate that way here, whether you think the offending party deserves respect or not.  Remember- everyone makes mistakes, so stay cool.  
The WRONG way to go about bringing a mistake to someone's attention is to send out a ship-wide NRPG message and chew the person out in front of everyone; all that will do is embarrass and possibly enrage the offending party who most likely simply made an honest mistake.  Talk to the offending party one-on-one first, without anyone else watching.  If the same mistakes keep happening after that, THEN you contact your CO and XO about the problem.  It is OUR job to take care of it, as it would be in a military unit.  It is NOT yours.  To do so is disrespectful, and we don't operate that way here, whether you think the offending party deserves respect or not.  Remember that everyone makes mistakes, so stay cool.  


I would also encourage everyone to allow for some small discrepancies in character portrayal and the like.  I'm not saying that major problems should be ignored, but if someone used a manner of speech for your character that was a little off, let it go.  It's not worth making an issue about- I would simply continue to work hard in my own writing to further establish patterns of speech so as to make it easier for others to grasp.  We should always consider that, if mistakes are made in how others view our characters, WE are probably as much to blame for portraying them poorly as the offending parties are for doing the same.  
I would also encourage everyone to allow for some small discrepancies in character portrayal and the like.  I'm not saying that major problems should be ignored, but if someone used a manner of speech for your character that was a little off, let it go.  It's not worth making an issue about- I would simply continue to work hard in my own writing to further establish patterns of speech so as to make it easier for others to grasp.  We should always consider that, if mistakes are made in how others view our characters, WE are probably as much to blame for portraying them poorly as the offending parties are for doing the same.  
Line 189: Line 188:
Commanding Officer<br>
Commanding Officer<br>
USS CONSTELLATION NCC-1017 <br>
USS CONSTELLATION NCC-1017 <br>
ASR: ORIGINS
STAR FLEET: ORIGINS
10,625

edits