Shinobi Legends Forum - Shinobi Legends Game Site

Please login or register.

Login with username, password and session length
Advanced search  


Ever wondered if your ideas have been talked about in the forum already? Well, try out the "search" option, where all your questions can be answered.

Author Topic: Current Biju Rules  (Read 642 times)


  • Moderator
  • Hero Member
  • *****
  • Karma: +100/-100
  • Offline Offline
  • Posts: 3469
    • View Profile
Current Biju Rules
« on: March 19, 2017, 03:17:33 pm »

Current Rules as of: June 16, 2017.

Bijuu Rules and Guidelines

1] Forum Account and Challenging the Host
  • A host must have/create an SL forum account.

  • Challengers will also have/create an SL forum account.

  • Challengers and hosts may have more than one OOC match going on at the same time.

  • A single player challenger may issue 3 challenges at a time.

  • A host must create a thread with the name of his or her bijuu in the title to the Bijuu Arena board, and use this thread to: state his or her preference for battle, keep a list of challengers, indicate if he or she is a new host and when his or her grace period will be over, and post any notices of absence.

  • Hosts are required to specify whether the character with the beast is a summoner of the beast or a host to the beast in the appropriate challenge threads.

  • A host cannot be challenged for his or her biju until after his or her 14 day grace period is over. After a host's 14 day grace period has ended, a challenger posts/issues a challenge to the host of preference as a reply to the thread of that particular beast for which they are interested in competing. The challenger must post to the host's preference thread to make a valid challenge. The host should also be notified by the challenger via SL PM (Shinobilegends Personal Message) that the challenger has issued a valid challenge.

  • After losing a challenge, the defeated challenger may not challenge the same host for the same beast for 3 months. However, he or she may challenge this same host for a different beast in his or her possession without waiting.

  • Challengers must check forum host preference threads to stay informed of the current status of the host.

  • After arrangements have been made between the host and challenger, a post to indicate what terms have been accepted will be made to the host's thread.

  • Challengers must also post a notice of absence in the thread of the host they are currently combating and/or challenging.

2] Activity Clause and Biju Match Time Restrictions
  • The purpose of making a notification of absence post is to permit life to happen without wrecking your participation in the bijuu activity, while making it clear that there will be punishments for those who abuse this leave of absence, like forfeit of match, loss of biju, and bans pending a review by the council.

  • Hosts must make a RP post in public once every 14 days while not engaged in an active challenge. Hosts who fail to do this will have their bijuu stripped by the council.

  • Extenuating circumstances during the 'idle phase' of a host: Most events occur so as to permit making a post at some time during your 14 days to alert the community that 'something' is going on. Your leave of absence notice will reset the clock to a 14 day absence max. Should you need more time than that...which adds up to possibly a whole month if your notice occurs on day 14...then you will step down as a host and try again later when your life will permit participation again. You will not be banned from challenging someone for another bijuu. But the SL community will be permitted to move on. The council will handle requests for concessions on a case by case basis and their decision will be binding.

  • The challenger and the host have 1 week to set up and begin their biju match.

  • Challengers should notify the host of forseen inactivity via SL PM, the host's preference thread, and, if applicable, the forum match if the match has already started. After 14 days of a notified inactivity, challengers will bow out gracefully and may challenge this host for this bijuu again after 3 months. 

  • During a match, hosts and challengers must make a post to the match once every 7 days.

  • A Host or Challenger who fails to make a post to the RP match once every 7 days, without posting a notice of absence to the forum host thread in question, will forfeit the match. During this forfeit, the bijuu will either remain with the host, in the event of challenger inactivity, or be transferred to the challenger, in the event of host inactivity.

  • Extenuating circumstances during an active match: Here the activity clause is 7 days, in order to keep the fight moving along to a conclusion. Posting for a leave of absence is essential to holding your slot in the match. Should this not be possible, the council will determine how to handle the situation at the time of your return upon request dependent upon a challenger waiting list, if the beast has already been transferred, or how it impacts current RP. All decisions of the council will be binding.

  • OOC matches are 1v1. Preferences can alter this upon agreement of all parties involved.

  • Cool down periods are an optional break from back to back fighting in order to permit the host to heal and train with his or her beast. As such, a cool down period can only be announced after the successful conclusion of a match, and is not intended to serve as a general leave of absence. Should a host opt to take a cool down period, this may last no more than 7 days and must be announced with dates of duration to the host's forum thread for each beast that player hosts. A cool down period from one beast a player hosts cannot be applied as a cool down period for all beasts under his control but must be bijuu specific.

4] Mastering a Biju Clause
  • The beast must be completely mastered before the Jinchuriki can access Tailed Beast Mode. 

  • The Bijuu Bomb can only be used while in Tailed Beast Mode.

  • If a host goes over their mastery for any reason at any time during a biju match, it is considered an automatic forfeit by the host.

  • The Bijuu’s passive ability can be accessed immediately upon being sealed with the beast, but the power will be weaker than someone who has mastered the beast. It takes time to master the passive abilities of a bijuu. 

  • Players' characters who has previously mastered a biju may retain the passive abilities of the previously mastered tailed beast.

  • If a player has previously mastered a tailed beast, then they are permitted to have a 3 week re-mastering period in place of the normal mastering period only on the character that previously mastered the beast. 

  • Mastery will occur in five stages consisting of 3 weeks each, with a mid range evolution stage to access partial transformations:

                    - 25% grants access to C ranked jutsu in the beast's passive ability. The host has access to the Initial Jinchūriki Form.

                    - 50% grants access to B ranked jutsu in the beast's passive ability. The host has access to the Version 1 Cloak.

                    - Mid-range EV grants control over the transformative stages now includes the finesse to perform partial transformations.

                    - 75% - grants access to A ranked jutsu in the beast's passive ability. The host has access to the Version 2 Cloak.

                    - 100% - grants access to S ranked jutsu in the beast's passive ability. The host has access to Tailed Beast Mode. The host may also combine biju chakra with senjutsu and use Amphibian technique and similar techniques to merge with a summon in order to maintain sage mode.

5] Bijū Summons
  •   A Summoner is bound by the same rules as Hosts in regard to challenges and activity unless otherwise stated.

  •   Summoning Tattoo: The Summoner will be marked with a tattoo, through which they call forth the bijū for use. This Tattoo counts as a bijū chakra signature which can be detected through the sames means as if the beast were sealed within a host and is subject to the same restrictions against metagaming during a RP hunting event.

  •   Chakra Cost: Bijū cost 20% of the user's total (not current) chakra to summon, even in succession.

  •   Controlling Mechanism: Bijū must be under the influence of genjutsu at all times while used as a summon. Regardless of the genjutsu's potency, it will tax 5% of the summoner's total (not current) chakra while it's actively being used as a summon, the taxation only ceasing when the bijū has been removed from the battlefield.

    Techniques capable of transferring chakra from the bijū to the summoner are strictly prohibited from being used in this context, and summoned biju will not willfully transfer chakra to any of the summoner's allies, and moves to take it by force will result in the tailed beast resenting its summoner.

     Outside of battle or training, summoned biju do not continuously drain the user's chakra.

  •   Severing the Summoner's Control: Acceptable means for attempting to sever ties between the Bijū and summoner include dismantling through means of a contract seal via touch attack or dispelling the genjutsu [cost is 20% of your chakra]. For Bijū controlled by means of  Rinnegan users, the chakra rods have to be extracted in addition to dispelling the controlling genjutsu. Success results in a rogue Bijū situation and will yet need to be subdued.

  •   Restrictions: Player character summoners are reduced to 2 actions per post while the biju is summoned and under their control. If control is lost, then the restriction is lifted until control is regained.

  •   Bonding: Summoned beasts will no longer infinitely hate their summoner, but will not bond with their summoner as much as a sealed biju bonds with the host. Something to do with not being as close as a breath.

  •   The tailed beast must be "located" somewhere in the physical world when it is not summoned by the host; the beast cannot be in a pocket dimension while not summoned.

  •   Death of Summoner: If the summoner dies while the bijū is unsummoned the challenger/hunter will transfer the summoning tattoo to themselves.  However, if the summoner dies while the bijū is summoned then the challenger/hunter can attempt to capture and subdue it, in the event that the beast has not already been captured prior to the death of the summoner. Now, if the summoner is also a host, and dies, the hosted bijū will respawn in 7 days at the location of the host's demise: the bijū will be GM'd by someone of the council's choosing.

  •   There are no prohibitions to enhancing a summoned bijuu.

6] Judging a Match
  • Both parties choose a judge and abide by their decision.

  • In the unlikely event of the gross incompetence of the judge, both parties must agree upon a new judge and this second ruling shall be the final word for good or for ill. 

  • After agreeing upon a judge, if he or she then gives a ruling that you find to be in error, the participants can agree upon another judge to settle the issue. If a second judge is requested his or her word will be final. No additional replacements of the judge will be possible and the new judge will be responsible for settling disputes for the remainder of the match.

  • No unresolved issues will be tolerated. Compromises must be made in the event of a deadlock. Failure to come to terms after every option has been exhausted will result in a stripping, challenger forfeit, and the bijuu handled according to the Stripping Rules. Both challenger and host will be denied access to all things bijuu for 3 months due to gross incompetence.

  • Council members are ineligible to be chosen as judges.

  • Attempts to commit fraud by providing a judge who is an alt [for your own match] by either party will result in a perma-ban of all things bijuu.

  • Judges will acquaint themselves with the rules of all things bijuu, the preference list of the host, the terms agreed upon by the participants, and commit to activity.

  • Judges may have to play crowd control in the event of a public, verbal, and abusive fight. In the event of such an issue, the judge should make one post requesting that this behavior cease, to arrange to mediate between the parties in private, and place the match on hold. Should this warning/request be ignored, the judge should refer the matter to a site Mod/staff and not be drawn into participating in such behaviors.

7] Stripping a Host
  • Breaking the activity clause constitutes stripping. You may participate again once your life permits the time commitment SL requires of their hosts. No ban is issued and when to try again is up to the participant.

  • Attempting to commit fraud by providing an alt as a judge to your own match results in a perma-ban from all things bijuu.

  • Breaking any of the other rules results in one warning to be issued by the council. A second violation of the same rule will result in stripping.

  • Hosts who are stripped will be on a 3 month cool down period in which they may not participate in bijuu matters, but can serve on the council. During this time it is hoped they will train and refine their RP/participation in order to become a host in the future. This cool down period does not apply to breaking the activity clause.

  • 14 days after stripping a new host must be chosen.

  •   7 days after host is chosen an RP to seal must be completed. OOC sealing must be completed within 2 days of being chosen. If the RP exceeds the 14 days, the host must default to OOC sealing and post his grace period dates immediately.

  • In the event that a host/summoner is stripped during a match, the beast goes to the current challenger.

  • In the event a host/summoner is stripped outside of a match, the beast goes to the first challenger on the host's challenge list.

  • In the event that a host/summoner is stripped, and no challenger exists, the bijuu council determines how to handle the reassignment of the beast in question.

  • When the Bijuu Council is called upon to assign a new host, the Bijuu Council can handle the reassigning of the bijuu in any manner they agree upon. Some ways they might to choose, for example, might be: Assigning to a new host they all agree upon, Asking for volunteers, Calling for a GM to host an RP for a wild bijuu hunt, Host a lottery of applicants [meeting in a paid zone and using the random die generators], or a tourney[not to exceed 2 months from start to finish]. However, judging the tourney matches will default to judge rules. Council members may not serve as judges.

  • A GM rp led event must begin no later than 2 weeks after it is called for and be concluded within 2 months of its beginning. Additionally, any SL GM staff who are trying to be hosts may not participate in aspects of a wild bijuu hunt but rather must confine themselves to being a contestant.

8] General Information
  • The maximum number of Bijuu a player is allowed to capture and hold onto is no more than 3.

  • Using Telescope Technique to circumvent the quest of seeking out *any* Jinchuuriki is not permitted.

  • The challenger list of the former host/owner is inherited by the new host/owner of a bijuu. You may still take the 14 day grace period before beginning discussions on setting up your first match even though your new bijuu comes with challengers.

  • If a biju is gifted, then the gifter's grace period, if the gifter is still within one, is transferred to the new owner without any extensions or reductions in time. If outside the grace period of the gifter, then a 3 days grace will be given to the receiver.

  • Player characters are not allowed to host multiple biju.

  • Tailed Beast chakra cannot be split in a fashion that creates psuedo-jinchurikii or multiple jinchurikii. In other words, no division into Yin-Yang, gifting of the biju chakra like Sora or Naruto in the series, and no Gold and Silver Brother shenanigans, etc. 

  • Biju Tournaments and FFA are required to have a honor system that all participants are bound by, with punishments enforceable by the Biju Council.

Bijuu Council Rules and Guidelines

1] The Bijuu Council will consist of 7 members.

2] The ratio of jinchurikii to non-jinchurikii will be 2:5. 

3] Council Member elections will occur every 6 months.

4] Hosts who have been stripped are eligible to run for a council seat.

5] If the number of Candidates is equal to the number of Council Members possible, then the Candidates will be automatically appointed.

6] Council Members cannot be judges for Bijuu matches.
« Last Edit: June 16, 2017, 01:51:27 pm by Eric »
Anything you can think of I can't think of, let me know; that's how the sharing circle works.


  • Moderator
  • Hero Member
  • *****
  • Karma: +100/-100
  • Offline Offline
  • Posts: 3469
    • View Profile
Re: Current Biju Rules
« Reply #1 on: May 26, 2017, 12:47:14 am »

IC Hunt Rules


Action: An action is anything that would require one turn in the shinobilegends game to do.

         -For example, most jutsu in SL require one turn to utilize, so jutsu that require no more but handseal preparation beforehand are counted as a single action. Those that require previous jutsu to be activated first, in order to be completed in total, the total action count is the sum of all of the moves required to activate, the activation move, and an additional move to maintain the technique if desired. Examples: summoning Shima and Fukasaku and then using Senpo Goemon are two separate moves, so 2 actions required to use Senpo Goemon if Shima and Fukasaku have to be summoned. Action count does not take into account the time required to do each, so while in-game  a player summons Shima and Fukasakua, activates Magen: Gamarinshō, and the effects are instant, in actual RP a certain amount of time has to pass before this particular jutsu takes effect, so the player must maintain the technique past its initial activation for however long is necessary.

        -"Basic" maneuvers and attacks, as a group, require one action. In other words, a player who climbs a tree by jumping from branch to branch has only done one action, while a player who twirls and then throws a hiraishin marked kunai to the top of the tree and warps to it using hiraishin has done 2 actions.

Character Controlling: Any strategy, action, or method used In Context (IC, RP, etc.) which both controls another players' character without their permission and transcends the prescribed ruleset that players determine the fate of their own characters based upon the roleplay that the character is in or agreed upon secondary elements such as judge and GM decisions.

Biju RP Game-Master: A player or set of players that control the non-player elements of the roleplay (NPC's, natural weather, rogue tailed beasts, etc.) and are responsible for keeping the roleplay focused and in order. Shortnamed "BGM", this role is not to be confused with the staff Game-Masters, whose RP responsibilities encompass all of the realm's RP and are expected to take punitive action towards players violating game rules and disrupting the peace of the site. Staff Game-Masters may take on this role and thus perform both their normal duties and the biju RP GM duties.

God-Modding: Any strategy, action, or method used In Context (IC, RP, etc.) which goes beyond the agreed upon limits or environment set by the narutoverse inspired shinobilegends world. This includes breaking SL RP rules.

Hunted: A jinchurikii or biju summoner in the RP

Hunter: Anyone who seeks out a jinchurikii or biju summoner with the the intent of taking the tailed beast.

Judge: A player or group of players agreed upon by the participants in the RP to preside over the entire RP in order to settle disputes and make decisions about the outcome of the roleplay, usually when called upon by at least one player. These decisions are non-negotiable, and support the GM in making the battlefield status update.

Metagaming: Any strategy, action, or method used In Context (IC, RP, etc.) which uses external factors to affect the game. Examples include viewing someone else's RP or reference information and attain knowledge which the player's character would not know otherwise, or to determine the outcome of a RP event based on the players themselves and not the situation that the players' respective characters are in.

Neutral: Any individuals that do not fall under the other categories described in terminology, such as bystanders and those not involved in the RP at all.

Support: Any individual who directly provides aide to either the Hunter or the Hunted. It is expected that they have fewer stakes in the success or failure of the mission.

Rogue Beast: Any tailed beast that is not controlled by a player character or sealed. It is a free range beast that will resist any attempts at subduing it.


Special RP rules for jutsu and techniques

Edo Tensei:,7768.msg210235.html#msg210235


* Anyone with Rinnegan cannot also use sage mode. The player must pick one or the other. Similarly, someone with sage mode cannot use rinnegan.

* Telescope technique cannot be used to discover jinchurikii/beast summoner locations.


Biju IC Hunt Specific Rules

---------- During the RP Hunt, neither a hunter nor the hunted can enter a place that bans the presence of biju, such as Kirigakure. Additionally, if a fight is a part of the Hunt RP, then the fight is forbidden from taking place in a heavily populated RPing area such as the village boards, and must be conducted outside of villages, clan halls, etc. In short, it must take place in the zones with no more than the Hunter, Hunted, BGM, Judge and Support posting anything related to the RP itself.

---------- The general flow of the RP will be charted out by the Hunter, the Hunted, a BGM, a backup BGM, and a Judge. The goal is to create a reasonable RP scenario where the Hunted and the Hunter at some point confront each other in some shape or fashion (it does not have to be a battle, but that is the most common direction for "confrontation"). The RP should take into consideration the desires of Support, and the discussion should take place on the forums and in public. The group has 2 weeks to setup and agree to the terms of the RP.

---------- Once the RP scenario is devised and hashed out, the RP should begin as soon as possible and follow the mapped out scenario as closely as reasonably possible. If adjustments need to be made for other events in the realm (massive war, anther biju hunt crossing paths, etc.) then these changes should be posted to the thread where the scenario was discussed.

--------- The judge has the final word on RP outcomes, but violations of biju rules may have a ruling appealed to the Biju Council.

--------- All players (including active BGM) have a 96 hour or 4 day post time, whichever is longer, whenever it is his or her turn to post. If a BGM or judge fails to post as needed during this time, then they can be replaced by another candidate of the Hunter and Hunted's choosing, starting with the replacement BGM. If a Hunter or Support fails to post on time, then their character is, at the determination of the judge, is considered captured, killed, considered having fled from battle, etc. If the Hunted fails to post on time, then they will either be considered captured, beast extracted, beast stolen, etc.


The Order and Flow of Biju IC Hunt:

------- Player characters may use up to 3 actions, all clones of a single character share a 1 action limit, and all summons share a 2 action limit. Special rules such as the Edo and Biju summoning rules trump the action limit rule when applicable (for example, a biju summoner can only do 1 action according to the Biju Rules, and the biju can only do 2 actions).

------- BGM's will always make the first post establishing the environment, while all other players will take turn posting in the order in which they made an entry post into the area or zone. Participant characters (including rogue biju and NPC elements) are not allowed to attack on the entry post, nor are they allowed to permanently leave the RP nor fight by any means. Any time spent in pocket dimensions and other such places must be kept to a maximum of 5 non-consecutive turns ( 1 action entering and 1 action leaving) for the entirety of a RP.

-------- Each round consists of each player's turn, which consists of a specific player's actions in the RP. At the beginning of each round, the BGM will post an "update" to the environment in order to facilitate a unified image of the battlefield. If required the judge and the BGM may work together to make sure that the intended post is accurate and, if judge rulings were made, that the consequences of said ruling are incorporated into the post.

--------- Discussions regarding the RP should take place in an OOC board (on SL) or in a separate thread from the fight (SL forum). It is every players' responsibility to maintain order and decency in the thread. Insults should not be present, even passive aggressively, and all players are encouraged to report any behavior that he or she considers disruptive to Staff (even if it is one of the Staff doing the action).

--------- Because of the great length of time it may take for a RP of large amounts of people to get done, there can be no more than 4 participants (excluding judge and BGM) in an IC biju match at this time; a Hunted, a Hunter, and 2 Support for either side. This may seem very small, but arrangements should be made in the beginning to keep the player count small. Players are forbidden from having IC matches with themselves for any reason, and players that are discovered doing this will be permanently banned from all things biju indefinitely, their beast stripped and delivered to the Council.

--------- Players cannot hunt and capture a biju IC outside of a biju hunt. If the host is killed in a RP unrelated to the biju hunt, then the biju will go to the Biju Council. There are no guarantees that the biju may go anywhere else after that (IE, challengers who challenged for a biju OOCly or IC hunt do not necessarily get first picks if this happens), but the Council must grant the biju to a player no later than 2 months after the biju first gets into its possession, unless a tournament or other event is on-going for the beast.

***** Metagaming, Godmodding, and Character-Controlling are forbidden at all times. *******

Anything you can think of I can't think of, let me know; that's how the sharing circle works.

Page created in 0.058 seconds with 19 queries.