Jump to content

gbwead

Members
  • Posts

    6103
  • Joined

  • Last visited

  • Days Won

    63

Everything posted by gbwead

  1. That would be counterproductive and leave the floor dirty.
  2. When you clean your house, you need to start with the ceiling and end with the floor. Busso just means that if the objective is to clean up OU to achieve balance you must start with top priorities like Gallade and then you can look at low priorities like Dugtrio.
  3. Not true, plenty of offense or balance teams can carry several checks to most of the OU threats, this has nothing to do with stall. The main difference is that stall will want hard counters and offense will settle for more shaky checks in exchange for more direct pressure. I said your team should have more than 1 option to stop mons like Volcarona. I did not say your team should have more than 1 option against every single OU mon. Those things are not equivalent at all. Volcarona is more of a threat than a shitty Darmanitan. When teambuilding you should focus more on being able to handle Volcarona than being able to handle Darmanitan. Not all OU mons should be equally respected. Garchomp is significantly more viable than Infernape. Tyranitar is significantly more viable than Gastrodon. When teambuilding, you need to use your ressources wisely. If your only check to Volcarona on your team is a Tyranitar (not even amazing vs Volcarona to begin with), your team will not be super viable. You need to pair Ttar with a Chansey or a Gyarados or w.e in order to have a plan B when something goes wrong (freeze, burn, etc.) when you play.
  4. It's really not that simple. There are very few Dugtrio teams that are actually decent because teambuilding around Dugtrio forces you to compromise in so many ways that leaves you vulnerable. Espeon and Serperior are viable to control hazards, but as walls they are extremely underwhelwing. They are one dimensional most of the time so they are easy to exploit. When you pair Dugtrio with Espeon and Serperior, you only have 3 mons left to build your team and 3 mons left is not enough to build something solid. I listed Espeon and Serperior, but to be fair, most Defogers and Spinners are in the same situation. As for Volcarona, plenty of mons can counter it and do not fear Dugtrio like Chansey, Gyarados, Dnite, AV Mienshao, Chandelure, etc. Dugtrio can trap key mons on your team, but if your team is solid, you should have more than 1 option to stop mons like Volcarona in the first place.
  5. I'm not saying the policy should be split. I am saying #2 and #3 should be swapped. A thread should not be opened if TC already made up their mind. Edit: Also, #2 and #3 are already swapped whenever a new ability or new mechanic is introduced. If Alakazam gains Magic Guard over night, you're not going to ask TC to go through the trouble of writing a thread, approve it and then opening it. They will vote instantly as they should.
  6. Yes. If TC has the power to silence us, they should vote on whether or not we should be silenced before opening the discussion thread. There is no point in keeping up appearances. It takes so much time for a thread to get written, approved and then opened. If TC intends on silencing us, they should not give us the illusion that our input matters. I assume the reason this thread is still opened is because TC doesn't want us silenced which is great, but if TC wanted us silenced, opening a thread for having it closed 2 minutes later is counter productive.
  7. Quick ban in the old policy has nothing to do with what a Quick Ban is today. A Quick Ban in the past was if something new was introduced in a metagame, the TC had the ability to ban it instantly because of the harm it could cause. A Quick Ban now is if TC wants the community to shut up, they can silence them at will. These things are completly different, so it doesn't really matter what the old policy did with Quick Ban because even though the same words are being used we are talking about two different things.
  8. If the quick ban vote is 6-0, what's the point in opening a thread in the first place then. Shouldn't the quick ban vote happen before opening the thread?
  9. Standard Ban: TC votes 5-1, the thread stays open for a full week and players discuss for no reason because the voting already occured. Quick Ban: TC votes 6-0, the thread gets closed instantly and the discussion is over. What's the difference? Players have no say regardless, quick ban or standard ban. This doesn't make sense.
  10. These teams look great to farm noobs on ladder, but I don't think they are very effective in tournaments outside of countering purposes. Some teams will naturally struggle vs Dugtrio and will have no chance of winning, but honestly the same could be said about these Dugtrio teams; they also have 0 chance of winning vs Togekiss, Chandelure and other common OU threats. It's just match up fishing, not very impressive imo. At the first sign of adversity, these teams crumble because they are rigid with no flexibility.
  11. @Ziiiiio What's the Gengar set on the second Dugtrio team? I have never seen that team before.
  12. I hope this is a typo because Dugtrio has been in OU for years. The option to quick ban has been out of the window for a long time. This should obviously fall into standard process, not quick ban.
  13. @Munya Is it possible to have a rough estimate of what TC intends to do with Dugtrio? Will this thread stay open for days, weeks, months or years? Is there an ongoing vote or an upcoming vote? If Dugtrio ends up banworthy, what are devs intending to do in order to remove Dugtrio from Uber? I think many of us fear another Sharpness fiasco and the community input would be valuable imo.
  14. The topic is OU Discussion Dugtrio. Arena Trap should not be affected at all by w.e decision being reached here. Otherwise, the thread would be about Arena Trap in OU and not Dugtrio in OU. There is no reason why Diglett and Trapinch end up nerfed when they accomplish nothing already.
  15. A lot of mons limit teambuilding and favors match up fishing. When it comes to Dugtrio, I agree that a case can be made that Dugtrio does those things to an unacceptable degree. I personally don't think Dugtrio is a problem, but I can see why someone might feel it should be banned and that's fine by me. Like I said, I agree with what you said at first. I don't agree with the later portion of your post where you painted a picture of Dugtrio giving an unfair advantage (implying brokeness) to whoever plays it, because that's not the case imo.
  16. I agree about everything regarding Dugtrio limiting teambuilding and sometimes screwing players over based on match up before duels even begin.However, let's not act like playing Dugtrio puts you automatically at an advantage because that's not true. This statement is not related to Dugtrio. Teambuilding is all about compromise and teambuilding against Dugtrio's team do not make you more vulnerable compared to teambuilding vs any other archetype. You do not need to play obscur unviable mons has counter measures to Dugtrio's teams, plenty of mons can do that on their own or can do that as a pairing with mons they naturally want to play with. Absolutely not. The reward of playing Dugtrio is not much greater than the risk itself. Most teams around Dugtrio have extreme flaws because of Dugtrio. Sometimes Dugtrio has nothing to trap or nothing valuable to trap to justifty its spot on a team. When that happens, Dugtrio becomes a liability and this happens all the time. It's not some rare occurence. Dugtrio brings nothing defensively to teams and relies on Focus Sash, heavy support from its allied mons and/or prediction in order to come on the field. Whatever advantage Dugtrio brings to teams, that advantage comes at a huge teambuilding cost. Sometimes the advantage is worth the cost, sometimes it's not. That's why Dugtrio teams are all about match up fishing. And I agree that can be gross from a competitive stand point, but that doesn't make Dugtrio broken. Unhealthy, that's arguable. AT being uncompetitive to an unaccpetable degree, that's also arguable. But given the current state of OU, Dugtrio is far from broken (UBER). As for SD Excadrill, we surely don't see it often (that doesn't mean it's unplayable) because we have stuff like Chomp, Breloom, Gliscor, etc. everywhere. You can't blame Dugtrio with less than 4% usage as the main reason Excadrill SD is not played more, that's riddiculous.
  17. Espeon and Serperior have been OU for a while. That's nothing new. Togekiss and Volcarona are also well supported by Dugtrio and have lost a lot of viability over the years. We are not in a specific meta where Dugtrio is suddenly more powerful. Dugtrio will always have mons to support and others to trap. The atk buff just increases the quantity of mons that can be supported by Dugtrio and the number of mons Dugtrio can trap. Edit: Also, Espeon and Defog Serperior (not any Serperior) are not as big of threats as Togekiss and Volcarona were in 2019.
  18. Dugtrio's most played items: Can we please not talk about CB Dugtrio? It's not relevant in any way. Also, here is an idea. How about not buffing Dugtrio's attack from 80 to 100? Dugtrio was litteraly NU by usage back when it had a base stat of 80...
  19. Hydreigon could be nerfed in various ways imo: Removing Draco Meteor Removing Nasty Plot Removing Focus Blast Removing Taunt etc. Choosing the right nerf is as important as choosing to nerf in the first place. TC, please think this through.
  20. Team Name: Sic Itur As Astra Team Tag: Sia Registres players: Captain: gbwead
  21. Wobbuffet went from OU to Untiered when it didn't have Tickle. It would not be a big deal imo.
  22. Wobbuffet without tickle would be healthy for our meta. It would also be very annoying for somme regen mons like Amoongus being forced to run Gastro Acid.
  23. Finals Lo (0)vs SIA (0) OU: Dshadd vs Zokuru OU: NewNewDemon vs Azphiel UU: Shamelesss vs gbwead UU: ForFour vs TheDH NU: ChronoRike vs Smadagos NU: TeaDance vs MadaraSixSix Dubs: LoveSiNiLe vs Jgaw Dubs: UTvs Kamimiii UT: MullenYu vs Mkns 3rd Place NORE (0)vs NWO (0) OU: LeJovi vs Goldrayer OU: Flacusaurio vs ArthurLeyinG UU: CarolML vs SecretPlayerZ UU: YaserAL vs jeltyfino NU: Lachidrago vs JulioZm NU: IHasvik vs Olzignie Dubs: YJos vs BadbutG Dubs: Alaniz vs TiburoncinDs LC: Edstorm vs zVelociraptor
  24. Welcome to the Teams Champions League III's Finals thread. Relevant links TCL III General Thread Discord Server TCL III Playoffs Bracket Player Sheets Please refer to the Little Cup Rules for LC. Join the Little Cup Club for further tiering information. Please refer to the In Game Pokedex for OU, UU, NU, UT and Doubles. Please refer to the Rules and Guidelines for Scheduling, Disconnections and Ghosting. Make sure you are aware of the rules for Substitutions and Activity decisions. Finals Lo (2)vs SIA (5) OU: Dshadd vs Zokuru OU: NewNewDemon vs Azphiel UU: Shamelesss vs gbwead UU: ForFour vs TheDH NU: ChronoRike vs Smadagos NU: TeaDance vs MadaraSixSix Dubs: LoveSiNiLe vs Jgaw Dubs: UT vs Kamimiii UT: MullenYu vs Mkns 3rd Place NORE (5)vs NWO (3) OU: LeJovi vs Goldrayer OU: Flacusaurio vs ArthurLeyinG UU: CarolML vs SecretPlayerZ UU: YaserAL vs jeltyfino NU: Lachidrago vs JulioZm NU: IHasvik vs Olzignie Dubs: YJos vs BadbutG Dubs: Alaniz vs TiburoncinDs LC: Edstorm vs zVelociraptor Deadline Sunday 28th @ 11:59 PM UTC
×
×
  • Create New...

Important Information

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