approved by Ludicrousity
credit to Reviloja753 for the idea
"Hah-hah-hah! Thanks to the continued cooperation of everyone on Team Rocket, our army of Fusion Evolutions has been flourishing with more and more powerful creations by the dozen!"
"What do you mean, doctor?"
"...And your plan?"
"Very well. I await your results."
"Okay, let me see here..."
"If I use this piece of the Fusion Stone on Magby and Elekid... Huh? The fusion seems to have worked, but there is still energy left within the stone. Could this be...inviting me to alter the DNA of the fusion? Oho! This is precisely what I was searching for: a reason for experimentation on lower-stage Pokemon fusions! I shall report my findings posthaste!"
.
.
.
.
.
"Anything to report?"
handed to Giovanni
"Hmm... Much easier DNA manipulation, huh? Excellent work, doctor. I suggest that you present your findings to the Grunts, in the form of a side project with a name of your choice."
.
.
.
.
.
"Listen up, Grunts! The reason why I called you all here is to introduce a side project that I call Fusion Prevolutions. Our test subjects shall be currently documented Fusion Evolutions of two parents with lesser forms. You are to find their lowest stage forms and fuse them together based on a set of guidelines that I shall provide. Also keep in mind that these Fusion Prevolutions are to be reported with the intention that they will only face other prevolutions in battle. That is all. Dismissed!"
"Aye, Sir!"
====================================
Submission Template and Guidelines
Derived Fusion: Which existing fusion is the basis for this prevolution? For example, Magmovire.
Prevolution Components: What are the two lowest-form Pokemon involved in the prevolution? For example, Magby / Elekid.
Prevolution Name: Give the prevolution a custom name that somehow ties the two components together. For example, Elemag.
New Type: Give the prevolution a typing that takes one type from each component, even if the typing differs entirely from that of the derived fusion. (In some cases, like FE #188 Escagon (Escavalier + Flygon), the typing must differ entirely.) For example, Elemag must be Fire/Electric.
Base Stats: As with any Fusion Evolution, start off by taking the average of each base stat, rounded half down. For example, Elemag would start off with 45 / 69 / 37 / 67 / 55 / 89.
What to do afterwards depends on whether or not the components of the derived fusion share the same Egg group--in other words, whether the derived fusion is Parent or DNA.
New Ability and desc: The Ability of the prevolution can either be that of its derived fusion (as long as it's justifiable flavor-wise, as in no out-of-the-blue form changes or Levitate variants), or a combination of one Ability from each prevolution component. However, if deciding upon the latter step, the Ability combination cannot be the same as that of the derived fusion, without being completely the same. (Name, effect, all that.) By inheritance or otherwise, if the resulting Ability is a combination of two of the same Ability (which ends up simply being identical to the Ability in question), then the prevolution gets an extra +5 to all stats.
Role Identification: Discuss competitive aspects of the prevolution. This can involve outlining pros and cons, explaining the previous fields, and/or bringing up some notable moves from which the prevolution can benefit.
Dex Entries (*NEW*): Give some flavor to the prevolution and its derived fusion. For example, what is the origin and behavior of the species in question? The prevolution and derived fusion will most likely be roughly the same in terms of typing, Ability, and even role, so this is the place to make a similar submission unique or a differing submission justifiable.
Voting
After submission phase, users vote for the prevolution submission(s) that they wish to have irrevocably associated with each of the fusions in the slate. Here is how it works:
Miscellaneous
Fusion Prevolutions get boosted by Eviolite--partly because both components are guaranteed to be NFE, partly because Eviolite is an integral part of Little Cup, and partly to compensate for the lack of usable Mega Stones. Species-exclusive Z-Crystals, however, cannot be used by Fusion Prevolutions.
Fusion Prevolutions do not have access to the Fusion Moves of their derived fusions, because some Fusion Moves contain component moves that are not learned by the prevolution components.
Current Banlist
credit to Reviloja753 for the idea
"Hmm... I feel like something is missing..."
"Think about it. Considering the power level of most of our fusions, it seems that they tend to consist of well developed parents or have an Ability to compensate. But what of the unevolved Pokemon...?"
"If you would excuse me, I wish to conduct some independent experimentation."
.
.
.
.
.
.
.
.
.
"Okay, let me see here..."
"If I use this piece of the Fusion Stone on Magby and Elekid... Huh? The fusion seems to have worked, but there is still energy left within the stone. Could this be...inviting me to alter the DNA of the fusion? Oho! This is precisely what I was searching for: a reason for experimentation on lower-stage Pokemon fusions! I shall report my findings posthaste!"
.
.
.
.
.
"Sir Giovanni, I have returned."
"Naturally."
handed to Giovanni
"Thank you, Sir."
.
.
.
.
.
"Listen up, Grunts! The reason why I called you all here is to introduce a side project that I call Fusion Prevolutions. Our test subjects shall be currently documented Fusion Evolutions of two parents with lesser forms. You are to find their lowest stage forms and fuse them together based on a set of guidelines that I shall provide. Also keep in mind that these Fusion Prevolutions are to be reported with the intention that they will only face other prevolutions in battle. That is all. Dismissed!"
"Aye, Sir!"
====================================
Submission Template and Guidelines
Derived Fusion:
Prevolution Components:
Prevolution Name:
Typing:
Base Stats:
Ability:
Role Identification:
Dex Entries:
Code:
[IMG]http://play.pokemonshowdown.com/sprites/xyani/a.gif[/IMG][IMG]http://play.pokemonshowdown.com/sprites/xyani/b.gif[/IMG]
[hide=AB][B]Derived Fusion:[/B] AB
[B]Prevolution Components:[/B] A / B
[B]Prevolution Name:[/B] AB
[B]Typing:[/B] A / B
[B]Base Stats:[/B] 0 / 0 / 0 / 0 / 0 / 0 (+0 HP, +0 Atk, +0 Def, +0 SpA, +0 SpD, +0 Spe)
[B]Ability:[/B] [I]Ab[/I] (A + B) - Aaabbb.
[B]Role Identification:[/B] Aaabbb
[B]Dex Entries:[/B] Aaabbb[/hide]
Prevolution Components: What are the two lowest-form Pokemon involved in the prevolution? For example, Magby / Elekid.
Prevolution Name: Give the prevolution a custom name that somehow ties the two components together. For example, Elemag.
New Type: Give the prevolution a typing that takes one type from each component, even if the typing differs entirely from that of the derived fusion. (In some cases, like FE #188 Escagon (Escavalier + Flygon), the typing must differ entirely.) For example, Elemag must be Fire/Electric.
Base Stats: As with any Fusion Evolution, start off by taking the average of each base stat, rounded half down. For example, Elemag would start off with 45 / 69 / 37 / 67 / 55 / 89.
What to do afterwards depends on whether or not the components of the derived fusion share the same Egg group--in other words, whether the derived fusion is Parent or DNA.
- If the derived fusion is Parent, add +5 to each base stat (50 / 74 / 42 / 72 / 60 / 94 in the Elemag example), and then add a total of 20 BST--with no more than 10 in each stat--afterwards.
- Otherwise, add a total of 30 BST, with no more than 15 in each stat.
New Ability and desc: The Ability of the prevolution can either be that of its derived fusion (as long as it's justifiable flavor-wise, as in no out-of-the-blue form changes or Levitate variants), or a combination of one Ability from each prevolution component. However, if deciding upon the latter step, the Ability combination cannot be the same as that of the derived fusion, without being completely the same. (Name, effect, all that.) By inheritance or otherwise, if the resulting Ability is a combination of two of the same Ability (which ends up simply being identical to the Ability in question), then the prevolution gets an extra +5 to all stats.
Role Identification: Discuss competitive aspects of the prevolution. This can involve outlining pros and cons, explaining the previous fields, and/or bringing up some notable moves from which the prevolution can benefit.
Dex Entries (*NEW*): Give some flavor to the prevolution and its derived fusion. For example, what is the origin and behavior of the species in question? The prevolution and derived fusion will most likely be roughly the same in terms of typing, Ability, and even role, so this is the place to make a similar submission unique or a differing submission justifiable.
Voting
After submission phase, users vote for the prevolution submission(s) that they wish to have irrevocably associated with each of the fusions in the slate. Here is how it works:
- For each fusion, vote for no more than 1 prevolution submission. Keep in mind that votes are simply counted, not weighted.
- If you submitted for the slate in question, you can cast no more than 3 votes for your own submissions.
- If one or more submission(s) end up with the highest number of votes, there will be a tiebreaker to determine the true winner(s). During the tiebreaker, each user only votes for 1 submission per prevolution, with no self-voting involved.
Miscellaneous
Fusion Prevolutions get boosted by Eviolite--partly because both components are guaranteed to be NFE, partly because Eviolite is an integral part of Little Cup, and partly to compensate for the lack of usable Mega Stones. Species-exclusive Z-Crystals, however, cannot be used by Fusion Prevolutions.
Fusion Prevolutions do not have access to the Fusion Moves of their derived fusions, because some Fusion Moves contain component moves that are not learned by the prevolution components.
Current Banlist
- Dragon Rage and Sonic Boom
- Fusion Prevolutions involving Scyther and/or Type: Null
Last edited: