 |
T1 Rules
Rules of T-1 Roleplay
Rule 1: All attacks should be done in "attempt".
Here is an example of IMPROPER T1 etiquette:
Jim replied to John's post:
Jim got off the ground after John's punch. He ran at John and threw a fist at John's face. He heard a crack as John's cheekbone broke.
^ This is a form of "godmodding." Due to Jim's post, it is impossible for John to dodge the attack or have any way of lessening the damage. Auto-hits are not part of T1 role play and in battle will result in an automatic disqualification. Sometimes you may be asked to re-do the post. (If you're lucky)
Here is an example of PROPER T1 etiquette:
Jim replied to John's post:
Jim got off the ground after successfully being hit by John's punch. He ran at John and began to throw a punch towards John's right cheek.
^ This is a good use of proper T1 role play. Notice how Jim never said that his punch connected with John's face. Jim said that his punch was going "towards" John's face. This allows John some options in his next post.
Rule 2: Use details.
Here is an example of IMPROPER T1 etiquette:
Jim posted:
Jim threw a punch at John.
John posted:
John dodged.
^ Both role-players did not use proper T1 etiquette. Notice how Jim only said that he was going to punch John. And then all John said was that he dodged. More descriptive features are needed to make the role-play more interesting and to avoid god-modding.
Here is an example of PROPER T1 etiquette:
Jim posted:
Jim's left leg bent forward while his right leg straightened behind him, his feet were firmly planted on the ground as he began to throw a right punch towards the left side of John's face.
John posted:
As Jim's punch came toward him, John bent his knees and ducked while moving his head right to avoid Jim's fist.
^ These posts are neither god-modding or ill-described. Both role-players used details to describe how they moved. Notice how Jim described which hand he was using to punch at John, and where he was going to punch. And John described how he dodged the attack instead of simply saying, "John dodged." Not only is this good T1 role play etiquette but it is also more interesting to read and gives the reader a good picture of what is happening.
Rule 3: Taking Turns
T1 role-play includes the role players to take turns as they post. Whether its 1-1, 3-1, or 3-3, the role-players' turns should be set before a match and each role-player should know who they post after and who they post before.
Here is an example of IMPROPER T1 etiquette:
John posted:
John stood, waiting for Jim to make his next move.
Jim posted:
Jim ran towards John and began to punch towards his face
Jim posted:
Jim then began to kick towards John's side.
^ This is unacceptable in T1 role-play. Jim posted twice without any regard of what John could do after Jim threw a punch towards him. If John dodges both attacks, Jim may accuse him of god-modding when really, Jim is the god-modder.
Here is an example of PROPER T1 etiquette:
John posted:
John stood, waiting for Jim to make his next move.
Jim posted:
Jim ran towards John and began to punch towards his face
John posted:
John brought his arm up in front of his face, successfully blocking Jim's punch.
Jim posted:
Jim then attempted to kick to John's side.
^ Jim and John have successfully taken turns in their fight. Neither one has posted twice in a row and therefore, neither one can be accused of god-modding.
Rule 4: No Overpowering
Here is an example of IMPROPER T1 etiquette:
Jim posted:
Jim laughed as John was on the ground. Jim was charging an enormous amount of energy. He then shot his "Super-Ultimate Apocalypse Blast" capable of destroying the entire world.
^ There is no way for John to stop the blast or dodge it without being a god-modder either. Attacks that either cannot be dodged or blocked or can destroy an entire village or planet are god-modding techniques and are not allowed in role play.
Note: Any form of attack is god-modding if it can't be dodged if it makes the user invincible if it destroys such a vast area that it's inescapable.
One-shot kill techniques are not god-modding as long as the target is able to dodge or escape in some manner.
Here is an example of PROPER T1 etiquette:
Jim posted:
Jim charged a large amount of energy. He shot the blast towards John. The blast is capable of covering about a 50m radius.
^ The attack is not a god-modding technique in T1 role-play. It is possible for John to get out of the blast's range without god-modding.
Hints for Quality Role-Play
1.) Try not to make a post that short. Short posts tend to contain little to no detail and is not good in making role play interesting. Quality role-players will find short half-line posts bothersome.
2.) Keep your attempted hit until the end of a post. Try to describe in the beginning of a post all your motions and attempts at confusing your opponent before you begin your attack. This will allow the reader to find interest in your posts. Seeing how you use intelligence and speed instead of sheer force.
3.) Avoid what I call "Pokemon Role Play." When using jutsu, describe what your jutsu is doing and do not use auto-hits or simple "you missed" or "I dodged" posts like as if it were a Pokemon game. Remain detailed in all your posts. A bad example is something like:
"I used Fire Style: Great Fire Bomb and you burn to ashes."
UNACCEPTABLE.
4.) Use 3rd Person Role-Play. Avoid using terms such as "I" or "We." 3rd Person role-play tends to be more popular and makes it easier for a role player to describe things such as a character's background story.
5.) Try "Organizing" your posts. Popular ways of organizing posts include: bolding quotes, using colored fonts when using jutsu, aligning posts center, making the font size smaller, and italicizing when posting the past or future.
COMBAT REGULATIONS - Every action that is neither melee or an inherit skill must be prepped at least once before an actual attack is issued.
- There are no exceptions to this rule.
- Any user may use their character to attack any other user's character without prior indication as long as the aggressor remains within his character limitations and is aware of the placement of the character they are aggressing.
- Exception #1: The attacking user attacks without entering the RP environment.
- Exception #2: The attacked user is:
a): Away.
b): OOC.
c): Hiding.
- Every attacking action has two or more counterparts. The first, although sometimes unnecessary, is the move where the spell is either charged or prepped (this could span several action sequences, building in power.). The second, always necessary, is the actual attack where an attempted strike at the combatant is made. The last is the resolution of the attack, wherein two things may occur.
a): The attacked states the hit, commonly removing the opportunity for user to state the cause and affect of the attack.
b): The aggressor states the hit, themselves stating the cause and affect. - Exception #1: The attacked dodges, the attack continuing without striking its intended target.
- Exception #2: The attacked reflects the attack, whereon they become the aggressor.
- Exception #3: The attacked blocks, the affect of the attack removed to another object.
- Exception #4: The attacked nullifies the attack, it ending abruptly.
- Exception #5: The attacked creates a diversion, confusing the object of the attack, thereby prolonging the hit's progression.
T1 CONDUCT REGULATIONS - All action sequences should contain clear and concise language. Not only that, but they should be descriptive and enjoyable to read. I find it very frustrating to read ill-formed paragraphs that are designed merely for the purpose of boggling the reader due to their cryptic language, repetitious patterns, and reproachably poor grammar. For those who honestly cannot spell or form sentences, get some form of spell checking and grammar correcting device! This is turn-based RP, not a race. There is ample time to correct errors made and proofread the paragraph if everyone is following the rules. Even use a thesaurus if you don't know what word you want!
- This requires no exceptions.
- The goal is not to evade every hit, and hit every time. The goal, in well-formed turn-based style RP, is to RP out the character. If a user can dream up a way out of the move, and their character cannot do it, then they should not do that move. It is impossible for me to stress the importance of playing the character to play the character, not to win.
- This requires no exceptions.
- When a user inadvertently has a flaw in their action sequence regarding the where-abouts of another user character, or any other matter concerning the character; the user should not start an argument over this. Instead, the user should, in their action sequence, generate a very clear correction of the situation. If the former user picks up on this and requests a repost, that is up to the users to decide; but, it should be denied --confusion does happen during a battle.
- This requires no exceptions.
- If it is found a user is acting outside their character limitations that user automatically loses the fight in dishonor.
- There are no exceptions to this rule.
Just a Friendly reminder Rp is supposed to be fun.
|