HeaLnDeaL
Let's Keep Fighting
Approved by jas61292
Previously it was decided here that Mega Evolutions would not be part of the main CAP creation process. However, the possibility of giving Mega Evolutions to past CAPs was left open and reserved for a future discussion. Well, that discussion has come now it seems.
Of course, I can imagine that some of you might have concerns with possible ways to actually go about making these Mega Evolutions. However, for now I think that the process is actually less important than what we want out of the potential MEvos in question, if we do want them at all. In other words, I think coming up with the goals of our end result is necessary prior to constructing a process that will in turn produce these results. Note that a lot of the assumptions that follow will be framed in the logic of if we already do agree to create MEvos for past CAPs. This is not meant to paint MEvos as an inherently logically option, and such assumptions will be used to generate different avenues (and potential problems) associated with the choice of having MEvos. Not allowing MEvos itself is a perfectly legitimate option. However, for the sake of discussion, talking about options that do allow us to make MEvos will hopefully help us explore the possibilities and spot issues that might arise that would generally make the option unfavorable.
If we create MEvos for past CAPs, how should we choose which CAPmon(s) to build upon? Should MEvos try to offer new and unique concepts themselves, or should they just try to enhance the original role of the CAPmon?
Ultimately, some of our biggest concerns are the prospects of actually revising past CAPs. Adding a Mega Evolution inherently creates a revision. As it currently stands, the CAP meta is a uni-generational tier; no 4th or 5th gen CAP meta exists, and thus adding a mega to a past CAPmon has the potential of conflicting with the mon’s original intentions upon the time of its creation. If the mega turns out to be completely worthwhile over the base form 100% of the time, then will the base form’s competitive intentions no longer be preserved? Should this even be a concern, or do the generational shifts and the different mix within the CAP meta already obscure a CAPmon’s original intention?
Between the shift from Gen 5 to 6, many of the Pokémon that received MEvos also received new moves, whether it be from breeding, TMs, etc. Therefore, it could be argued that if we decide to give past CAPmons MEvos that we could also update their movepools. Does updating movepools pose a greater risk to the preservation of the CAPmon’s original intent? If we allow the updating of movepools at the same time as the creation of MEvos does it just needlessly complicate the process? Or is it acceptable as long as we come up with an agreed set of rules that apply to updating moves?
Essentially, we should try to weigh how important the preservation of past creation is, and how much MEvos and related changes would impede upon this preservation. Furthermore, I also think it’s important whether or not we want a playtest for any new MEvos that are made, if any are made at all. A playtest might send the message that we are trying to make something competitive, but at the same time could detract from the playtests of the main CAP process. Do we want to make MEvos just for fun, or do we want this to be a competitive endeavor?
Perhaps what makes the issue of MEvos for past concepts so complex is that we are faced with multiple questions that are fairly independent. Whether we want a playtest is for the most part unrelated to whether or not we to allow for additional movepool additions. Below, in place of concrete proposals, I have listed different questions to explore:
1) Do we want to allow Mega Evolutions for past CAPs? Is exploring the mechanic of mega evolution a good reason to "mess with" past CAP creations? What are the positives of allowing Mega Evolutions for past CAPs?
2) Do we want to make MEvos just for fun or for a competitive goal?
3) Do we want to allow additional movepool revisions to occur during the creation of MEvos? (If so, will we have restrictions on this?)
4) Do we want the MEvo to be an enhanced version of the original concept, or is a new concept altogether feasible? Or would either option be acceptable depending on the situation?
5) Do we want to have the MEvos on the battle simulator? If so, do we want to have a playtest for MEvos?
Feel free to discuss your opinions on these or point out related concerns that I missed. However, for the time being, it is advisable that proposals regarding actual Mega Evolution creation processes are not discussed. We all know there needs to be an abilities stage where a single ability is chosen and a stats stage where a new stat spread with an additional 100 BST boost. However, what we actually want our end goal for MEvos to be, if we want them at all, will likely decide how to go about drafting an actual MEvo creation process. Therefore, talking about these end goals if more important for the time being. Once a consensus is made, and if the consensus allows the creation of MEvos for past CAPmons, then we can shift the discussion into drafting an actual process guide.
Edit: Expanded question #1
Mega Evolutions for Past CAPs
Previously it was decided here that Mega Evolutions would not be part of the main CAP creation process. However, the possibility of giving Mega Evolutions to past CAPs was left open and reserved for a future discussion. Well, that discussion has come now it seems.
Of course, I can imagine that some of you might have concerns with possible ways to actually go about making these Mega Evolutions. However, for now I think that the process is actually less important than what we want out of the potential MEvos in question, if we do want them at all. In other words, I think coming up with the goals of our end result is necessary prior to constructing a process that will in turn produce these results. Note that a lot of the assumptions that follow will be framed in the logic of if we already do agree to create MEvos for past CAPs. This is not meant to paint MEvos as an inherently logically option, and such assumptions will be used to generate different avenues (and potential problems) associated with the choice of having MEvos. Not allowing MEvos itself is a perfectly legitimate option. However, for the sake of discussion, talking about options that do allow us to make MEvos will hopefully help us explore the possibilities and spot issues that might arise that would generally make the option unfavorable.
If we create MEvos for past CAPs, how should we choose which CAPmon(s) to build upon? Should MEvos try to offer new and unique concepts themselves, or should they just try to enhance the original role of the CAPmon?
Ultimately, some of our biggest concerns are the prospects of actually revising past CAPs. Adding a Mega Evolution inherently creates a revision. As it currently stands, the CAP meta is a uni-generational tier; no 4th or 5th gen CAP meta exists, and thus adding a mega to a past CAPmon has the potential of conflicting with the mon’s original intentions upon the time of its creation. If the mega turns out to be completely worthwhile over the base form 100% of the time, then will the base form’s competitive intentions no longer be preserved? Should this even be a concern, or do the generational shifts and the different mix within the CAP meta already obscure a CAPmon’s original intention?
Between the shift from Gen 5 to 6, many of the Pokémon that received MEvos also received new moves, whether it be from breeding, TMs, etc. Therefore, it could be argued that if we decide to give past CAPmons MEvos that we could also update their movepools. Does updating movepools pose a greater risk to the preservation of the CAPmon’s original intent? If we allow the updating of movepools at the same time as the creation of MEvos does it just needlessly complicate the process? Or is it acceptable as long as we come up with an agreed set of rules that apply to updating moves?
Essentially, we should try to weigh how important the preservation of past creation is, and how much MEvos and related changes would impede upon this preservation. Furthermore, I also think it’s important whether or not we want a playtest for any new MEvos that are made, if any are made at all. A playtest might send the message that we are trying to make something competitive, but at the same time could detract from the playtests of the main CAP process. Do we want to make MEvos just for fun, or do we want this to be a competitive endeavor?
Perhaps what makes the issue of MEvos for past concepts so complex is that we are faced with multiple questions that are fairly independent. Whether we want a playtest is for the most part unrelated to whether or not we to allow for additional movepool additions. Below, in place of concrete proposals, I have listed different questions to explore:
1) Do we want to allow Mega Evolutions for past CAPs? Is exploring the mechanic of mega evolution a good reason to "mess with" past CAP creations? What are the positives of allowing Mega Evolutions for past CAPs?
2) Do we want to make MEvos just for fun or for a competitive goal?
3) Do we want to allow additional movepool revisions to occur during the creation of MEvos? (If so, will we have restrictions on this?)
4) Do we want the MEvo to be an enhanced version of the original concept, or is a new concept altogether feasible? Or would either option be acceptable depending on the situation?
5) Do we want to have the MEvos on the battle simulator? If so, do we want to have a playtest for MEvos?
Feel free to discuss your opinions on these or point out related concerns that I missed. However, for the time being, it is advisable that proposals regarding actual Mega Evolution creation processes are not discussed. We all know there needs to be an abilities stage where a single ability is chosen and a stats stage where a new stat spread with an additional 100 BST boost. However, what we actually want our end goal for MEvos to be, if we want them at all, will likely decide how to go about drafting an actual MEvo creation process. Therefore, talking about these end goals if more important for the time being. Once a consensus is made, and if the consensus allows the creation of MEvos for past CAPmons, then we can shift the discussion into drafting an actual process guide.
Edit: Expanded question #1
Last edited: