communications relay login

[Archived] - Ares Roleplay Basics

Started By:
Caymen Greener, Sun 24 Oct, 2021 10:44 PM
Views:
1497
Replies:
0
    • Pillar of the Community
      Very Rare (100 Points)

      Be a registered user for 10 years

      Unlocked Wed 03 Jun, 2020 6:09 AM

      34.20% have received this achievement

    • The Ghost Writer
      Rare (50 Points)

      Be the Commanding Officer of the Roleplay Division

      Unlocked Sat 29 Sep, 2018 1:05 PM

      0.04% have received this achievement

    • Dedicated
      Rare (50 Points)

      Volunteer for 1+ year

      Unlocked Wed 22 Sep, 2021 12:02 AM

      0.54% have received this achievement

    • The Fool
      Rare (50 Points)

      Got pranked on April 1st

      Unlocked Fri 01 Apr, 2022 12:27 PM

      0.32% have received this achievement

    • To Boldly Go On and On
      Rare (50 Points)

      Reach one-thousand posts on the forums

      Grandfathered

      0.71% have received this achievement

    • Well Respected
      Uncommon (25 Points)

      Reach reputation tier 6

      Unlocked Sun 01 Feb, 2015 1:01 AM

      0.70% have received this achievement

    ACHV. Points
    1095
    Reputation
    9
    Join Date
    Jun 03 2010
    Posts
    3,613
    Location
    Indiana, USA
    0
    • Users who disliked
    • None
    1
    • Users who liked
    • Kiflin
    #1
     –  Last edited by Kiflin; Mon 20 Jun, 2022 10:01 AM.
    ARP 240

    Roleplay Basics
    2021 ARES HANDBOOK
    We like everyone to have fun and do their own thing in the Ares within reason, but we will apply the same basic and simple rules as every other previous UFP roleplay game (so yeah, that's a copy/paste):

    • Follow the UFP Code of Conduct.
    • Be respectful of other players. This means that you should avoid posting for someone without his/her consent, be kind and courteous during the game (your character may be brash, but you do not have to be), and just know that you and your character are part of a “military”/gaming organization, with rules, commanding officers, and standards. Act like a true Starfleet Officer!
    • Obviously no god-mode characters – you are an author just like everyone else, but you are not Q and everyone has a right to roleplay their own characters. Keep this in mind as you move the story along.
    • Ask Ares CO, XO or Simulation Officer if you are unsure of anything (see the last section of this handbook)


    Acronyms
    Also, here are some common acronyms you may see throughout Ares missions:.

    • CO : Commanding Officer, head of the ship in most cases (unless an Admiral is on board AND put in charge)
    • CEO : Chief Engineering Officer, head of engineering, often stationed in engineering, but sometimes found on the bridge.
    • CMO : Chief Medical Officer, head of sickbay and medical treatments (including psychological), usually found in the medical areas.
    • CSciO : Chief Science Officer, head of all science departments and scientific laboratories, usually found on the bridge.
    • CSO : Chief Security Officer, head of security and any marines/soldiers on board. Often stationed in an office elsewhere on the ship.
    • CTO : Chief Tactical Officer, head of weapons and defense systems, working closely with Operations often. Usually stationed on the bridge. Occasionally combined with CSO.
    • JP : Joint Post, described above. A major mission story contribution involving the individual work of multiple (2 or more) authors/players.
    • OOC : Out-of-character, meaning the content does not contribute to the direct story telling but provides background, unseen, confident info. Surrounded by (( )) at all times.
    • OPS : Operations, in charge of communications and sensors, sometimes combined with Helm.
    • SD : Stardate, in case the stardate changes drastically mid-post (mostly found in JPs).
    • UFP : United Federation of Planets, our parent gaming group and also the governmental body that contains all the systems we are fighting for in the war in game.
    • XO : Executive Officer, second in command, most often on the bridge, defacto successor to the CO should something happen. After the XO, succession can go either by rank + seniority or often cases to Ops and/or Tactical.

    Post Formatting
    And a bit of formatting basics for Joint Posts:
    Ensuring Joint Posts are properly formatted and the proper tags are applied is a lot more important than it looks. A Joint Post that is formatted properly can give readers and your fellow writers a clearer image of what's going on. A post with poor formatting can not only break immersion, but can also result in confusion in some cases. The following tags should be applied in JP's to make sure they're as clear as can be!

    Locations
    A location should be present at the beginning of a post to show where the scene is starting. The location may change throughout the post, and every time it does it should be marked in the same way.
    Example:


    USS Ares
    Deck 1 - Bridge


    To put a location or label of some sort, you can use this code:
    Code:
    [font=LCARS][size=5][color="#99CCFF"]USS Ares[/color][/size][color="#99CCFF"][size=2]Deck 1 - Bridge[/size][/color][size=2][/size][/font]
    Normal Text
    Any text in a post which includes a characters actions, etc. is considered normal text, and doesn't need to be marked in any particular way.
    "Speaking"
    Whenever a character is communicating verbally, it is to be marked out with quotation marks. Anyone within earshot of the character can hear this.

    =^= Comm Speaking =^=
    This indicates that someone is remotely speaking via comm (another place on the ship/station, a friend or foe on another ship, etc).
    ~"Thinking"~
    There should be a special tag, typically used with tildes, when someone is thinking something rather than speaking aloud.
    *"Computer Confirms"*
    Some other format should be used to signal the computer is doing something, like chirping, processing, or speaking. This is sometimes used with the tildes as with 'thinking', but should be clear in surrounding narrative as well.
    ((TAG Captain))
    As stated previously, these are OOC tags to indicate that a particular person is expected to type a response, reaction, etc. where the tag is located.
    [[OOC Eaglesg: Note for people here]]
    This is a note that is designated NOT to be a part of the post, but instead to let folks know what might be going on, to clarify something in the thread, or to coordinate parts of a post. These should always be at the beginning or end. If you need to make an Out-Of-Character note or question, please put it in a spoiler and quote. Here is the code and what it would look like:
    Code:
    [quote]OOC: Ok, so just testing this OOC note thing. yay![/quote]
    OOC: Ok, so just testing this OOC note thing. yay!

    Header Formatting
    Putting a header in your post is practically essential. It helps establish where & when your post is. You can still establish that information in the body of your post, but having that up front helps alleviate a lot of confusion.
    Example:
    Planet or ship
    Specific location on Planet/Ship

    When the post happens

    FAB spacer small
    ^^^^^This bar is COMPLETELY not required, but it helps pretty up your post^^^^^

    Cod for the bar:
    Code:
    [img]https://ufplanets.com/ufp/fab/images/FAB-spacer-small.png[/img]

    Color References
    UFP Light blue: #99CCFF
    UFP Orange: #D37445
    UFP Dark Blue: #336699

    UFP Shortcodes: [CL4]text[/CL4] looks like text
    This works for all CL levels to match UFP colors: CL1 CL2 CL3 CL4 CL5 CL6

    Federation: #336699
    Romulan: #008000
    Klingon: #800000

    TMV5AlZ


    Rank Images
    Here are the standard rank images we use in Ares. You can modify the image location/URL to change the rank you wish to use.

    UFP Style: rcapttltcmdryensignredblank

    Alt Ares Style: R OF 6T OF 4Y OF 1R Blank

    Romulan Alt: 07 o6 07 o5 07 o4 07 o3 07 o2 07 o1
    Commander (Capt), Subcommander (Cmdr), Centurion, Lieutenant, Sublieutenant, Uhlan (Ensign)

    Klingon Alt: 3 16 3 15 3 14 3 13 3 12 3 11
    Captain, Commander, Lt Commander, Lieutenant, Lieutenant JG, Ensign or Bekk
    Not all "pips" are available at the proper rank, so I had to fudge a bit. But these are close enough for our purposes.

    Example Code from above:
    [IMG]https://ufplanets.com/ufp/ares/ranks/officer/rcapt.png[/IMG]
    [IMG]https://ufplanets.com/ufp/ares/ranks/officer/tltcmdr.png[/IMG]
    [IMG]https://ufplanets.com/ufp/ares/ranks/officer/yensign.png[/IMG]
    [IMG]https://ufplanets.com/ufp/ares/ranks/other/redblank.png[/IMG]

    [IMG]https://ufplanets.com/ufp/ares/altranks/command/R-OF-6.png[/IMG]
    [IMG]https://ufplanets.com/ufp/ares/altranks/sciences/T-OF-4.png[/IMG]
    [IMG]https://ufplanets.com/ufp/ares/altranks/operations/Y-OF-1.png[/IMG]
    [IMG]https://ufplanets.com/ufp/ares/altranks/blanks/R-Blank.png[/IMG]

    [IMG]https://ufplanets.com/ufp/ares/altranks/romulan/07-o6.png[/IMG]
    [IMG]https://ufplanets.com/ufp/ares/altranks/romulan/07-o5.png[/IMG]
    [IMG]https://ufplanets.com/ufp/ares/altranks/romulan/07-o4.png[/IMG]
    [IMG]https://ufplanets.com/ufp/ares/altranks/romulan/07-o3.png[/IMG]
    [IMG]https://ufplanets.com/ufp/ares/altranks/romulan/07-o2.png[/IMG]
    [IMG]https://ufplanets.com/ufp/ares/altranks/romulan/07-o1.png[/IMG]

    [IMG]https://ufplanets.com/ufp/ares/altranks/klingon/3-16.png[/IMG]
    [IMG]https://ufplanets.com/ufp/ares/altranks/klingon/3-15.png[/IMG]
    [IMG]https://ufplanets.com/ufp/ares/altranks/klingon/3-14.png[/IMG]
    [IMG]https://ufplanets.com/ufp/ares/altranks/klingon/3-13.png[/IMG]
    [IMG]https://ufplanets.com/ufp/ares/altranks/klingon/3-12.png[/IMG]
    [IMG]https://ufplanets.com/ufp/ares/altranks/klingon/3-11.png[/IMG]

    The Alternate Style ranks were created at Kuro-RPG. Please do not modify the images in any way. If you wish to obtain them and an up-to-date copy, access the Kuro-RPG Website.


    Activity Expectations ( dammit Jim, we are officers )
    Joining Ares is knowing that we're here to have fun, and the only condition to have fun is that each member of Ares need to be active. All we are requesting from each player is a minimum of one post per week on each character linked to that individuals account. It can range from any of the following:

    • Personal Logs (paragraph)
    • Mission Post (more than one paragraph, tag others to participate, tags indicate that a particular person is expected to type a response, reaction, etc. where the tag is located. )
    • Joint Post (more than one paragraph)

    If someone does not answer your tag, keep playing anyway. Do not let somebody else's inability to respond, for whatever reason, interrupt your writing and your character's role in the story.

    Don't worry: this is more a guidance advice than a strict rule. We will most likely not hunt you for not meeting these requirements every week unless a month goes by. We don't like putting rules in place, but we really do need to strive for activity for Ares to live!