Art by Albatross!
Hosted by Gekokeso, Murphy Lawden and Horii.
Petmods Premier League V Admin Decisions and Announcements
The following thread will document both all the resources available to start playing in the PMPL, as well as announcements regarding administrative decisions and changes to the tiers in the tournament. This includes mid-tournament nerfs and bans, as well as emergency bug fixes.
PMPL V will consist of the following teams:
- Workers Union of Gourgsokyo: anaconja and Beaf Cultist
- Dave's Daschbuns: Monai and Lostmemories
- Gladiator Gallades: Zpice and JeoZ
- Fast & Furret: Cao Jie and RL
- Torchics RD: desi and Ngolatria
- Gigaton Spammers: Fragments and Spammernoob
Manager Self-Buys:
Not Selected Yet
The tiers this year are:
- Iron Fist
- [Gen 6] Megas Revisited
- Fusion Evolution Gen 9
- Paleomons Gen 9
- Teramax
- Glacemons
- Blank Canvas Meta C
- Random Tandem (Bo3)
Next section will cover the general list of rules that should be set in place in case that there are any errors.
Systems put in place in case of failure
Teambuilder legality
In every PL we have had issues with some moves, abilities or Pokémon being allowed when they shouldn’t have been and has led to some controversy. For this reason, moving forward we will standardize the procedure of what happens in each of these cases.First and foremost, we shall implement the following:
- The banlist submitted for each tier is final. If it appears on the banlist, you don’t use it. If a pokémon is found to be banned on the builder, but does not appear on the banlist, let tour hosts know as soon as possible to ensure either its added to the list or unbanned.
- Should a pokémon be unbanned midweek in the above case, this decision will be broadcasted publicly so that every player is notified in time. Same if a banlist is updated.
- Should a player appear to use a banned element that clearly appears in the banlist of said tier, their match will be considered null and win will be granted to their opponent. Should said element not been explicitly banned on the banlist it will be considered legal and the match will stand.
- Should an element be judged to have been incorrectly mislabeled or functioning differently as it appears on a spreadsheet, you must notify any person responsible for the sheet or tour hosts to indicate the mistake prior to your match to fix it as soon as possible or notify all teams about it. Knowing about a bug or miscoded mechanic yet not reporting it on time could result in a match being redone. If a bug hasn't been fixed in time but all teams have been notified about it, it will be considered allowed until the fix goes through.
Midweek Tier Changes
This has been a constant in every PL, and the method employed during the first section of this post should at least help with it in some way. Still, it's likely one or two metas have stuff that slips through the cracks, so to prepare for that, I have designated a schedule of some sort.Every tier will be entitled to making changes to their metas only three times per the duration of the solomods premier league. The changes can be done at any point during the tournament, but once you change it one week you must wait another week before being able to push for a change in the meta. This is a change that should allow for metas to get rid of anything that ends up being too much while also preventing multiple changes from taking place in a short time.
Crashes / DH connectivity issues
This is unfortunately the one we have the least control of. It is every tier leader’s responsibility to make sure every meta is working as intended, and it will be their responsibility to test every custom element in their metas to prevent crashes. Still, there’s the chance a crash occurs in a battle or the server undergoes troubles that prevent players from logging in. For that the following options shall be provided:- Extension: Extensions to the battle can be provided for teams to make new teams or to play in case one can’t make it due to connectivity issues (note, provide as much evidence of this as possible to prove its due to connectivity)
- Recreation: If a battle has started but the server restarts a recreation of the battle can be attempted, as long as every team provides their teams and a host is around to prove that no foul play is going on.
- Rematch: Both teams load completely different teams. This does put pressure on players to have multiple teams at hand so it's definitely a more unpopular option, so just take this option if you feel comfortable having a backup in case of an emergency.
Last edited:









