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

CAP 38 - Part 13 - Prevo # Discussion

Spammernoob

is a Forum Moderator
Moderator
CAP 38 So Far

====

Main Design:

T_kJvVwtemcmzb9ruZbERQ.png




How many pre-evolutions do you think CAP 38 should have (None, One, or Two), and why?

This thread will be open for 36 hours, at which point we will open the poll for this stage. Please remember that usual rules against one-liners are still in effect for this thread!
 
Last edited:
It is of my opinion that instead of being a legendary (:chromera:), mythical (:ramnarok:), or psuedo-legendary (:aurumoth:) we should be a random stat monster like :Archaludon:, as the design's vibe doesn't conform to these categories (pseudo maybe). Thus, CAP38 should only have one pre-evolution, but I dunno if that prevo would be as swole as :duraludon:.
 
Last edited:
Gen III had :salamence: and :metagross: so CAP getting 2 pseudo legendaries is fair. However, evolutions of pokemon that are two separate entities are really strange. There are combinations like :slowbro:+:shellder:, fusions like :calyrex-shadow:, and pairings like :remoraid:+:mantine: but I don't think flavor is allowed to design a whole new fully evolved pokemon for CAP ZU (lmao). Imo the best way to get around this issue is to just ignore it by having no prevos.

We also have decent legendary vibes.
 
I think the 600 bst, unusual coverage for a grass type like meteor beam, and the dual-being nature of the design makes 38 a prime candidate for a proper Legendary, so my preference is None. However I will say I don't agree with the notion that the design can't be iterated on in reverse. Feels a bit disingenuous, especially with how talented are artists can be. In the event of there being support for anything besides Legendary status though, I think Two and pivot to being a pseudo-legendary is also acceptable here.
 
I'd normally go with One because I can't see this as a legendary imo. But I think we should go for Two and make it a pseudo-legendary because it'd be more interesting. It gives me similar vibes to Metagross.
 
I'm in favor of having Two prevos here, there's a lot of elements in the design that lend themselves well to being scaled down and remixed, and I can easily imagine a lot of diversity in potential submissions. There being two entities especially makes me prefer having more evolutions, there's a lot of possibility to develop a relationship between the tree and vine in the pre-evolved forms.

It also feels fitting to make the "Mini-Uber" version of a legendary into a pseudo-legendary.
 
Piping in to join the pseudo-legendary bandwagon by throwing support for Two prevos.

On the topic of the design being two separate entities, I'll like to draw attention to one crucial fact: pip has stated that this is a mystical tree being strangled by a wisteria. Evidently, there is a clear bias on who the main 'driver' is. I'm bringing this up because there is also one canonical example we have for a Grass-type that has two ambiguous beings in one - :Paras: & :Parasect:, and the latter's flavour of being controlled by another plant (Okay, but mushrooms in Pokemon are considered plants, so the logic still stands) is a clear reference point as one avenue we can utilise.
 
I think CAP 38 should have 2 pre-evolutions. Since it's meant to have the same role Eternatus :eternatus: has in Ubers, it shouldn't be so powerful upon birth so that trainers won't immediately use it to battle right after catching it, since it's a mini-legend. Evolving a Pokémon usually requires leveling up, evolution stones, or friendship, which forces trainers to put in the effort to nurture it. After all, it wasn't decided that CAP 38 is a Legendary or Mythical Pokémon—it's only meant to emulate :eternatus:'s role in Ubers.
So I think CAP 38 should really have 2 pre-evolutions.
 
Last edited:
For me, it’s definitely None. It’s a magnificent, deeply mystical design. I think the concept—that the wisteria itself is the "true" Pokémon—is unique and special, and it shouldn't be over-explained through pre-evolutions. Part of the charm lies in that very ambiguity, much like with Dhelmise. The fact that people might mistake the tree for the actual Pokémon is precisely what makes it so intriguing; learning the truth behind the misconception adds a great layer to its lore.

Furthermore, in my opinion, it doesn't give off pseudo-legendary vibes at all. I also believe Pipotchi designed it with the intention of it being a Legendary or Mythical Pokémon, a point he explicitly stated and one I completely agree with:

"I also wanted to do a powerful looking design that could be legendary/mythical if stats went that way, which ended up happening—if you want a proper mythical/legendary origin, then the vine is the serpent Nidhogg strangling the world tree Yggdrasil."​
 
jumping on the Two train - I think the "snake" wisteria aspect is something I'd really like to see iterated upon in prevos, and I actually don't really think this design screams "mythical" at me despite being imposing and complex
 
For me, I will be voting for 2 pre-evolutions. CAP38 is designed to be a mini-Eternadus. Eternadus is only capable of being caught at the end of the main story of Sword/Shield, and because this is meant to be a smaller/weaker version of that, it seems fitting enough to make it a Pseudo.
 
I'm going to go a bit against the grain and say CAP38 should have One pre-evolution. Specifically, that first form would be the wisteria vine before it possesses the tree. So similar logic to the people saying two, but I think the story could just be told with a single pre-evolution; after all, to the people making the Parasect comparison, that line is just two stages. That said, I think it's a case similar to Kubfu. CAP38 is a legendary/mythical, just one of the rare ones with evolutions for story reasons.
 
Two or None are my preferences here: I really like the idea of a grass-type pseudo-legendary, and I think this 'mon pairs nicely with Aurumoth from a typing and design perspective as our two pseudos. Alternatively, this 'mon is also VERY similar to mythicals such as Darkrai and Deoxys, so I can see an argument for no prevos as well. I do prefer prevos in this case: I think this cap has room to evolve for sure and is strongly reminiscent of other three-stage grass types. For instance, see: :tsareena: :roserade: :arboliva: :meowscarada: :leavanny: (also :lilligant-hisui: but that's a two-stager)
 
Back
Top