This document is outdated! For Tree challenges beginning on 3/22/2022 or later, consult the MK IV document.
Battle Tree Signups
Battle Tree RP Tables
Ref Rules:
The ref is never obligated to interact with content that makes them feel uncomfortable. If such a case occurs, either work out the issue with the challenger, or privately message the Tree Head (nightblitz42) to have the issue resolved on a case-by-case basis.
Challenge Preparation:
After you have a agreed to ref a challenge, secretly take these preparatory steps:
Finally, give yourself one (1) Mulligan Token. At any time before or during the challenge, you may (secretly) spend the Mulligan Token to perform any one (1) of the following actions:
Challenge Structure:
After you have taken all the preparatory steps, the challenge proceeds as follows:
Roleplay Segment Expectations:
The Scenario and the pre-challenge preparations you have made will provide simple “blueprints” for most of the basic story elements. The referee’s job is to add details to these blueprints with the goal of establishing narrative cohesion. Within the Roleplay Segments, the ref has the freedom to add details to the story however they please (adding new characters, locations, events, worldbuilding, etc). However, they must always abide by the following narrative rules (in addition to standard rules of decency):
Each Roleplay Event describes to the ref, in very general terms, an obstacle that the challenger must overcome (for example, “The challenger’s team must cross a large chasm”). Sometimes the Roleplay Event also specifies a specific goal that must be achieved. At the start of each Roleplay Segment, the ref writes up a narrative (at least 1 paragraph), adding details to the blueprint in order to fit the story and setting.
The challenger must respond with a Solution. The challenger's Solution is their plan for overcoming the obstacle. In order to be valid, the challenger's Solution must make use of their Pokemon according to the following guidelines:
Battle Tree Signups
Battle Tree RP Tables
Ref Rules:
- You must be approved as a Tree Ref to ref this facility. If you are interested in applying as a Tree Ref, message me (nightblitz42) here on Smogon, or on Discord. General qualifications I am looking for are: recent reffings done with minimal mistakes, and proficiency with the Damage Formula.
- Players may ref a maximum of two (2) simultaneous Tree challenges.
- Refs must take challenges starting from the top of the queue, and are not allowed to "skip over" earlier challenges (excluding their own).
- Players who are challenging Battle Tree for the first time take priority over repeat challengers.
The ref is never obligated to interact with content that makes them feel uncomfortable. If such a case occurs, either work out the issue with the challenger, or privately message the Tree Head (nightblitz42) to have the issue resolved on a case-by-case basis.
Challenge Preparation:
After you have a agreed to ref a challenge, secretly take these preparatory steps:
- Randomly select four (4) unique Pokemon from the posts below, belonging to the challenge's Tier. (for example, if the challenger is challenging Tier 2, select four unique Pokemon from the Tier 2 Ref Mons list.) Note the order that you rolled them in.
- Randomly select two (2) unique Pokemon from the posts below, one Tier above the Tier being challenged. (if the challenger is challenging Tier 2, select from the Tier 3 Ref Mons list. If the challenger is challenging Tier 3, select from Tier 3 Bosses.) They will be used for the final battle.
- Randomly select three (3) Roleplay Events from the Battle Tree RP Tables using the following method (the events must be used in the order you rolled them):
- Roll a d3.
- If you rolled a 1: Randomly select a unique Special Event corresponding to the Scenario being challenged.
- If you rolled a 2 or 3: Randomly select a unique Generic Event that shares at least one Keyword with the Scenario being challenged.
Finally, give yourself one (1) Mulligan Token. At any time before or during the challenge, you may (secretly) spend the Mulligan Token to perform any one (1) of the following actions:
- Swap the order of the Roleplay Events you rolled, however you like.
- Replace one Generic Event you rolled with the next unique Generic Event on the RP Table that shares a Keyword with the Scenario (if you reach the end of the table, return to the top).
- Randomly select a unique Generic Event that shares at least one Keyword with the Scenario, append it to your list of Roleplay Events as a fourth Event, then discard one Roleplay Event of your choice (leaving you with three).
Challenge Structure:
After you have taken all the preparatory steps, the challenge proceeds as follows:
- RP Segment 1 (using Roleplay Event 1)
- Battle 1 (using mons 1 and 2)
- RP Segment 2 (using Roleplay Event 2)
- Battle 2 (using mons 3 and 4)
- RP Segment 3 (using Roleplay Event 3)
- Battle 3 (using mons 5 and 6)
- The challenger challenges the High-Rise Metropolis Scenario at Tier 3.
- You post in the Signup Thread that you will ref the challenge.
- One by one, you randomly select four (4) different Pokemon from the Tier 3 Ref Mons list. In this case, your rolls, in order, are:
- Eelektross
- Gigalith
- Metagross
- Wishiwashi
- Next, you randomly select two (2) different Pokemon from the Tier 3 Boss Mons list. In this case, your rolls are:
- Mega Beedrill
- Zekrom
- For RP Segments, you roll three (3) d3 in sequence. Your rolls are 1/3, then 2/3, then 3/3.
- Since your first roll was a 1, you will randomly select a Special Event from the High-Rise Metropolis Scenario. In this case, you roll Special Event 2/5.
- Since your next two rolls are 2 and 3, the next two events will be random Generic Events that share at least 1 Keyword with the High-Rise Metropolis Scenario. It takes a couple tries, but eventually you roll appropriate Events: Guarded for the second Event, and Snatched for the third.
- Based on these preparations, the Tree Challenge is going to have the following flow:
- RP Segment 1 (Special Event 2/5)
- Battle 1 (vs. Eelektross and Gigalith)
- RP Segment 2 (Guarded)
- Battle 2 (Metagross and Wishiwashi)
- RP Segment 3 (Snatched)
- Battle 3 (Beedrill and Zekrom)
- Finally, you have your Mulligan Token available, should you decide you need it.
Roleplay Segment Expectations:
The Scenario and the pre-challenge preparations you have made will provide simple “blueprints” for most of the basic story elements. The referee’s job is to add details to these blueprints with the goal of establishing narrative cohesion. Within the Roleplay Segments, the ref has the freedom to add details to the story however they please (adding new characters, locations, events, worldbuilding, etc). However, they must always abide by the following narrative rules (in addition to standard rules of decency):
- The challenger’s team is comprised of:
- The Trainer, which represents the player themselves.
- The Trainer’s two Pokemon.
- The ref cannot add, remove, or modify information related to the identity or history of the challenger’s team.
- The challenger’s Pokemon cannot abandon their Trainer, and vice versa.
- Pokemon can talk.
- The challenger’s team may move to new locations within the Scenario’s setting, but cannot completely leave the Scenario’s setting.
- People and Pokemon can survive in any environment (underwater, outer space, alternate dimensions) without safety equipment, unless a Roleplay Event specifically makes the environment an obstacle. This is because of magic, don’t ask questions.
- Characters are allowed to suffer minor injuries (cuts, scratches, bruises), and may face the threat of injury or death, but characters must NEVER actually be seriously injured, die, or be killed under any circumstance.
- At the end of the challenge, the challenger’s team always finishes safely and in one piece.
Each Roleplay Event describes to the ref, in very general terms, an obstacle that the challenger must overcome (for example, “The challenger’s team must cross a large chasm”). Sometimes the Roleplay Event also specifies a specific goal that must be achieved. At the start of each Roleplay Segment, the ref writes up a narrative (at least 1 paragraph), adding details to the blueprint in order to fit the story and setting.
The challenger must respond with a Solution. The challenger's Solution is their plan for overcoming the obstacle. In order to be valid, the challenger's Solution must make use of their Pokemon according to the following guidelines:
- The Pokemon, not the Trainer, must be the main contributors to the Solution.
- One or both of the challenger’s Pokemon must "participate"in the Solution. Pokemon "participate" in a solution by using one or more of the following things to help solve the problem:
- A move it knows.
- Its Ability.
- Its Held Item.
- Its Pokedex entry (from any of the official Pokemon games).
- Its biology (from Bulbapedia).
- Its Attitude. (Contributions made this way must be within human capabilities.)
- Its Background. (Contributions made this way must be within human capabilities.)
- At least one Pokemon must participate by using something that it has not used in a previous Roleplay Segment.
- The solution must have a >0% chance of success.
- During Roleplay Segments, Metronome is banned.
- If the challenger's Solution meets all of the above criteria, the solution must be accepted. The ref writes up another narrative (at least 1 paragraph) describing the result of the challenger’s proposed solution. As always, the ref has free reign to add details as they please, but with the following added restriction: Every valid Solution must succeed.
- If the ref believes that the challenger's Solution has a 0% chance of success due to information that is already available to the challenger, then the ref initiates a Repeat Round. The ref narrates the solution in action, points out a fatal flaw with the solution, then gives the challenger a chance to either make adjustments to their solution or devise an entirely new solution from scratch. Essentially, this causes the Roleplay Segment to begin anew.
- A ref must ask me (nightblitz42) for permission before initiating a third Repeat Round within the same Roleplay Segment.
- If the challenger does not provide a Solution, or if the challenger's Solution is invalid and does not qualify for a Repeat Round, then the challenger fails the Roleplay Segment. The ref writes up a narrative (minimum 1 paragraph) explaining that the challenger overcomes the obstacle through brute force and sheer luck.
- In cases such as these, the ref is encouraged to describe a negative non-gameplay consequence for the challenger, such as becoming covered in filth, having their goal nearly compromised, or being irritatingly inconvenienced.
- Don’t feel forced to incorporate every ref mon into the narrative. Ignoring one Pokemon per team is perfectly fine -- it’s much easier to orchestrate an encounter with one Pokemon than it is for two Pokemon.
- Try to add details that foreshadow one of the Pokemon from Battle 3. This will make your narrative look structured and well-planned (even if it isn’t!)
- Trainer Battles are always appropriate, no matter the circumstance. Your ultimate get-out-of-jail-free card is to narrate the challenger’s solution, then immediately introduce an NPC Trainer who wants to battle. At the end of the battle, the NPC Trainer can give the challenger some “very helpful directions” that lead them straight to the next Roleplay Event.
- If you’ve reached the Battle 3 Roleplay Segment and you still don’t know how to bring the story to a head: simply introduce a bad guy from an evil Pokemon Organization, explain that they are doing something related to an ambiguous evil plan, then make them fight the challenger. At the end of the battle, the baddie can either: get apprehended by the player; or get a call from evil HQ, say that there’s been a change of plans, and run away while still being smug and enigmatic. Because this is just a more specific instance of the Random NPC Trainer strategy, it is applicable in any situation and scenario.
- If the challenger loses a battle at an awkward time, and you don’t know how to end the story: just make the challenger black out and wake up again somewhere safe with their teammates.
- Don't be afraid to ask the challenger for ideas, especially when it comes to themes or motivations.
- For each battle the ref finishes, the ref earns 4 RC, 2 TC, and 3 JC (to be claimed cumulatively at the end of the challenge).
- For each Roleplay Segment the ref finishes, the ref earns 1 JC.
- If a ref is DQ'd, they are paid 3 JC for each battle they reffed start to finish, and 1 JC for each Roleplay Segment they reffed start to finish. They are not paid for battles they partially reffed, and they are not awarded any TC or RC.
Last edited: