Ok, sorry. I had some irl problems going on that I was really frustrated with because I can't find the answers to, and so I wasn't really the most logical with my posts, sorry for making you list out all of those mons.

Let's get back to the actual argument, if you will allow us to. In this post, I will attempt to address all of the main arguments for keeping Mega Sableye in OU. If I missed any points or if I did not provide enough support please notify me and I will fix it. I would hope that you all keep in mind that reqs are more difficult to get than ever, unlike the other suspects that we have previously had, so your vote counts so much more this time. Because of this, I suggest that you all approach this suspect with an open mind, and think thoroughly to gain a deeper understanding of what the right decision to make is. If you have thought through all possibilities and viewpoints, then I will understand whatever decision you choose to make.

It is also important to keep in mind that this suspect test is unlike a majority of suspect tests that usually take place, so I would recommend not trying to relate this suspect to any previous ones when making your decision. The main reason behind this is that this suspect has taken place because both Mega Sableye and Gothitelle are found to be uncompetitive, not because the OU Council thought that it was necessarily "broken", or at least not what we usually think of as broken. Most people associate being "broken" with being strong, powerful, impossible to counter, has many potential sets, overcentralizing, etc. Think of other mons that the OU Council has suspected, like Greninja, Landorus-Incarnate, Aegislash, and Mega Mawile; for these reasons, it does not bode well to attempt to associate Mega Sableye with the word "broken". Instead, I advise you to see how Mega Sableye fits into the category of being uncompetitive. Uncompetitive mons take away from skillful aspects of the games such as, switching (Gothitelle), attacking (evasion moves and Swagger), teambuilding (Baton Pass), and with the advant of Mega Sableye, hazards. I believe that switching, attacking, teambuilding, and hazards are all components that are skill-based, and that is what I will be basing my argument on. If you don't believe this things involve skill, I will not attempt to persuade you otherwise. In this post I propose to you that you think about how Mega Sableye may be uncompetitive in the aspects of teambuilding, switching, and hazards. If you are convinced in at least one of these points, I urge you to vote ban on Mega Sableye because these previous uncompetitive mons and ideas have been banned for being uncompetitive in only one category.

Now some of you may argue that hazards do not involve skill because they do not need to be on the field in order to win every game, even if they certainly play a large role in the outcome of the game if played correctly. While this may have some truth to it, I believe that the real reason that preventing hazards is uncompetitive comes from the fact that it does not reward players for making good plays, and forcing Mega Sableye stall to switch in and out. Merely forcing Mega Sableye to switch around is not going to be damaging it enough for a player to win. If the Mega Sableye stall is built decently, then it stands to reason that the teambuilder will have counterplay to all of the big threats in OU that they could account for, which usually means the team will be able to deal with all but the most dedicated of stallbreakers, which is a very limited group of mons. Well yes, you could make the argument that teams can run these mons, more often than not it really limits the teambuilding options available to the teambuilder. Mega Sableye dictates teambuilding because of this. Again, this all stems from the fact that Mega Sableye is able to prevent hazards from a large majority of mons with its ability, which is made effective by its stats and typing.

Another argument that I have seen some people use as their reasoning for not banning Mega Sableye is that they did not have any troubles when playing against it. This is a bit complicated, so I will do my best to simplify the reasoning why this support is flawed. For suspects that were based on the mon being "broken" this logic may have applied. However, in this suspect the argument is Mega Sableye being uncompetitive. While you may not have had any problems playing against Baton Pass, swagplay, evasion moves, and Gothitelle due to the teams you use or the playstyles you play, it doesn't change the fact that these mons are still uncompetitive. This applies to Mega Sableye in the same way as these potentially uncompetitive mons that ended up being banned.