Jump to content

Munya

Global Moderator
  • Posts

    13161
  • Joined

  • Last visited

  • Days Won

    22

Everything posted by Munya

  1. None because nobody has definitively asked me to start a vote on it, it was mentioned and i replied to them about the at least one vote currently in limbo waiting for more of the test to happen and they never asked to vote anyway.
  2. 3-1 is not how many tc members we have
  3. It has been 4 votes for a long time now. "A vote requires a 2/3 majority by the tier council to pass"
  4. its not, it requires 4 in favor to ban something. We have 5 members, soon to be 6 again.
  5. Then that section of the policy needs to be re-written, its likely an oversight that it wasn't trying to condense multiple sections into one. Nobody is doing anything to try and "bypass" anything, a quick ban is the last resort option, people wanted to test it as there was doubt, hence the no quick ban, and some still want to take it to the end of the month before making the decision on to ban it or not. We can initiate a vote now but you are likely not going to get the result you want doing it before people are decided on the issue. Its not like I didn't ask for community input in the definitions thread either, that post is still very much there.
  6. Whenever we were re-writing the definitions I asked about suspect tests and from what we came up with this falls into suspect category via definitions. According to it it doesn't need to have been banned first, it just needs to be identified as a potential problem. What is a suspect test? A suspect test is when a pokemon is identified to potentially be a problem, but without practical evidence there is reasonable doubt. So a test period can be initiated to try the pokemon in a tier to find out.
  7. Maybe its obvious to everyone but I feel like at the very least this part of caoix's post is valid enough to be answered even if its a short answer. "What is the issue with Vaporeon?"
  8. Last month of the season, 4.36% was the cutoff at the time usage was taken. Next month we will resume normal cycles. To OU from UU: Toxicroak - 6.01% usage in OU Seismitoad - 5.76% usage in OU Back to BL: Porygon2 - Voted on an re-banned, more info here. To UU from OU: Ditto - 4.23% usage in OU Jolteon - 3.69% Usage in OU Milotic - 3.75% Usage in OU Salamence - 4.08% Usage in OU To NU from UU: Cloyster - 3.58% Usage in UU Gastrodon - 3.90% Usage in UU Nidoqueen - 3.70% Usage in UU Tentacruel - 3.63% Usage in UU Vaporeon - 2.89% Usage in UU Zoroark - 4.02% Usage in UU Discussion thread:
  9. Nah this is specifically for ban reversal/starting suspect tests. Wouldn't change anything for the banning process.
  10. How would people feel about amending this section to allow skipping the 1 week discussion and going straight into suspect testing/thread assuming discussion has happened on a topic within one of the 4 open discussion threads and or the monthly discussion thread. Mainly the bolded part.
  11. If kingdra should be there then its likely a mistake that its not - user error, this is why I prefer to not manually keep track of things and why some things are not going to happen unless it gets automated. pretty sure there is policy for unbanning anything in the policy thread.
  12. You are correct about machamp from the looks of it will have to dig more to find out but gatr was actually quickbanned. Was prior to us having a log channel for votes so finding that info sucks.
  13. BL1 Darmanitan Dugtrio Haxorus Lucario Porygon-Z Staraptor BL2 Durant Feraligatr Machamp Rhyperior Roserade Venomoth
  14. We are aware of the potential salamence issue yes and it has been mentioned in the tier council discord, most people are asleep right now I would assume though.
  15. Its because we haven't been on a stable seasonal schedule in some time, every time we try and get back on one something new is added to the game to disrupt it.
  16. Last month in the season and hopefully we can finally get back on a seasonal schedule after this with normal movements. 4.36% to go either way. For this month things above / below cutoffs are: To OU from UU: Toxicroak - 6.01% usage in OU Seismitoad - 5.76% usage in OU To UU from OU: Ditto - 4.23% usage in OU Jolteon - 3.69% Usage in OU Milotic - 3.75% Usage in OU Salamence - 4.08% Usage in OU Additionally a vote has been requested for the Porygon2 test so we should see a conclusion that that this month whichever way the vote ends up. To NU from UU: Cloyster - 3.58% Usage in UU Gastrodon - 3.90% Usage in UU Nidoqueen - 3.70% Usage in UU Tentacruel - 3.63% Usage in UU Vaporeon - 2.89% Usage in UU Zoroark - 4.02% Usage in UU
  17. We are currently looking for a new member for TC, if anyone is interested please send a DM to me here on forums, thank you. EDIT: Filled. Feel free to still apply and we will keep you in mind for the future.
  18. You haven't found the part of the event that is still going on yet?
  19. Toxic boost isn't stated when its activated, thats normal. It doesn't have full attack evs, nor does it have a max IV in attack.
  20. Without knowing what level, nature, HP% your lapras was at before being hit, etc. We can't really tell anything from this screenshot. Even in the absolute worst case scenario where the lapras was built to die from 1 hit to a zangoose in this situation, there would be the slight possibility it would survive from full HP. Assuming the lapras is level 100.
  21. Its intentional that it deducts PP from both pokemon. This also isn't the place to make bug reports, you should be doing that here: https://support.pokemmo.com/ login using your game account.
  22. To OU: Nothing To UU from BL1: Porygon2 - Given all of the recent changes and additions to the game TC has deemed it appropriate to once again test the waters with P2, a more detailed explanation for this can be found in the thread dedicated to it soon to be posted. To UU from OU: Venusaur Empoleon Shaymin To UU from NU: Magneton Druddigon To NU from UU: Scrafty Golbat Sharpedo Slowbro Discussion thread:
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use and Privacy Policy.