mayfield_ooc | Applications

• Please read over all the rules and information before applying in order to minimize any confusion before joining.

• If applying for a character that has already been dropped, it would be a good idea, though not required, to know something of their previous interactions. You are also free to pick up a dropped character with no memories of their previous time in Mayfield.

• All content for the personality and sample entry in your app must be written or roleplayed by you; for the personality section in particular, we do not accept copied text from wikis or other sources. Obviously, you may not copy your app from other players, whether in Mayfield or other games. Application plagiarism will result in a ban from the game.

• If you wish for your character to be placed in a specific house, please mention this in the relevant section of the application and specify that permission was obtained by the PCs already residing in that house. We will be operating by the Honor System for this, and there is no need for others to comment their permission in this post!

• Other special requests would also best go in the beginning of the application. Remember, grammar and spelling are important -- if your app contains errors, you will be asked to revise.

• Please post all applications or canon updates in this post; posting them elsewhere and linking to them from here may cause them to get changed later. Posting them here keeps us from having to save them.

When Applying, Fill Out the Following:

Name: Not the character's name, but yours or however you'd like us to refer to you.
Personal Journal: If you have one; a journal on another website is fine.
Contact Info: Any other way of contacting you. IM screen names, e-mail address, etc. AIM appears to be the common link between most players, so having a handle on AIM is preferable.
Other Characters Played: Any other characters you play at Mayfield, if applicable.
Preferred Housing: We encourage random matches, but if there is a particular house you want, you will need to contact every person in the house for permission. Please post your app AFTER doing this. If you cannot get in contact with any one person, please wait a week after contact and we'll accept it as a good faith effort. It is not necessary for those you received permission from to comment; we believe you! If you have no housing preference, simply put "N/A".

Character Name: Names, nicknames, whatever is applicable. In western order, please. If the character has no last name (adult males especially), you are free to either make one up or let us do it.
Character Series: 
Character Age: 
Background: We will accept copy/pastes or links to Wikipedia or another source, provided that the source reasonably explains the canon. This section is necessary, so if you can't find an explanatory source, you'll have to write something up yourself.
Personality: The more detailed here, the better. This lets us get a good feel for the character. Please try to back up your details with canon examples when you're getting past their basic character and more in-depth. Generally, we want to see at least four good-sized paragraphs.
Abilities: This section may end up being optional for you. If your character has any abilities or powers, such as magic, they'll be taken away upon arrival in Mayfield. These will come back over time, though.
Sample Entry: Please write as if you've already been accepted and writing an ordinary post from your character during their stay in Mayfield. Using an "introduction" post is fine, but we tend to discourage it, as the typical "who am I where am I what is this crazy place" format doesn't really give us a good grasp of how your character will behave on a daily basis. If you have trouble writing sample posts, we allow links to museboxes or other RPs to demonstrate as a sample. However, you'll want to post with the account you'll be linking to in that situation. Please make sure that your app is written in first person (!!!), as that's the format that will be used in the roleplay. Generally, we want to see at least five sentences, if not more. Prose log style samples will not be accepted. If you're confused about the distinction, we will be happy to explain. Remember, we're looking for FIRST-PERSON format; prose narration is fine, but it cannot make up the bulk of the entry.

When Applying for an Original Character, Fill Out the Following

Name: Not the character's name, but yours or however you'd like us to refer to you.
Personal Journal:
Contact Info: Any other way of contacting you. IM screen names, e-mail address, etc. AIM appears to be the common link between most players, so having a handle on AIM is preferable.
Other Characters Played: Any other characters you play at Mayfield, if applicable.
Preferred Housing: We encourage random matches, but if there is a particular house you want, you will need to contact every person in the house for permission. Please post your app AFTER doing this. If you cannot get in contact with any one person, please wait a week after contact and we'll accept it as a good faith effort. It is not necessary for those you received permission from to comment; we believe you! If you have no housing preference, simply put "N/A".

Character Name: Names, nicknames, whatever is applicable. In western order, please. If the character has no last name (adult males especially), you are free to either make one up or let us do it. 
Character Age: 
Background: For OCs, we require a detailed background to be fully written out. Please make sure to describe both the character's specific, personal background, and the world the character is from. If it is exactly like the real world, you'll still need to describe the location and the specifics of the society the character lives in (also please note here that we no longer accept 'Canon OCs,' so if this world is not one invented by you, the character is not appable).

This section will need to be somewhat long; there's no specific length we want, but we want to have a very clear feel of the character's backstory, so that we can compare it to the personality section.
Personality: This section is probably the most important. We're looking for at least six or seven paragraphs, but what's more important is that this be comprehensive and detailed. We want to see what makes your character tick, and we want to see that you understand what makes them tick and have fleshed them out as a character. Some things we will need to see include their important relationships and the major events in their lives and how these have shaped them, how they tend to interact with others and the world around them, their strengths and weaknesses, and what motivates them, among others.

If we do not have a strong sense of personality or it doesn't seem to match up with the background or sample, we will not accept the character even if your writing is strong.
Abilities: This section may end up being optional for you. If your character has any abilities or powers, such as magic, they'll be taken away upon arrival in Mayfield. These will come back over time, though.
Sample Entry 1: We're looking for a first person sample here; prose or action log format is not acceptable. If you write a sample, please write as though your character has already been accepted and is in Mayfield. You may write an introduction or first post, but we tend to discourage this, as the typical "who am I where am I what is this crazy place" format doesn't really give us a good grasp of how your character will behave on a daily basis. You may also use a link to a post in a dressing room, another game, or a musebox. We're looking specifically for a clear sense of character voice; spelling and grammar are important, but showing strong voice and characterization is more important than anything else. Remember, we're looking for FIRST-PERSON format; prose narration is fine, but it cannot make up the bulk of the entry.
Sample Entry 2: In this sample, we'd like to see a different side of your character than we saw in your first sample. This sample also needs to be in first person, but you may do a sample heavily based on introspection and action as long as it shows us a different side of your character and your first sample was strongly focused on speaking voice. For this sample, we will ask you to write something out as though your character is already in Mayfield. Please do not link to a sample elsewhere or use their first post/waking up in Mayfield here. That can go in the first sample instead.

• Before applying, please look over any applications that were recently accepted to get an idea of what we're looking for.

• If you apply for a character that has already been reserved, we will inform you and ignore the application until the reserve runs out. You may not apply for more than two characters from the same canon. For the sample entry, you may write your own entry, or use a post from a musebox, dressing room, or other game. We recommend testrun_box if you prefer the latter!

• After you're accepted, please follow all of the instructions given. You will need to reply to the acceptance, post your journal to the friend add page and your canon post, join the communities, and use the friend add page to update your journal. Once you're accepted, please introduce yourself on the community when you're ready to play.

• If your app is "Pending", do not freak out! This means that we need you to make some revisions, and does not mean you're rejected. We generally give players a chance to revise before rejecting them, but we will reject apps that do not address the concerns stated when we asked for a revision. If you have been rejected, our reply will clearly state this to be the case. If we have not gotten back to you yet, under no circumstance does this mean you are rejected. If it has been over a week since our last reply, it would be a good idea to contact us with a reminder, otherwise, please be patient!

• If you have received a "Pending" notice, you will have one week to supply us with your revisions, or your reserve will be considered expired and that someone else is free to apply for the character.

• The typical wait for a reply on apps may be anywhere from a day to a little over a week. If any part of your application requires a pending, it may be another week after your reply to that before we can get to you. We process a high volume of apps every round, so please be patient.

• If you have not heard back on a pending for over a week after apps close, please send a PM directly to the mod account.

APPLICATIONS ARE CLOSED.

Flat | Top-Level Comments Only

Background: (Taken from Wookieepedia) HK-47 was a Hunter-Killer assassin droid and Jedi hunter constructed by the Dark Lord of the Sith Darth Revan shortly after the end of the Mandalorian Wars in 3,960 BBY.

In the wake of widespread destruction caused by the Mass Shadow Generator, a superweapon used during the final battle of that conflict, Revan was inspired to seek more subtle methods of defeating his enemies. HK-47 was sent throughout the galaxy on his missions and successfully assassinated countless targets whom Revan had deemed threats to galactic stability and peace.

HK-47 continued to serve Revan during the Jedi Civil War, a devastating conflict between the Sith Empire that Revan had created after his turn to the dark side, and the Galactic Republic. During this time, HK-47 helped Revan to locate the Star Forge superweapon and also assassinated beings who could potentially destabilize the galaxy, which eventually led to a mission into Mandalorian space in 3,957 BBY. While HK-47 was on this mission, Revan was captured by the Jedi after Malak turned on his master and fired a volley of turbolaser fire at the bridge of Revan's flagship.

The Jedi High Council ordered Revan's mind to be re-written, and the Sith Lord lost all the memories of his former self, including those of HK-47's existence. Meanwhile, although HK-47 succeeded in his assassination mission, his motor functions were damaged, and he ended up in the possession of a Mandalorian soldier. The Mandalorian reprogrammed and laid claim to the crippled droid, repairing him—though not particularly well in the droid's opinion—and began to use the droid to elevate his own rank by having him eliminate his superiors and clear the way for his own promotion.

HK-47 had lost much of his memory due to the damage he had received and lacked the knowledge as to where he had been created, though he believed himself to be of Systech Corporation's manufacture. Conversely, rumors circulated that his true creator was Czerka Corporation. All that remained was his affinity toward violence, although he could not recall why he had been equipped for such a purpose.

Eventually, the Mandalorian ordered HK-47 to assassinate the reigning Mandalore. HK-47 failed and was captured by his target, who reprogrammed his objectives to send the droid against his master. The Mandalorian soldier was subsequently terminated. Since HK-47 was programmed to shut down whenever his current master died, he deactivated himself after killing the Mandalorian and was sold to Bochaba the Hutt, a crime lord based on the planet Sleheyron.
HK-47 helped Bochaba to maintain his reputation as the most feared gangster on Sleheyron, terminating 322 targets in a single year before Bochaba was assassinated by his rivals. The droid shut himself down once again after learning of his master's death and was sold to a Human senator on the galactic capital of Coruscant. The Senator first assumed HK-47 to be a mere protocol droid, but one of his assistants later discovered the droid's assassination functions and asked the Senator to destroy him. The Senator instead ordered HK-47 to kill the assistant, and the droid remained with his master, helping him eliminate his political enemies. With his rivals quickly being eliminated, the Senator was on his way to being elected as the Supreme Chancellor, but things did not go as they had been planned.

The next target the Senator ordered HK-47 to kill was his own wife, who, as he had discovered, had been cheating on him. As HK-47 approached the wife and her illicit lover to terminate them both, his master suddenly regretted his order and dove between the droid and his intended victims. Having accidentally terminated his master, HK-47 had no choice but to shut down once more. The Senator's wife later sold him to a low-ranking commercial officer of Systech Corporation. At first, the officer used HK-47 as a protocol and bodyguard droid, but following his discovery of the droid's assassination protocols, the officer sent HK-47 on a mission to eliminate workers of a company that was developing a product which, if launched onto the market, would ruin the officer's career. The officer did not realize that the company was, in fact, another branch of Systech Corporation. By the time he realized his mistake, HK-47 had already terminated 104 Systech employees. HK-47 assumed that, being the only officer remaining, his master would be promoted. Instead, the officer, in dismay, attacked the droid. While doing so, the officer pierced one of HK-47's actuators with a writing utensil, resulting in an electric shock that killed him and damaged the droid's assassination protocols, again forcing the droid to deactivate himself for killing his master.

After the accident with the Systech Corporation officer, HK-47 was sold to Yuka Laka—an Ithorian droid dealer at the Anchorhead settlement on the planet Tatooine—who fitted him with a restraining bolt, further restricting the droid's memory and his protocol and assassination protocols. There, HK-47 encountered his original master, Revan, whose mind had been erased by the Dantooine Jedi Enclave Council after being injured at the hands of Darth Malak. Revan was once again trying to find the Star Forge and was looking for the Star Map, an ancient artifact located on Tatooine. This time, Revan was acting on behalf of the Jedi Council in order to locate and destroy the superweapon and save the Republic from defeat. Revan purchased the droid for his knowledge of the Sand People dialect, as he intended to negotiate with the local chieftain about ceasing attacks against Czerka Corporation personnel and could not understand the dialect himself. HK-47 eagerly accompanied Revan, as he disliked Yuka Laka, and acted as a translator when Revan met with the chieftain of the local tribe.

In keeping with his violent programming, HK-47 advocated for simply eliminating the local tribe, but Revan opted for a peaceful method and managed to gain entrance to the Sand People Enclave by using disguises taken from fallen Tusken Raiders. Revan was able to successfully reach an accord with the chieftain by trading two moisture vaporators he had bought from the Czerka outpost so that the tribe could journey farther away from the settlement and cease their constant raids. As a sign of appreciation, the chieftain gave Revan his personal gaffi stick as well as a map of the area of Tatooine where the Star Map was located. At that, HK-47 expressed his disappointment at the loss of a chance for combat against the Sand People. HK-47 was present when Revan was allowed to meet with the Sand People storyteller in return for presenting the chieftain with a krayt dragon pearl. HK-47 translated for this meeting as well, cautioning Revan against making any potentially offensive statements.

When Revan later asked HK-47 about the droid's past, he was quite taken aback to discover that the droid had, indirectly or otherwise, been the cause of death of all of his interim owners. This did not stop Revan from making multiple repairs to the droid, despite some trepidation on HK-47's part. Revan eventually restored everything but HK-47's memory core, which was too fragile to attempt to repair manually. Revan later encountered Malak for the first time since his former Sith apprentice had betrayed him.

This meeting proved to be the stimulus necessary for Revan to remember the truth about his own history. It was also the signal for HK-47's internal programming to unlock and undo the damage to his primary memory core, allowing the droid full access to his entire memory as well as his entire combat and assassination protocol package. HK-47 appeared more than satisfied to be reunited with his master, but later commented that Revan had changed since he had last served him, stating that Revan was more compassionate than before. Despite this, the droid still believed that Revan was just as capable of merciless and necessary actions when required. The droid also expressed his alleged frustration and rage at being absent during Malak's betrayal and his inability to defend Revan from Malak's treachery.

HK-47 remained with Revan until the end of the former Dark Lord's journey, following him to the Star Forge and aiding in the destruction of the superweapon as well as the defeat of Darth Malak. HK-47 was honored with Revan's other companions as a hero of the Republic and was awarded the Cross of Glory beside them. Shortly thereafter, more of Revan's memories returned, and the Jedi recalled a threat to the galaxy that he had uncovered as a Sith Lord. HK-47 was left behind with Revan's wife, Bastila Shan when he departed for the Unknown Regions. Revan also had HK-47's memory of the past four years erased so that the droid would not discover his destination. For a short time, Shan left HK-47 with the Jedi Council on Coruscant, hoping his murderous instincts might be calmed.

However, HK-47 was unwilling to stay and wait for his master to return, and when Bastila refused to tell the droid where Revan had gone, HK-47 left to find him. During the droid's attempt to locate Revan, HK-47 was once again heavily damaged and almost entirely dismembered. HK-47's remains were later discovered by one of Revan's other droids, T3-M4, who recovered HK-47 and stored the remains onboard the Ebon Hawk.

Applications

Re: HK-47 | Knights of the Old Republic | Not reserved (2/5)