Rules of Combat

Combat Role-play
Combat Role-play can be used for many activities that go on within and even outside of your village. It is used when we spar, when we fight to the death, and even in special events such as matches. These are the rules of said combat as follows:

attack in your entrance post, you will automatically be either disqualified, or lose the match. It does depend on the circumstances; however, you will lose the match either way. properly. You cannot say you just simply dodged your opponent's attack because you can. If it comes to the proctor's attention that you are being unfair with evasions; you will be asked to repost by a proctor. means your rpc is allowed one movement towards, away, or whichever direction you wish to move your rpc within that post.
 * 1) There MUST be a proctor present for all GENIN  and CHUNIN  spars, deathmatches, and missions.
 * 2) There are to be NO attacks in the entrance post. If you
 * 1) Each post is allowed to be made up of 2 attacks. This means your rpc is allowed 2 combative attacks upon your opponent.
 * 2) Each post is allowed to be made up of 2 deflections. This means your rpc is allowed 2 evasions. Do understand that your rpc MUST dodge
 * 1) Each post is allowed to be made up of 1 movement. This

Role-play Lock Edit

 * The Explanation

When someone is in a training session, they generally cannot progress in the storyline until their training is complete. This also goes with Combat, Spars, Story Progression, Casuals, and anything else that takes part in a role play.


 * The Guidelines

training, or self-training; you are not allowed to move on to another roleplay session until that certain session is completed. You are allowed TWO '''open roleplay sessions. ('''By two role-play sessions, we mean one casual and one training, mission, self-training, etc.) roleplay session with an inactive roleplayer, the inactive roleplayer will have (3) days to reply to the session or the session will be voided. Please also notify a council member if this situation occurs.
 * 1) If your rpc is involved within a spar, mission, casual,
 * 1) If you become stuck in a situation where you are involved in a

NOTE: The reason we choose to enforce role-play lock is because we want your rpc to have a steady progession in their storyline. There is also a possibility of your rpc being caught up in various sessions, and if something happens to your rpc; the other person's involved in that session would have to have a session voided. Since you would not be able to reply to the roleplay session within the specified time-frame. Please understand the necessity of such a rule. If you have any questions or concerns, please bring it to the council.