>>47867829Let me be more specific then with my post and back up my initial arguments.
>>47867309this is a bad design. Sorry not sorry, it just is.
>needlessly complexIt's way too complex in silhouette, there are spikes and shit jutting out everywhere, most pokemon designs are incredibly simple and smooth, even ones with spikes like nidoking have a smoothness and simplicity in their designs. This design is going overboard with design elements.
>can't tell what it isAt first glance I legitmately cannot tell what the design is even supposed to be. It's not communicated well at all. When I look at most official pokemon, even the bad ones, I can immediately tell what they are based on. This one is too unclear. I think it's supposed to be a vampire of some kind, but it's not really clear. It seems to have sharp teeth in one of the side drawings, but those aren't visible in the design proper when they really should be as that is a crucial design element that shows what this thing is supposed to be. Also why the "wings" shaped like that? if they wanted to make a vampire thing then make the wings look like bat wings so people actually recognize it's supposed to be a vampire. I get they are trying to be original but realize that being original comes secondary to clearly communicating the idea to the viewer. The horns add extra confusion and are not needed, vampires generally do not have horns. If they wanted to have something above head level, then they could have just made the ears larger, more prominent, and made them look like bat ears (another design element that communicates intent).
They made it humanoid but forgot to actually give it features that make it actually look like a bat/vampire. No, having side notes that show a cloak with the hair down doesn't count because no one is going to see that part in the actual game, same with the teeth. Should have just implemented those things into the design in the first place.
