• Follow our Instagram!
  • Curious about what we're currently doing about bots? Check out the latest updates from staff in this thread.

(Little) Things that annoy you in Pokémon

DrPumpkinz said:
Assuming this bracket had any amount of seeding, I think it's very funny that Totodile and Feraligatr were pitted against relatively unpopular Pokemon and were probably seeded 1st and 3rd, while Croconaw was immediately sentenced to death by 2nd seed Wooper.
Which it's a shame, Croconaw is the coolest of the line. Mid evolution starters tend to have the best designs very often.
 
This isn't really a problem in any way and is more of a "it bugs me for really dumb reasons" thing, but Clangorous Soul costing 1/3 of your max HP to use.

It's perfectly balanced as is, it's just that the only other things in the game that use 1/3 for the math are some recoil moves and Regenerator. It just feels wrong to me and I don't know why lol.
 
I don't like how top heavy the current VGC format is. Of the current top mons, i'd say Basculegion & Whimsicott are the most annoying mons. Basculegion just hits way too hard with the broken Ghost Move & feels very overturned in most areas, with its Stab combo being perfect & adaptability boosted while also having pivoting and incredible bulk for a strong attacker. Immune to Fake Out too. As for Whimsicott - it feels like its Tailwind is nearly guaranteed (quite dangerous with some of the breakers around) & priority Encore makes it WAY too easy to put opponent into checkmate scenarios when clicking moves like Protect. I never played any Urshifu metagames, but I'd figure its similar to that.

I also don't like many other Pokemon in the format. Garchomp and Charizard in particular are both very annoying, as is Floette. A decent amount of this is a skill issue fwiw. But I wish there was a wider pool of counterplay to these Pokemon (that are also serviceable into the rest of the metagame) beyond Megas.
 
Last edited:
This isn't even an annoyance so much as a "huh, funny to think about" detail, but it makes me laugh that Groudon and Kyogre have such similar concepts (Titans who affect the weather to potential world-ending degrees), but such a contrast in (English) ability titles.

Where Groudon has the appropriately extreme "Drought" for the sun, Kyogre's rain ability is "Drizzle," a term usually used for light, sporadic precipitation instead of a prolonged endless fall. "Monsoon" or "Deluge" probably captures the idea better.
 
pika pal said:
This isn't even an annoyance so much as a "huh, funny to think about" detail, but it makes me laugh that Groudon and Kyogre have such similar concepts (Titans who affect the weather to potential world-ending degrees), but such a contrast in (English) ability titles.

Where Groudon has the appropriately extreme "Drought" for the sun, Kyogre's rain ability is "Drizzle," a term usually used for light, sporadic precipitation instead of a prolonged endless fall. "Monsoon" or "Deluge" probably captures the idea better.
I mean that's just how they are in Japanese too Drought is Drought (ひでり) and Drizzle is Rainfall (あめふらし).
 
Magcargo said:
I don't like how top heavy the current VGC format is. Of the current top mons, i'd say Basculegion & Whimsicott are the most annoying mons. Basculegion just hits way too hard with the broken Ghost Move & feels very overturned in most areas, with its Stab combo being perfect & adaptability boosted while also having pivoting and incredible bulk for a strong attacker. Immune to Fake Out too. As for Whimsicott - it feels like its Tailwind is nearly guaranteed (quite dangerous with some of the breakers around) & priority Encore makes it WAY too easy to put opponent into checkmate scenarios when clicking moves like Protect. I never played any Urshifu metagames, but I'd figure its similar to that.

I also don't like many other Pokemon in the format. Garchomp and Charizard in particular are both very annoying, as is Floette. A decent amount of this is a skill issue fwiw. But I wish there was a wider pool of counterplay to these Pokemon (that are also serviceable into the rest of the metagame) beyond Megas.
Yeah its quite a bit less stifled in singles from what I've read. Never got into vgc. It actually made me a bit sad that more teams were carbon copies there than bss, since there are soo many doubles combos. I guess after all testing from countless people over many years, what prevailed is...what you have to run to win. It just sounds awful lol.

Edit: those 2 especially sound nightmarish. Fairy takes the oddball dragons who take water and ghost, hydre comes to mind. But other things are taken, regardless of if they see any real viability ever. I immediately think drampa mega, I run that partly for basc. Scrafty takes it, gl making progress. Cant wall it without def set up? Encore. Those kind force you to be fast or tr(aka fast for a bit.)

EDIT 2: So...think champions switched taunt for power whip in learnset of gliscor wth. Is ok?! erm. If no toxic orb it didn't need a nerf, if later orb that doesn't scratch the surface.
 
Last edited:
The 2 weekly missions in Champion that force you to play a certain way annoys me so much. No not the ones the force usage of certain types. I'm talking about the one that require hitting something 4x SE, and the one that requires a deathless victory.

You would think that hitting 4x SE is super easy because many of the top mons have a 4x weakness (ZardY, KG, Chomp, Whim, Sneasler, Swampert, Pelipper) right? Well I'm currently still 0/5 on that mission this week because I'm playing Gardevoir Maushold.

And the deathless victory mission is even worse and antithetical to what is good in VGC, namely redirection and Fake Out pressure. Things obviously die when you use redirection, but sacking a mon in the back for another round of Fake Out is also gamewinning. Then this mission comes around and says, "hey lose no mon" like it's already not hard enough to do so when you have reached MB.
 
Last edited:
Xeggutor said:
And the deathless victory mission is even worse and antithetical to what is good in VGC, namely redirection and Fake Out pressure. Things obviously die when you use redirection, but sacking a mon in the back for another round of Fake Out is also gamewinning. Then this mission comes around and says, "hey lose no mon" like it's already not hard enough to do so when you have reached MB.
Sacking is a desirable option more often than you'd think even outside of Fake Out or redirection. Sometimes you need a safe switch, Intimidate, or weather reset. It's definitely a super annoying mission to complete.
 
Karxrida said:
Sacking is a desirable option more often than you'd think even outside of Fake Out or redirection. Sometimes you need a safe switch, Intimidate, or weather reset. It's definitely a super annoying mission to complete.
Yea definitely so. I just specifically brought up Fake Out and redirection because these are the examples that really differ from singles to doubles. Considering many singles players only started VGC with the release of Champions, having a mission that requires this actively deters newer players from picking up on the importance of redirection and Fake Out.

I remember in the early days of Champions where I was more starved for resources, I would just load into 3 BSS singles games to complete this mission. Nowadays I would just leave it uncleared, as much as my OCD bothers me.
 
Last edited:
doipy hooves said:
It's worth mentioning that their respective OST names are "Drought" and "Heavy Rain".
speaking of the OSTs, both a drought/heat wave and heavy rainfall are pretty scary irl but I feel the OSTs didn't really capture this well. Heavy Rain just sounds like standard villian music, not particularly scary compared to Drought just outright sounding like the apocalypse.

I don't think sapphire or its remake did a very good job making Kyogre as scary as it probably should be compared to how well they nailed Groudon being calamitous in ruby and its remake.
 
It's mildly annoying that Farigiraf's name is a palindrome.

Girafarig I get it, because the mon itself is head - neck - torso - neck - head (ABCBA). Farigiraf being CBABC would imply torso - neck - head - neck - torso, which sounds like a sleep paralysis demon.

Farigiraf has both heads and necks overlapping together, followed by the torso at the very end. So I can see a case for it being ABABC or AABBC, neither of which palindromic, but that's how the mon looks.

Japanese has it as Rikikirin, which is ABBAC, not quite it either.
Korean (Kikiring) and Chinese (Qíqílín) is simply AAB, but I think it does a good job at depicting how the mon actually look.
 
Last edited:
Xeggutor said:
It's mildly annoying that Farigiraf's name is a palindrome.

Girafarig I get it, because the mon itself is head - neck - torso - neck - head (ABCBA). Farigiraf being CBABC would imply torso - neck - head - neck - torso, which might just be my sleep paralysis demon.

Farigiraf has both heads and necks overlapping together, followed by the torso at the very end. So I can see a case for it being ABABC or AABBC, neither of which palindromic, but depicts Farigiraf's design better.

Japanese has it as Rikikirin, which is ABBAC, not quite it either.
I think Korean (Kikiring) and Chinese (Qíqílín) has it the best, being just simply AAB.

So either:

Giragiraf = head - neck - head - neck - torso (ABABC)
Gigiraraf = head - head - neck - neck - torso (AABBC)
 
Pikachu315111 said:
So either:

Giragiraf = head - neck - head - neck - torso (ABABC)
Gigiraraf = head - head - neck - neck - torso (AABBC)
Assuming A = gi/ig, B = ra/ar, C = f,
If you look from the back, you also get Farigarig (CBABA) and Fararigig (CBBAA).
:psywoke:
 
So from what I can gather, the romanization of Girafarig's Japanese name (Kirinriki) isn't a palindrome but the kanji (キリンリキ) is. Meanwhile, Farigiraf's romanized Japanese name is an inversion of Girafarig's (Rikikiran) and the kanji just flat-out isn't a palindrome (リキキリン).

The potential disconnect here could stem from differing localization philosophies and/or different naming practices by the GSC and SV devs from projects over two decades apart. Plus I have no idea if Girafarig's Japanese kanji being a palindrome was even intentional or just a coincidence that the localizers picked up on to use as a basis for the English name. However, I'd argue that the SV localization doesn't seem to be a strictly incorrect interpretation regardless, as Farigiraf still falls in line with being an inversion of Girafarig like the original Japanese name.
 
Last edited:
Karxrida said:
So from what I can gather, the romanization of Girafarig's Japanese name (Kirinriki) isn't a palindrome but the kanji (キリンリキ) is. Meanwhile, Farigiraf's romanized Japanese name is an inversion of Girafarig's (Rikikiran) and the kanji just flat-out isn't a palindrome (リキキリン).

The potential disconnect here could stem from differing localization philosophies and/or different naming practices by the GSC and SV devs from projects over two decades apart. Plus I have no idea if Girafarig's Japanese kanji being a palindrome was even intentional or just a coincidence that the localizers picked up on to use as a basis for the English name. However, I'd argue that the SV localization doesn't seem to be a strictly incorrect interpretation regardless, as Farigiraf still falls in line with being an inversion of Girafarig like the original Japanese name.
From what my Japanese friend told me, Girafarig is the only Pokemon with a palindromic name in Katakana that isn't just the same radical twice (Pidgey, Clefairy, Cramorant). It's also kinda of a huge stretch to even interpret the リキ* part of キリンリキ as Psychic-adjacent to begin with, so it being a palindrome kinda feels intentional.

Admittedly I don't understand the intention with it's naming after evolution, it feels annoying that Farigiraf is the only localisation that kept a palindromic naming when Japanese, Chinese and Korean broke it, especially when making palindromes in the latter languages is arguably easier than in English.

Edit:
Just to make sure I'm not being a Farigiraf hater, I really really like what they did with their naming in Chinese (麒麟奇 qí lín qí >奇麒麟 qí qí lín). It's not a direct palindrome in terms of words, but still does so with the pronunciation, which kinda fits because Girafarig's tail is not a direct mirror image to begin with. And the best part is that the name perfectly explains how we have a normal/psychic giraffe, with 麒麟** being the giraffe part, and 奇 the psychic part, so having it as 奇麒麟 directly shows that the psychic part has come to the front.

Additional notes:
*Bulbapedia interpreted リキ(力)as a part of 念力 (telekinesis), but 念 is what adds the psychic connotation. 力 is way more commonly used to refer to physical strength, something that is present in the Machop line, and the HM for Strength.
**麒麟 apparently this isn't actually a giraffe, but rather some mythological creature (Kirin). But there's this imperial envoy who voyaged to Africa brought a giraffe back and told the emperor that he brought a Kirin back. But that kinda adds justification for psychic/supernatural connotation, which is really cool.
 
Last edited:
Xeggutor said:
From what my Japanese friend told me, Girafarig is the only Pokemon with a palindromic name in Katakana that isn't just the same radical twice (Pidgey, Clefairy, Cramorant). Katakana does not innately carry any meaning, and it's kind of a huge stretch to even interpret the リキ part of キリンリキ as Psychic-adjacent to begin with, so it feels like it being a palindrome feels intentional.
Admittedly I don't understand the intention with it's naming after evolution, it feels annoying that Farigiraf is the only localisation that kept a palindromic naming when Japanese, Chinese and Korean broke it, especially when making palindromes in the latter languages is arguably easier than in English.

Well, thinking about it, there is another way you can justify the English name.

So the evolution idea behind Farigarif is that Girafarig's "auxiliary head" has moved from being its tail to becoming a sort of hood for the "main head". If we're assigning parts of the name to parts of this Pokemon, you can then argue that the "main head" is called "Giraf" and the "auxiliary head" is "Farig". When they're Girafarig the order of their name makes sense as they're on either send of the body. But when it evolves Farig is now covering Giraf, so now the auxillary's name will come first followed by main's: Farigiraf. Heck, with this we can even still use the "ABCBA" methodology: We start with the outer auxillary head, go down the outer auxillary neck, the body provides the base where both necks connect, thus we can go up the inner main neck, which leads to the inner main head; a non-gruesome "inside-out" design philosophy thus deserving of an inside-out name.

Though the main issue with Farigiraf's name in most languages is that it relies on being based on Girafarig's name to make sense. While most obvious in the ones which use its English name as it tries to keep the palindrome, Asian countries try focusing on the double head by having a repeating syllable. But that only makes sense to do if they're working off an existing name, if this was a completely new two-headed Pokemon with no ties to another I'd imagine instead of trying to do some double syllable gimmick it would have a word meaning "two" somewhere in the start of its name, such as they did with the Doduo or Deino family.
 
Pikachu315111 said:
Well, thinking about it, there is another way you can justify the English name.

So the evolution idea behind Farigarif is that Girafarig's "auxiliary head" has moved from being its tail to becoming a sort of hood for the "main head". If we're assigning parts of the name to parts of this Pokemon, you can then argue that the "main head" is called "Giraf" and the "auxiliary head" is "Farig". When they're Girafarig the order of their name makes sense as they're on either send of the body. But when it evolves Farig is now covering Giraf, so now the auxillary's name will come first followed by main's: Farigiraf. Heck, with this we can even still use the "ABCBA" methodology: We start with the outer auxillary head, go down the outer auxillary neck, the body provides the base where both necks connect, thus we can go up the inner main neck, which leads to the inner main head; a non-gruesome "inside-out" design philosophy thus deserving of an inside-out name.

Though the main issue with Farigiraf's name in most languages is that it relies on being based on Girafarig's name to make sense. While most obvious in the ones which use its English name as it tries to keep the palindrome, Asian countries try focusing on the double head by having a repeating syllable. But that only makes sense to do if they're working off an existing name, if this was a completely new two-headed Pokemon with no ties to another I'd imagine instead of trying to do some double syllable gimmick it would have a word meaning "two" somewhere in the start of its name, such as they did with the Doduo or Deino family.
Nah, you're right that the naming still makes sense and I understand that.

I still really like the name Farigiraf. It's really clever and iconic and is possibly one of the best names you can give to a mon related to Girafarig.
I just think it belongs to a split evolution / alternate form where the main-head and the tail-head still operate on different ends of the body in a symmetrical manner.

I'm just annoyed that "Farigiraf" is a palindromic name on a visual design whose entire point is that it's not longer palindromic. I know Giragiraf would probably sound stupid, there is probably a funny pun with ____giraf that isn't palindromic. Heck, I've heard people at the start of the generation mispronounce it as Farifarig which theoretically does match how it looks and is named in other languages.
 
Last edited:
CPU said:
I hate that Farigiraf's G is officially pronounced with a hard G sound. Giraffe isn't, Girafarig('s first G) isn't. It sounds terrible.
granted I think pronouncing it like a j runs into it sounding like Fridgeraf in a lot of north american accents, lmao.
 
Well I beat Emerald for the first time... But y'all wanna know what my team was before the Elite 4?

Screenshot_2026-08-05-12-22-06-147.webp


Only 4 mons around the mid 40s-early 50s with an HM Mule for Waterfall. Note that I made sure to beat most trainers in each area and have really only caught these mons at all.

Yeah... grinding was DEFINITELY not an issue in these games... zoomers just have TikTok brain and a bad attention span... This totally isn't just terrible game design.


image.png
 
LPBvgc said:
Yeah... grinding was DEFINITELY not an issue in these games... zoomers just have TikTok brain and a bad attention span... This totally isn't just terrible game design.
Running only a team of 4 makes it significantly easier to keep everything leveled without grinding. If you try to engage with the game the way it implicitly wants you to and have a full team you will run into problems. Also, I was replaying Colosseum recently and you're basically forced into a grind session immediately after Miror B. lol.

JRPGs telling people "go grind loser lmao" has been a legitimate pain point since the genre's inception 40 years ago. The shift to making it easier shouldn't be blamed on TikTok brain when it simply boils down to people hating it. Same reason why random encounters tend to be found dead in a ditch nowadays.
 
Last edited:
the best rpg take is that leveling is a outdated system and progression should come from actually cool and material things rather than what number

like ive been playing splatoon raiders, good game, but the level up system is dumb compared to the much better progression of upgrading your gadgets/chips that let you do new things and experiment. that is fun progression while levels only have three modes: 1. you're underleveled and you might just lose because you don't have the stats 2. the game plays normally 3. you are overleveled and you might just win because you have the stats (boring)

i keep going back to "pokemon would totally work without level ups" bc its just true imo, new moves, EVs and evolution are enough progression that make training the same pokemon rewarding without needing levels
 
Back
Top