Quick links:
Reserves thread
Requests thread
Event planning thread

Reserves

If you want to reserve a character, comment here. Reserved characters cannot be app'ed by anyone else other than the person who made the reserve. Reserves should used in a situation where you are already working on an app and do not want anyone to preempt you, not when you are still only pondering whether to app a character or not.

Reserves are valid for one month after posting. After that time, a reserve comment will be deleted. If your reserve expires and you do not actually end up app'ing the character, please wait a while before making another reserve. There are no official rules on that but reserve abuse will be frowned upon.

Requests

If you wish to see a particular character in the game, write a character request here. Characters can be requested only in two cases:

-When you already have a character from the same canon as the requested character, and seek to increase the cast.
-When you are ready to app into the same canon as the requested character. In such a case, write which character you are willing to app as well.

Requests are cleared every activity cycle, but can be reposted without any limits.

Event Planning

If you want to plan a particular event for your canon, especially one that requires or would be nice if it included cross-canon interaction, post here. Discussion between players is encouraged!

If you need a mod's opinion on anything, or want to bring results of planning to the mods' eyes, please contact them as usual.

Event planning tags are not cleared.
srwu_mods: (Default)
( Jan. 14th, 2014 12:39 am)
tl;dr version: Post activity here. You need 35 tags every AC cycle. A cycle is 2 months. Post or mission counts as 5 tags.

Activity and hiatus rules

  • Each activity cycle lasts 2 months. Once each activity cycle ends, you have one week to post your activity, by providing links to it in your response to this post.

  • During each activity check, you are required to provide at least 35 in-character tags (comments) made during the appropriate activity cycle. The tags can come from more than one thread or a post. There are no limits to the size of a thread the tags were posted in.

  • Each in-character post you write during the activity cycle counts as 5 extra tags for the sake of activity, in addition to tags written in the post itself. Likewise, each mission you participate in counts as 5 extra tags.

  • Any character that fails an activity check is ACTIVITY WARNED. A list of ACTIVITY WARNED characters is publically available.

  • A character that fails an activity check and is already ACTIVITY WARNED will be removed from the game. A character that is ACTIVITY WARNED but passes an activity check is no longer warned.

  • A character removed from the game because of inactivity may be app'ed by another player. The mods may also decide to allow the original player to re-app the same character, but that is not guaranteed.

  • Characters that are absent from the game (in any in-character position that prevents them from interacting with the rest of the cast) are excused from the activity check, if they are absent for at least three weeks during the cycle.

  • Freshly-introduced characters are excused from the activity check during the first cycle they were introduced in.

  • Players may declare they are on HIATUS for an activity cycle, if circumstances prevented them from being active in the game. A HIATUS has to last at least three weeks to excuse a player's characters from an activity cycle. A character cannot be excused from failing activity due to a hiatus two activity cycles in a row.

  • In cases of extreme inactivity (that is, a character who does not interact with others AT ALL despite being present in the game, for a prolonged period of time), mods reserve the right to remove a character from the game without observing normal inactivity rules.

  • REMEMBER! Posting activity is your responsibility, not the mods'. Even if you tagged enough to clear an activity check, if you won't write it in the Activity post then we won't know and you will be warned as if you had no activity at all.
This is a HMD post for the mods, and the game itself in general.
Mod Contact Information

Following individuals are mods of the game SRW Unification:


Cubey - responsible for game site maintenance, mission running, general mod duties
AIM handle: cubey@aol.pl


Tengu - responsible for mission running, general mod duties
AIM handle: tengusaur


Steam - responsible for mission running, general mod duties
AIM handle: wyverncakes

Following individuals are mission runners of the game. They are responsible for running missions but not for other mod duties:


Jockey
AIM handle: vertigojockey@gmail.com


Our contact email address: srwunification@gmail.com

If you need to contact the mods, the fastest way is to check if anyone is on AIM and talk to us directly. Please do not put pressure on the mission runners - they do not have the same duties and responsibilities as full-time mods, though they may be able to relay a message to the "main" mods if no one from that group is online.
Failing that, the second fastest way is to leave a comment on this page. All comments are screened by default so no one but the mod team can read them. If you post anonymously, leave some sort of contact information we can use to respond to you.
Sending an email to the contact address or a private message to the mod account is the slowest method of contacting us. Please do that when you send us material you want us to have access to (detailed mission lists for example), and not for emergencies.

How's My Driving post list

HMD for the game itself, and the mods

Mods' HMDs, respond to them whether you have feedback concerning their work as mods or as players:
Tengu's HMD
Cubey's HMD
Steam's HMD
Jockey's HMD

Players' HMDs:
Drascin's HMD
Fri's HMD
Ishikar's HMD
Jonny's HMD
Junker's HMD
Terra's HMD
PLAYER CONTACT INFO

The mods' contact info can be found here.
Players' contact info can be found on this page. You need to be a community member to see it.

PLAYER LIST

Cubey (mod)
Characters: [personal profile] herodrawing Hitachi Izuru (canon: Majestic Prince), [personal profile] star_of_sad Setsuko Ohara (canon: Super Robot Wars Z), [personal profile] jianai Ren Ubuntu (canon: Best Face of Humanity (OC))
HMD: here

Steam (mod)
Characters: [personal profile] empress_without_a_throne Mizuki Onodera (canon: SolSavior (OC)), [personal profile] kill_all_vagans Flit Asuno (canon: Gundam AGE), [personal profile] prismphantom Selena Recital (canon: Super Robot Wars Alpha 3)
HMD: here

Tengu (mod)
Characters: [personal profile] cloningblues Asagi Toshikazu (canon: Majestic Prince), [personal profile] abugslife Hetepheres (canon: Swarms of Gods (OC)), [personal profile] a_louse Roger Smith (canon: the Big O)
HMD: here

Jockey (mission runner)
Characters: [personal profile] genericprotagonist Raleigh Becket (canon: Pacific Rim), [personal profile] tillallareone Optimus Prime (canon: Transformers Gen 1), [personal profile] break_the_nine Leos Klein (canon: Armored Core 1: Master of Arena), [personal profile] mistaken_for_monster Volya Alkaev (canon: Dirge of Fate (OC)), [personal profile] not_a_prize Peola Nelfess (canon: Runaway Princess Bride (OC)), [personal profile] sang_av_helten Skald Skogkattson (canon: Project 'M' (OC))
HMD: here

Aldo Salt
Characters: [personal profile] actuallyselfish Dido Sybil (canon: SolSavior (OC))
HMD: none

Arachnion
Characters: [personal profile] ships_full_of_missiles Bruno J. Gloval + bridge crew (canon: SDF Macross), [personal profile] 63rd_shockwave Sarah Daniels (canon: Dirge of Fate (OC)), [personal profile] brought_it_back Eva Barton (canon: Project: Pedantic Blue (OC))
HMD: none

Corel
Characters: [personal profile] caressthedarkness Seta Albreich (canon: Hell's Embrace (OC))
HMD: none

Drascin
Characters: [personal profile] keep_your_dignity Kagura (canon: Hellsinker), [personal profile] booty_chaser Ashe (canon: Megaman ZXAdvent)
HMD: here

Fri
Characters: [personal profile] ben_dixon Kakizaki Hayao (canon: SDF Macross), [personal profile] dolorous_sensei Walt Schmertz (canon: the Stain (OC)), [personal profile] delouser R. Dorothy Waynewright (canon: the Big O), [personal profile] armowrpiercing Baron Archibald von Whiskers (canon: Project 'M' (OC))
HMD: here

Ishikar
Characters: [personal profile] ugyuuya Yuuya Bridges (canon: Muv Luv Total Eclipse), [personal profile] broken_puppet Lamia Loveless (canon: Super Robot Wars Advance/Original Generation 2)
HMD: here

Jonny
Characters: [personal profile] gold_four Ataru Suruga (canon: Ginga Kikoutai Majestic Prince), [personal profile] tiger_ken Kentaro Torao (canon: SolSavior (OC))
HMD: here

Junker
Characters: [personal profile] srwjunker Russel Bagman (canon: Super Robot Wars Original Generation), [personal profile] fire_dancer Raquel Manora (OC, canon: Super Robot Wars Compact 3)
HMD: here

Terra
Characters: [personal profile] majestic_keiki Kei Kugimiya (canon: Majestic Prince), [personal profile] itbelongsinamuseum Alexandra de Witt (canon: Sacred 40 (OC))
HMD: here

CANON LIST

Armored Core 1: Master of Arena
Characters: Leos Klein

The Big O
Characters: Roger Smith, R. Dorothy Waynewright

Ginga Kikoutai Majestic Prince
Characters: Hitachi Izuru, Asagi Toshikazu, Kei Kugimiya, Ataru Suruga

Gundam AGE
Characters: Flit Asuno

Hellsinker
Characters: Kagura

Megaman ZXAdvent
Characters: Ashe

Muv Luv Alternative: Total Eclipse
Characters: Yuuya Bridges

Pacific Rim
Characters: Raleigh Becket

Super Dimension Fortress Macross
Characters: Kakizaki Hayao, Bruno J. Gloval + bridge crew

Super Robot Wars:
Super Robot Wars Advance/Original Generations 2
Characters: Lamia Loveless

Super Robot Wars Alpha 3
Characters: Selena Recital

Super Robot Wars Compact 3
Characters: Raquel Manora (OC)

Super Robot Wars Original Generation
Characters: Russel Bagman

Super Robot Wars Z
Characters: Setsuko Ohara


Transformers Gen 1
Characters: Optimus Prime



Original canons:

Best Face of Humanity
Characters: Ren Ubuntu

Dawn of Miracles SolSavior
Characters: Mizuki Onodera, Kentaro Torao, Dido Sybil

Dirge of Fate
Characters: Volya Alkaev, Sarah Daniels

Future's War Today
Characters: Anastasia "Ana" Racik

Hell's Embrace
Characters: Seta Albreich

Project 'M'
Characters: Skald Skogkattson, Baron Archibald von Whiskers

Project: Pedantic Blue
Characters: Eva Barton

Runaway Princess Bride
Characters: Peola Nelfess

Sacred 40
Characters: Alexandra de Witt

The Stain
Characters: Walt Schmertz

Swarms of Gods
Characters: Hetepheres
srwu_mods: (Default)
( Jan. 14th, 2014 10:28 pm)
Player name: Write whatever you want us to call you. Don't give us your RL name (unless you want to). REQUIRED
AIM contact: This game uses AIM extensively, for missions and OOC communication. As such an AIM handle is REQUIRED. If you are not comfortable having your contact info publically known, send it in a message to the mod account and note here you did this instead.
Alternate contacts: Write your email, personal DW/LJ or Plurk account, etc. - whatever you are willing to let people use to contact you. Keep in mind that the mods do not use Plurk. As above, you can send this in a message to the mod account if you don't want it publically known. OPTIONAL
Character name: Add (OC) to the name if it's an original character. REQUIRED
Source canon: Pretty self explanatory. If it's an original canon, it's a good idea to give it a name and write it here. Also add (OC) to the original canon's name. REQUIRED
Community tag: Almost always some form of the character's name, "firstname lastname" for example. Used so we don't accidentaly have multiple tags for one character. REQUIRED
Do I Want a HMD: This is a question on whether you want to have a How's My Driving post or not. Please answer using one of the below:
"Yes" - the game will provide a HMD post for you, and the mods will give you a link as soon as the application is approved
"No, I'll set up my own one" - you will create, or have already created your own HMD page. Make sure to provide us with a link to the HMD when it's ready. The game only allows for HMDs that let people post anonymously, so make sure yours does that
"No, I don't want a HMD" - self-explanatory, you'd rather not have a HMD post for one reason or another
"I already have one" - this is not your first character in the game and you already have a HMD post for your SRWU players

Notes: Anything you want to add that doesn't fit the standard app format. Feel free to add notes to every section of the app, rather than writing them here. OPTIONAL

Background: A description of your character's canon background. For canon characters, you only need to write enough information to let us know that you are familiar with the character. Do not write any headcanon here (headcanon means things that are not canon but are considered to make sense either by you or the fandom as a whole). For original characters, you have to be more specific - show that the character's background makes sense and fits the setting. The background is written from an OOC perspective. If the characters don't know something but you do, write it down anyway. REQUIRED
Original canon background: Write the background of your original canon here. This is for the canon, not the character. Take other canons and the setting into consideration when writing this section - do not assume your canon exists in vacuum, or in a seperate "universe" where it's the only canon around. REQUIRED for original canons ONLY
Personality: Show us you know enough about your character to play them competently. This is not exclusive to the character's personality at the start of the canon - also write down their character development as it went in canon, or as you expect it to happen during the game (for OCs). For canon characters there are no limits on section length - you can even be short and concise, as long as the section makes it clear you are familiar with the character. Feel free to add headcanon, as long as: 1. it makes sense and does not contradict the rest of the character's personality and 2. you clearly mark which parts of the section are headcanon. For original characters, you have to go into detail to show this is a well thought-out and three dimensional character.
The personality section is probably the most important one and it will have the greatest influence on whether the app is rejected or approved. Obviously REQUIRED
Capabilities and Resources: If your character is exceptionally talented in anything other than mecha piloting, has substantial resources (money, minions, etc), a high military or political rank, or any kind of extraordinary ability (Newtype, being an alien, etc), write this down here. This is for exceptional talents only - being just a mechanic or having disposable income does not need to be noted, but being super rich or a talented mecha designer does. And of course, all extraordinary abilities or powers are exceptional. REQUIRED (unless there is nothing exceptional to write about)
Position in Unity Group: Player characters are assumed to be normal combat operatives/pilots of Unity Group by default, if they're combatants (for non-combatants, they usually just hang around UG for one reason or another). If you want your character to have an additional higher position within Unity Group, please write here what it could be. For more details please read our Upgrade Requests page. IMPORTANT - this position does not replace your character's canon rank or role in whatever organisation they are canonically in, if there is one. This is a position in Unity Group only. OPTIONAL

Type: There are three options here.
Combatant - these characters fight the enemy, by piloting giant robots or other vehicles, commanding capital ships, or in some cases on foot. Most player characters are here.
Non-Combatant - these characters do not have a machine of their own. They are often untrained civilians, but not necessarily: They may still be trained soldiers but they lack extraordinary equipment or abilities that allow them to take on mecha-sized enemies on their own. A non-combatant may be present on a mission, but the way they can influence it is usually very limited.
Commander - these characters have leadership abilities or serve as mission control. Their actions during missions may involve giving commands and instructions to other player characters (with their permission) rather than acting themselves. This is not a standalone type but rather something you combine with two others - Combatant/Commander, or Non-Combatant/Commander.
A character's type can change during the game. REQUIRED

Unit Name: The name of the machine you pilot, a ship you command, or perhaps your own combat form if you're an Ultraman or something like that! REQUIRED for Combatants
Unit Description: Describe your unit - how it looks, what weapons/attacks and special systems does it have, what are its strong and weak points. Perhaps where it came from or who made it. Feel free to link an image, if there is one. REQUIRED for Combatants
Size: Pick one of following:
SS - roughly human-sized
S - larger than a human (3-4 meters tall) to 10-12 meters in height
M - roughly mobile suit sized - 15 to 20-something meters tall
L - substantially larger than a mobile suit, at least 30 meters in height
LL - 75+ meters in height
Feel free to add a brief description to the size rather than just a size class. It's just a guideline, to make it easier to visualize how large the unit is. OPTIONAL.
Terrain compatibility: There are four sub-sections. For each one, write "yes" or "no":
Air: Can your unit fly in a gravitic environment? Yes if it can, otherwise no. Units that can make jumps, even very long ones with use of boosters, still do not count as flying.
Ground: Does your unit have legs, tracks, wheels or anything else that lets it move on solid ground with non-negligible speed? Yes for most, but for example jet fighters answer this "no" even though they have wheels.
Water: Can your unit float in water? If it drowns like a rock, then it's a no.
Space: Is your unit equipped with thrusters, verniers or other systems that allow it to maneuver in space? Or is it forced to float around, throwing or jumping off other space objects to gain momentum? Yes and no respectively.
Terrain compatibilities are OPTIONAL, but very helpful.
Favored terrain: Which environment does your unit perform best in? Select one or at most two terrains from the list above. It does not have to be one you marked positively - most forms of Getter-3 are a "no" in water yet it has water as a favored terrain. OPTIONAL

Upgrades: If you foresee your character to gain something new in their unit during the course of the game, write it here. If it's just a new attack or a system then give it a brief description. If it's a new unit altogether, it is suggested you write a block similar to the Unit block above. Characters are allowed more than just one upgrade, write each seperately.
This list is not exclusive. Players are allowed to request additional upgrades not mentioned in their application. OPTIONAL

Wingmen: If your character is accompanied in combat by NPCs, write about them here. Mention them by name (if they have any) and briefly describe them, their machines and capabilities. During missions, players can write actions that include their wingmen rather than only their own characters. OPTIONAL

Mission requirement: If your character cannot join the cast until a particular mission in their event list happens (usually the first one), because for example: before that happens they do not have a machine to pilot yet or they have no inclination to ally themselves with the Unity Group; then write "yes" here and point out which mission is it. Otherwise (that is, if a character can join the cast and interact with others as-is, or just following an event post that does not require a mission), write "no".
This requirement is only a suggestion and, at the player's discretion, may be changed depending on how many canons are in the game and other circumstances. Characters who require a mission to join the cast will be given priority in mission planning. REQUIRED
Suggested Event List: IMPORTANT! Before writing this section, make sure to read the guide to missions, events and arcs. Write down a list of important events that occur in your canon and that you want to see in the game. For each event, point out if it's a mission or an event post, and provide a description saying what should happen during the event - including descriptions of enemies. Describe the events well enough so that a mod without first-hand experience with the canon can run the event (possibly with help of wikis or other canon review materials), but leave a degree of elasticity to make integration with other canons easier.
Please try to limit yourself to 10 or less suggested missions. There is no limit to how many non-mission events there can be, only ones that are run as a mission.
By default, each mission is in its own individual one-mission arc. If any missions in the canon are in an arc together, make sure to point it out.
REQUIRED, except in following cases:
-The canon is already present in the game and you have no events you wish to add to it
-You decided to app your canon without any missions or events

Sample post: This may take many forms - you can write a theoretical in-character post here, or write a post on a test run community such as [community profile] testrun_box and link it here. The purpose of it is to show us your writing style and that you are able to portray the character accurately. REQUIRED
srwu_mods: (Default)
( Jan. 14th, 2014 11:07 pm)
Below is a glossary of terms you can often find in roleplaying in general, and DWRP in particular.

Table of contents:
General DWRP terms
SRWU-specific terms

General DWRP terms

AC - Activity Check. A requirement every two months (in SRWU at least - may very for other games) to demonstrate that your characters been active in the game - posting, tagging, interacting with other characters, participating in events.

AU - Alternate Universe. AU-style games take canons or characters and change them in a significant way. Characters of opposite gender than their canon versions or setting the canon in a high school or modern day setting are examples of AUs. SRWU is not an AU game.

Canon - a piece of media, for example a TV show, a movie or a video game. If something is "canon" then it means it happened like in the media - canon characters, events, and so on. Compare OC. Non-original canons are often called "established canons" in the game, because calling them "canon canons" sounds stupid.

CR - Character Relationship. Ties between characters - friendship, romance, rivalry, hatred. Characters are said to have “CR” with one another if they’ve interacted and built up some kind of history together. CR can be pre-planned or happen spontaneously.

Cut - Formatting used by Dreamwidth that allows the post author to hide parts of the post behind a link that others must click to view. Often used to compress long posts. Questionable content must be hidden behind a cut, with appropriate warnings/descriptions. For a guide on how to use cuts, see here.

Enabling - Encouraging or helping another player to app their character. Often takes the form of having a character from one canon (or being willing to app one), making it easier for the other player to app from the same canon. Pressuring people into app'ing characters or making commitments they wouldn't make on their own is not enabling, and explicitly against the rules.

Fanon - Headcanon (see below) that a lot of fans agree on.

Godmoding - Determining another character's actions without their player's input or consent. It is explicitly against the rules so do not do this. Players control their characters' actions, but not the results of how these actions affect other characters. If you are afraid this may slow interaction down, coordinate with the other player OOCly while writing your actions or reactions.

Headcanon - One person’s ideas about a canon, which may supplement or even contradict what’s generally accepted as canon. SRWU accepts headcanon as long as it does not contradict canon characterisation and makes sense. Also see fanon.

HMD - "How's My Driving". Solicitation for feedback and constructive criticism on one's time in the game. Usually takes the form of HMD posts, which for SRWU can be found here. HMD posts in SRWU must allow anonymous commenting.

IC - In-character. Anything that happens in the game world, to the characters and not their players. Includes all player characters' actions, of course. Compare OOC.

Infomoding - Having your character act on OOC information, knowing things you are aware of as a player but they could not have learned ICly. Once again, against the rules, please don't do this. If you are not sure is it reasonable for your character to know something or not, contact the mods or affected players.

LCW - Lone Canon Warrior. The only character present in the game from their own canon.

Lock - A post or some prompts in a post can be designated as locked only to specific people, either given by name or described by quality (for example, "locked to close CR only" or "locked to people good at hacking" for an in-universe network action). Before responding to a locked post, make sure you qualify!

Mingle - Type of post where player characters are encouraged to interact with each other and not just with the original author of the post. Threadjacking is still a faux pas.

OC - Original Character or Original Canon. Original Characters do not exist in canon and are made up by their players. Though they may belong to an established canon - a made up VF OC pilot from Macross, for example. Original Canons are whole canons created by the player. Original Canon characters are of course all OCs. Compare canon.

OOC - Out of Character. Anything that happens in the real world, including communication between players. Make sure to keep the line between IC and OOC distinct - just because a character was rude to yours does not mean the character's player hates you. Compare IC.

PB - Played By. OCs and some canon characters do not have a canon appearance, so players often "borrow" an image of a different character from an unrelated canon to serve as basis for their icons. The character the appearance was borrowed from is a PB.

Post - An entry on a journal or community. Comments and responses to a post are called tags. See also thread.

Prompt - Subsection of a post. A single post may contain multiple prompts, generally numbered - for example, one prompt where a character puts out a network message saying “who wants karaoke?”, and a second prompt set a little later where the people who responded to the first one can embarrass themselves in person. Some prompts may be locked to specific people - see lock. When responding to a post with multiple prompts, make it clear which prompt you are responding to.

Tag - This has two meanings: 1. A comment left on a post, either as a response to a post itself, or another tag. If you respond to someone, it means you "tagged" them. 2. Keyword assigned to a post. Posts can be searched by tags, to find for example all posts written by a certain character and such.

Thread - A string of tags in a post, written in response to one another. A single thread (usually) forms a coherent conversation, be it IC or OOC. Posts often have more than one thread, or threads branch out into sub-threads of their own.

Threadjacking - Act of jumping into a thread between other characters with your own. Not technically against the rules, but poor form. Unless you have the involved players' permission, don't do this.

SRWU-specific terms

Backup - characters (or their players) who are not technically present on a given mission, but rather hang around the OOC chat and wait for opportunities to join the mission - which may happen if another player had to leave, didn't show up in the first place, or a character is downed and needs a replacement. Players can sign up for missions as backup if they know they will be busy or can't join the mission until it's already underway, other than that the mission runner will have to decide who is in a mission and who is on backup when there are too many normal signups for a given mission. See also lineup.

Debrief - a post-mission post which states what important events happened on the mission or are a direct result of it, as well as who was present on the mission and (possibly) what damage their units suffered. The damage has no consequences rules-wise, it's used as a roleplaying opportunity. Also includes a link to the mission log.

Lineup - before a mission starts, its mission runner will write a post stating who is on it - which characters and possibly who is on backup (if there were too many signups). This is known as a lineup post. Only characters whose players wrote in the scheduling post or otherwise expressed interest will be in the lineup, you will never find yourself assigned to a mission against your will or knowledge.

Role call - used only in the OOC chatroom, shortly (~15 minutes) before a mission starts. When a mission runner calls for a role call, people who are signed on the mission and already in the room (or aren't signed but want to come anyway, if there are free slots) respond with the name of the character they're sending. This is to quickly check who is already around and ready and if we have to wait for anyone before starting the mission. Role calls usually last only a few moments so please don't talk in the room during one.
.