Talk:List of glitches (Generation VII)

Aparentally, they fixed some bugs for Safari Ball, but...

So, I put yesterday the glitch involving the Safari Ball. I've been testing since today morning if this glitch persists and aparentally it only persists for Generation III Pokémon, since my Gen IV Great Marsh Azumarill was not passing throught Battle Spot, but now is. Althought, my Gen III Pokémon still banned and I am seeing a lot of players complaining about the same thing but involving Dream Balls and non-Gen V Introduced Pokémon. I'll update the page putting informations about Dream Ball, but is it correct to put Safari Ball glitch as being fixed? I won't change it for being fixed until get a answer. HilbertCalderon (talk) 18:39, 30 January 2017 (UTC)

Accuracy bug?

I was playing Pokemon Sun, and I had my Vulpix with max affection use Ice Beam against an Absol with no stat changes, and it said that the Wild Absol avoided the hit. Since neither Vulpix or Absol have abilities that lower accuracy, and Ice Beam has 100 percent accuracy, this should not have been possible. Could the affection bonus of avoiding hits be improperly applying to enemy Pokemon? Nairbnroh (talk) 23:41, 14 December 2016 (UTC)

Wild Absol in Tapu Village can use Double Team. It probably did that without you noticing. -- Umbee (talk) 03:50, 18 December 2016 (UTC)

GTS Filter Bug

I found a weird GTS bug that affects Pheromosa and Kartana. If you search for either species without any level filters, you'll only see results for ones at level 60. To see any at higher levels, you need to select a filter for a specific level range. I'm led to believe this is a glitch because if you do a search for "level 61 to 70", you'll get lots of results for people asking for common Pokémon, and I've been able to take my time trading for them. If they were showing up in the unfiltered results as they should be, there's no way I'd be seeing and successfully trading for so many of such offers.

My questions are, what's causing this glitch, and why does it only (to my knowledge) affect those two species in particular? -- Umbee (talk) 03:50, 18 December 2016 (UTC)

This issue is just because both are found in the wild at Level 60, and thus, most players are catching them and then trading them. Does not look like there is any glitch. --Super goku (talk) 04:14, 18 December 2016 (UTC)

I already explained why it's a glitch. You didn't answer anything. -- Umbee (talk) 15:44, 18 December 2016 (UTC)

The answer is that, in my opinion, this is simply not a glitch. Instead, there is a much greater group of Level 60 Pokémon vs Level 61+ Pokémon that is causing this. --Super goku (talk) 08:19, 19 December 2016 (UTC)

People don't put Pokémon on the GTS that fast, nor would an easy trade for a legendary sit for hours at a time (I counted) unless there was something preventing most people from seeing it. I've been observing the GTS listings for these species, with and without the filter, very carefully before concluding that something is amiss. Don't dismiss me just because you think you have an easy answer. -- Umbee (talk) 22:04, 19 December 2016 (UTC)

I've observed similar things in past generations; it was extremely hard to find Pokémon for levels they couldn't be obtained at (Legendaries in particular) when you didn't specify levels, but if you searched for higher levels specifically, there was a chance you'd get "easier" trades. Back then at least, global trading mechanics were weird sometimes, but I wouldn't wanna say they were necessarily glitchy. So, if you found a glitch, you apparently didn't do a good job explaining why it is a glitch. (And, to be honest with you, it seems to be very rude to say what you said when Super goku was only trying to help you out.) Nescientist (talk) 08:48, 20 December 2016 (UTC)

I honestly never noticed that before, despite spending an unhealthy amount of time on the GTS in multiple generations, so I figured something was wrong. I probably was being rude, and I'm sorry; I thought I was explaining well enough and was frustrated that I wasn't being understood. -- Umbee (talk) 22:28, 21 December 2016 (UTC)

AI acting weird against Komala with Comatose

So, I saw a video (from 26:00 onwards) where a Komala was up against Faba's Hypno. Hypno just repeatedly used Hypnosis against it, despite it not working. This also occurred again in the rematch against Faba post-game. And I also remember it happening against someone else in Marriland's playthrough. It seems the AI doesn't understand that you can't put a Pokemon with Comatose asleep and will repeatedly try anyway. Would this count as a glitch, or is it just bad AI? ☆The Solar Dragon☆ 11:05, 22 December 2016 (UTC)

I think that's just bad AI. This just so happens to be the part of the game I am up to right now, I went and caught a Komala to try it out (although it did mean it was fairly low level). It did seem to use Hypnosis a lot, but it also used Psychic occasionally. It didn't even try to use Nightmare until running out of PP in Hypnosis.

Hau's AI attacking his own ally is definitely a bug; this doesn't seem to be. --SnorlaxMonster 12:05, 22 December 2016 (UTC)