🗂️ Organize and update project files, documentation, and plugin configurations for the Pokémon Professor project
This commit is contained in:
@@ -0,0 +1,62 @@
|
||||
**BRACKET/CHALLONGE**
|
||||
|
||||
* Double Elimination (until you have lost 2 matches, you are still in the tournament)
|
||||
* Best of 3 (first to two wins, no need to play additional games if it’s 2-0)
|
||||
* Ties (to be replayed as if no game happened)
|
||||
* Saturday, we are playing up until (insert \# here)
|
||||
* QR CODE (links to challonge bracket)
|
||||
* FIND YOUR MATCH
|
||||
* Find your name on challonge
|
||||
* Pairings are assigned a table number
|
||||
* ABOVE written as “Table \#” or “Stream \#”, number on the left side is irrelevant
|
||||
* number on the left side is irrelevant
|
||||
* BRACKET MONITOR
|
||||
* Estimated round time starts
|
||||
* still your responsibility to be on time start time will never be earlier than the time on the monitor, but could move later
|
||||
|
||||
**PHONE AND TABLE ETIQUETTE**
|
||||
|
||||
* Only WIRED headphones are allowed
|
||||
* RESPONSIBILITY to remove your account after playing, don’t remove staff test account
|
||||
* ONLY use phones for gameplay, nothing else
|
||||
* Note that reviewing your own match recording or trying to resolve disputes amongst players are both grounds for a penalty
|
||||
* SETTINGS PROBLEM request a judge to assist you by raising your hand (don’t download assets or other, those should be all done already)
|
||||
* NO PERSONAL PHONES (unless for two-factor identification for login) make sure to remove from table before gameplay
|
||||
* Outside resources are not allowed on personal or provided tournament phones
|
||||
* This includes battle simulators such as pvpoke
|
||||
* NO PERSONAL ITEMS OR LIQUIDS on tables
|
||||
* exception: plushies and a BLANK notebook
|
||||
|
||||
**TOURNAMENT ETIQUETTE**
|
||||
|
||||
* TIME \= You have 5 minutes to show up once your round/match is called
|
||||
* (late 5 minutes \= 1 game loss / late 10 minutes \= 1 match loss)
|
||||
* TEAM SHEETS \= Exchange with opponent at the start of your match and you are responsible for retrieving it after the match
|
||||
* (needing a replacement team sheet will incur a warning on 1st offense and a penalty on 2nd offense and more)
|
||||
|
||||
**Team Sheets**
|
||||
|
||||
* HANDED OUT at the start of each round by the floor judges
|
||||
|
||||
**Other Stuff**
|
||||
|
||||
* NO NOTES prior to sitting down for your match
|
||||
* NO SPECTATING in the tournament area
|
||||
* TEAM CHECKS \= if a judge asks to do a team check, you have to comply or you could be assigned a penalty
|
||||
* COMMUNICATE with judges if you need to leave the play area (bathroom break, etc.) or drop out of the tournament
|
||||
Do not leave the station until the score has been recorded, wait until judging staff completes team checks (even if your opponent is being team checked instead of you)
|
||||
|
||||
**GAME REVIEW**
|
||||
|
||||
* RAISE YOUR HAND if you think a rematch might be required, a nearby judge will assist you
|
||||
* RECORD YOUR MATCHES (your responsibility \- you void your right to dispute if you don’t record), warning will be issues after first offense, additional offenses may incur penalties
|
||||
* PLAY OUT every match (if you forfeit, no rematch can be given)
|
||||
* GAME REPLAY \= No restrictions, doesn’t have to be same teams
|
||||
* RIGHT TO APPEAL \= you can appeal any judge's decision. Head or Assistant Head judge will be called over and has final say on the matter.
|
||||
|
||||
**FINAL THOUGHTS**
|
||||
|
||||
* Have fun
|
||||
* Be respectful
|
||||
* Enjoy the tournament\!
|
||||
|
||||
@@ -0,0 +1,59 @@
|
||||
Information Gathering:
|
||||
|
||||
1. Request the players to describe **ISSUE(S)** to you. This is the most crucial part because the entire review hinges on the judge being able to confirm the issue happened. Without knowing what/when the issue was, the review may take a very long time and/or you may miss some critical issue that occurred.
|
||||
2. If multiple issues occurred, ask them to provide you with all instances
|
||||
3. If they say entire game was laggy, ask these followup questions:
|
||||
1. Do you think you were losing turns?
|
||||
2. Do you think your opponent got extra moves?
|
||||
3. Did the general lag impact you making any plays i.e. throwing charged moves, switching, catching, etc?
|
||||
4. Attempt to define players’ **INTENT** should the game have worked correctly. Intent is extremely important during your final decision making process because this will drive whether or not the player would have had additional win condition(s) without the game issues.
|
||||
5. Ask player what they were trying to do in the matchup before/when the lag happened, examples:
|
||||
1. Were they trying to farm up energy then switch/catch?
|
||||
2. Were they trying to force a Charged Attack Priority (CAP)?
|
||||
3. Were they trying to get to the move and throw as fast as possible?
|
||||
4. Were they trying to farm a Pokemon down completely?
|
||||
5. Were they just going to play out the matchup in a normal manner?
|
||||
|
||||
Review Process:
|
||||
|
||||
1. First confirm the **ISSUE(S)** actually occurred. Scrub through the footage yourself or have the competitor direct you through the instances of the game issues. Be sure to confirm the issues on both devices.
|
||||
2. Confirm the **INTENT** described by the player. Examples:
|
||||
3. If possible, validate they were clicking the switch button if they intended to catch or bank energy and swap out
|
||||
4. If possible, validate they were tapping the correct charged move button if they intended to force CAP or KO opposing pokemon ASAP
|
||||
5. Determine if the intended play was a realistic option for them.
|
||||
6. Realistic:
|
||||
1. Had lag not occurred, player could have farmed down opponent’s pokemon prior to them reaching a move
|
||||
2. Had lag not occurred, Player could have reached charged move at the same time as Opponent and would have won CAP.
|
||||
3. Had lag not occurred, player could have swapped out to save energy/health for a different matchup
|
||||
7. Unrealistic:
|
||||
1. Player claimed lag prevented them from getting to a move, however they would have reached move the same time as opponent and would have lost CAP
|
||||
2. Player claims lag prevented a farm down, but opponents Pokemon would have reached a move regardless of lag
|
||||
3. Player claimed lag prevented a catch, however opponent throw the charged move at a time where player’s pokemon would have been mid-fast move
|
||||
|
||||
Determine **Impact**:
|
||||
|
||||
1. Determine if the intended plays were impactful and would have allowed for a different game outcome. When determining impact, try to consider all aspects of the game the lag may have impacted: energy, damage, alignment, shields, etc. Impact is the driving force for the final decision in reviews. In order to deliver a fair decision, we need to establish whether the issue significantly changes the game in question. Some examples of impactful v not:
|
||||
2. Possible Impactful Scenarios
|
||||
1. Player could have reached a final CM to KO Opponent’s final pokemon had lag not occurred
|
||||
2. Player could have flipped a matchup and thus won alignment had lag not occurred
|
||||
3. Player could have obtained a crucial shield advantage had lag not occurred
|
||||
3. Possible Unimpactful Scenarios
|
||||
1. Player did not have enough health to reach a final move
|
||||
2. Player could have reached a move, but it would not have been enough to KO final pokemon
|
||||
3. Player could have caught the move but it would have resulted in an impossible to win alignment
|
||||
4. Player could have reached a charged move to KO a Pokemon, but another Pokemon in the back would have still won the game for the opponent.
|
||||
4. Remember to consider the entire game state when determining impact. Just because an issue affects how 1 matchup between two pokemon is played out, doesn’t mean the other pokemon can’t render the issue unimpactful. As a general rule of thumb, we want to consider all aspects of the game, however we want to avoid extensively theorycrafting every possible game state that could have occurred.
|
||||
5. This may be the most subjective piece of the puzzle and could end in grey areas quite often. In those situations, reach out to other judges for their input as well. You do not need to make all of your decisions alone.
|
||||
|
||||
Making the Ruling:
|
||||
|
||||
1. The rule of thumb when it comes to making a ruling requires answering these questions:
|
||||
2. Did the **Issue** described actually occur? If yes, this may be a potential rematch, so move onto the next question. If not, a rematch should not be granted.
|
||||
3. Was the **Intent** of the player realistic? If yes, this may be a potential rematch, so move onto the next question. If not, a rematch should not be granted.
|
||||
4. Was the issue **Impactful** to the outcome of the game? If yes, this should be ruled as a rematch. If not, a rematch should not be granted.
|
||||
5. Always deliver your ruling in a well structured manner that clearly lays out the Issue, the Intent, the Impact and what your final decision is. A couple examples of how you can deliver the rulings:
|
||||
6. I was able to confirm that Player A’s Azumarill lagged one turn when coming to Mandibuzz.This prevented Azumarill from getting a bubble through on Mandibuzz’s Aerial Ace. Then, once Mandibuzz switched out into Annihilape, Annihilape was able to Rage Fist Azumarill for the KO. If Azumarill had gotten the bubble through, Player A would have been able to reach Ice Beam to KO the Annihilape prior to it reaching a charged move. This impacted the outcome of the game because if Azumarill reaches the ice beam, it can KO the Annihilape and then bubble down the Mandibuzz afterwards. Due to this, a rematch will be played for this game.
|
||||
7. I was able to confirm that the game stuttered for Player A when they attempted to catch the Earthquake from Clodsire onto their low HP Marowak, preventing them from making the catch. Player A was clicking to switch to the Marowak right when Player B was throwing the Earthquake. If the game had not stuttered, Player A would have made the catch, which would have KOed the Marowak. Then they could have come back in with Feraligatr and gotten to a Hydro Cannon to KO the Clodsire before the Clodsire would reach another move. Therefore, this will result in a rematch being played.
|
||||
8. Once you are done delivering the ruling, **ALWAYS** let the players know that they may appeal your decision to a Head Judge. You can always end your rulings with sometime along the lines of: “If you disagree with my decision, or would like to have it looked at further, you may appeal to a Head Judge. Please let me know if you would like to appeal and I will bring them over.”
|
||||
|
||||
Not all reviews are very straightforward. In some, the issues may be scattered around or very early in the game. This may make defining Intent and Impact very difficult. In others, a player may have difficulty communicating the issue to you due to issue complexity, nerves or whatever other reason. This is meant to help you follow a structured process when doing a review. You are still trusted by your team and leadership to use your own discretion in situations where you may not be able to strictly follow these best practices. That is okay and encouraged. The idea of this is just to help, at the minimum, ask the right questions so that you are making the most well informed decision you can make.
|
||||
@@ -0,0 +1,7 @@
|
||||
**Duties and Responsibilities:**
|
||||
|
||||
- **Support to Head Judge:** Work closely with the Head Judge to help manage the event, including providing support for decision-making and overall event management.
|
||||
- **Rule Interpretation:** Assist in interpreting and applying rules during the event, particularly in more complex situations or when disputes arise.
|
||||
- **Dispute Resolution:** Handle disputes or rule violations that are escalated from Floor Judges. Provide fair and consistent resolutions based on the event rules and guidelines.
|
||||
- **Judge Coordination:** Help coordinate and manage the Floor Judges, ensuring they are performing their duties correctly and effectively.
|
||||
- **Logistical Support:** Assist with the logistical aspects of the event, including scheduling, match management, and ensuring the event progresses smoothly.
|
||||
@@ -0,0 +1,7 @@
|
||||
**Duties and Responsibilities:**
|
||||
|
||||
- **Support to Head Judge:** Work closely with the Head Judge to help manage the event, including providing support for decision-making and overall event management.
|
||||
- **Rule Interpretation:** Assist in interpreting and applying rules during the event, particularly in more complex situations or when disputes arise.
|
||||
- **Dispute Resolution:** Handle disputes or rule violations that are escalated from Floor Judges. Provide fair and consistent resolutions based on the event rules and guidelines.
|
||||
- **Judge Coordination:** Help coordinate and manage the Floor Judges, ensuring they are performing their duties correctly and effectively.
|
||||
- **Logistical Support:** Assist with the logistical aspects of the event, including scheduling, match management, and ensuring the event progresses smoothly.
|
||||
@@ -0,0 +1,15 @@
|
||||
**Duties and Responsibilities:**
|
||||
|
||||
- **On-the-Ground Support:** Floor Judges are responsible for handling issues and inquiries from participants during the event. They’re the first point of contact for players who need assistance or have questions.
|
||||
- **Rule Enforcement:** They ensure that the rules of the tournament or event are being followed. This includes monitoring gameplay, addressing rule violations, and making sure that matches are conducted fairly.
|
||||
- **Match Oversight:** Floor Judges may be assigned to oversee specific matches, ensuring that they are played according to the established rules and resolving any disputes that arise.
|
||||
- **Player Assistance:** They provide guidance and support to players, including helping them with registration issues, understanding event procedures, and addressing any concerns they might have.
|
||||
- **Reporting Issues:** They report any significant issues or disputes to the higher-ranking judges (Assistant Head Judge or Head Judge) for resolution.
|
||||
- **Technical Issues:** Help the players with logging in and more importantly when logging out how to remove personal information from the phones.
|
||||
- **Team Checks:** On an as needed bases, check the players team posted on RK9 and compare it to the team shown on the phone they are using. In addition, using gameplay footage to verify is always good to do if you have time.
|
||||
- **Match Reporting:** Using Challonge to update what tables are playing currently as well as the final scores when a player raises their hands.
|
||||
- **Crowd Control:** Making sure other players are giving an appropriate distance from the table to give the active players comfortable and focused on the games at hand. Also assists with deterring cheating.
|
||||
- **Housekeeping:** Making sure the stations where players will be playing is clean, free from debris or clutter. In addition, phones are connected to the chargers and back on the stands. Chairs should be pushed in and ready for the next player.
|
||||
- **Phone Testing:** Logging in to the phones with the organizers' Google login to make sure that assets are downloaded, game functions properly, and battles do not seem to have any issues.
|
||||
- **Game Disputes:** Handle any game disputes the players might have. You are the first line of defense in terms of being able to solve their problem and make a ruling. After making a ruling always explain to them if they would like to appeal to a head judge they may ask for that.
|
||||
- **Penalties:** Handle explaining any penalties the player might incur from being late, not submitting a team, not having the same Pokémon registered in RK9 vs what they are playing with in a manner they can understand and can comply with.
|
||||
@@ -0,0 +1,7 @@
|
||||
**Duties and Responsibilities:**
|
||||
|
||||
- **Event Management:** Oversee the entire event, ensuring that it is conducted according to the established rules and regulations.
|
||||
- **Final Decision-Making:** Make final decisions on disputes and rule violations that have been escalated from the Assistant Head Judge. Their decisions are authoritative and final.
|
||||
- **Rule Consistency:** Ensure that the rules are applied consistently across all matches and that all participants are treated fairly.
|
||||
- **Team Oversight:** Manage and oversee the judging team, including Floor Judges and Assistant Head Judge. Provide guidance, support, and address any issues within the judging team.
|
||||
- **Communication:** Act as the primary liaison between the event organizers and the judging team, ensuring that any major issues or changes are communicated effectively.
|
||||
@@ -0,0 +1,7 @@
|
||||
**Duties and Responsibilities:**
|
||||
|
||||
- **Event Planning:** Involved in the planning and preparation stages of the event, working with organizers to ensure all aspects of the event are properly coordinated.
|
||||
- **Judge Training:** Responsible for the training and preparation of the judging team, including Floor Judges and Assistant Head Judges, to ensure they are well-versed in the rules and their roles.
|
||||
- **Strategic Oversight:** Provide strategic oversight for the event, making high-level decisions to ensure the event runs smoothly and addressing any significant issues that arise.
|
||||
- **Complex Issue Resolution:** Handle complex or high-profile disputes and problems that may arise during the event, ensuring fair and balanced resolutions.
|
||||
- **Reporting and Evaluation:** Provide post-event reports and evaluations to organizers and stakeholders, summarizing the event's success, challenges, and areas for improvement.
|
||||
@@ -0,0 +1,34 @@
|
||||
**You’ve been selected as a GO Head Judge or Assistant Head Judge?**
|
||||
**Created By Pete Lachaine**
|
||||
|
||||
**First of all congratulations, this is a great achievement and also a fantastic opportunity to keep growing as a professor. Here are some of my thoughts of what you should do, things to keep in mind and general tips that I'm happy to offer you. *(Please remember your specific lead may have event specific tasks for you as well, never assume these will be all of them and you should talk with your lead before the event begins)***
|
||||
|
||||
- Remember that now especially, you are looked to as a leader. This means your actions, words, & general demeanor are very important. People will follow what you do so “lead by example. You are the face of the GO tournament now
|
||||
|
||||
- Get comfortable with delegating tasks to your floor staff. But in a way where staff feel valued and appreciated. Your tone is important here so staff don't feel like these tasks are punishment or performance related
|
||||
|
||||
- You shouldn't get involved in Floor Judge tasks, especially Game reviews unless its an appeal of course. If you see lots of players hands up, look around quickly, if you see every floor judge is busy, then step in and help with entering match results ect. Otherwise you should always delegate the task to any free floor judge.
|
||||
|
||||
- Plan staggered lunch and dinner breaks for the floor judges. This needs to be done in such a way to not affect tournament flow on the floor or on stream
|
||||
|
||||
- Watch your floor staff and give extra breaks when you notice they could use one. Ex. after a complicated ruling or once the floor slows down after being at max capacity for a while.
|
||||
|
||||
- Plan a stream judge rotation schedule. Judges switches should line up with castor switches for simplicity. This also involves a quick discussion with the stream liaisons to coordinate
|
||||
|
||||
- Listen to player appeals and make a final ruling. When first arriving at the table, let the floor judge explain their ruling to you while showing you the video footage. This should be done away from the players. Listen to the floor judge carefully and see if you agree with their decision. If you don't agree, grant a rematch. But remember you will need to explain your decision to the floor judge after. This is so the judge can apply the lesson learned here immediately. Remember you need to overwhelmingly disagree with the judges initial decision here.
|
||||
|
||||
- You will need to apply to any penalties that involve more than a warning. This includes Game Loss, Match Loss and DQ scenarios. These issues can be discussed with your Lead, but remember the final decision is yours.
|
||||
|
||||
- Provide active Feedback to your floor staff during the tournament.If you see something that could be done better please tell them. This way they can attempt to improve during the event. It's not fair to just unload all the information to them during PERF’s
|
||||
|
||||
- Prepare to write and then give Post Event Reflection Forms(PERFS)
|
||||
|
||||
- Remember to work together with the AHJ and split some tasks amongst yourselves. You both are a team and you should not be working as individuals
|
||||
|
||||
- Have some sort of document prepared that will explain current game mechanic issues and how everyone is expected to rule on them during the current event
|
||||
|
||||
- Escalate any concerns or issues directly to your lead. Communication and chain of command are very important here
|
||||
|
||||
- Have the player meeting prepared for both Saturday and Sunday. This generally includes information about the format, rules and tournament flow. The HJ team will announce this information to players before the tournament begins
|
||||
|
||||
- Be the stream judge during the loser final, winner final and grand final matches
|
||||
Reference in New Issue
Block a user