The official discord link if you wish to join the discord: https://discord.gg/j5RKwCvAFu
Support the wiki on our official Ko-Fi page or Patreon page!
Stabilization Feats: Difference between revisions
m |
|||
Line 15: | Line 15: | ||
|} | |} | ||
<br> | <br> | ||
[[File:Chronoa Stabilization.png|right|thumb|360px|[[Chronoa]]'s existence keeps history stabilized and her death would cause it to collapse (an example of [[Environmental Destruction]]/[[Chain Reactions]].]] | [[File:Chronoa Stabilization.png|right|thumb|360px|[[Chronoa]]'s existence keeps history stabilized and her death would cause it to collapse (an example of [[Environmental Destruction]]/[[Chain Reactions]]).]] | ||
==Background== | ==Background== |
Revision as of 14:21, 4 June 2023
Background
Stabilization Feats involve having characters, objects, etc. sustain a structure through their existence, life force, connection, abilities, etc. on a varying level. These places are dependent on the people sustaining them, and they will most likely cease to exist or fall into disarray should the character, object, etc. die. As mentioned earlier, there is no set capacity on what degree something can be sustained as it could be from something as minimal as a building to even an entire multiverse in scale.
However, not all sustenance feats are valid. Some of them are very questionable on whether or not they actually fit the idea of scaling to Attack Potency. The accepted idea on this wiki of sustaining feats are that they are non-combat applicable Attack Potency, or Environmental Destruction/Chain Reactions. In order to be regular Attack Potency that scales to one's Striking Strength and Durability the following requirements below need to be met.
Stabilization Feat Rules
- Requirement 1: The structure that is being sustained needs to be directly explained and specified. This is to better understand the general scale a certain area is being sustained at.
- Requirement 2: Demonstrate how a character's stabilization should scale to the stabilized structure. Characters should preferably have showings that rival or show influence on a scale of comparability to that of the stabilized structure. For example, a character warping the location, corrupting it, or even doing something extreme as utilizing it for offensive attacks can illustrate how they properly scale to it too. Keep in mind that the rate of a collapse may also influence how a character is rated for statistics. An important note for this requirement is that merely having one's existence stabilize the dimension isn't enough to be considered outright regular Attack Potency, there must be at least some form of proof showing the character has feats on the level of what they stabilize.
- Requirement 3: Our last notable requirement is that you demonstrate why this stabilization feat should be consistent with a character's overall statistics. This is just to avoid any potential outliers.
Possible Common Problems
- The sustenance may be too vague and unexplained to properly count as a feat.
- Structures may only be tied to characters because of their existence, magical properties, or a specific link that is independent of the character's statistics.
- A collapse might potentially be like a domino effect where something/someone that was crucial to the overall support, and that's what may have made it collapse. To give an example, take the idea of a platform supported by four beams. If you break one of the beams, the entire structure can come crumbling down in response.
- Someone may hold a general structure together, but it could be non-viable in that it demonstrably and logically doesn't scale in strength. To explain this idea, take the idea of a paper clip. Papers clipped together fall apart and cannot stay together without the paper clip. However, the paper clip doesn't necessarily do that with power.
- Something's existence may not be fully required for a structure to be stabilized.
- There is nothing to suggest a degree of comparability between the character and the structure.
- Statistics between a character and the sustenance aren't consistent with each other.
Examples
Combat Applicable Attack Potency Examples
- The Triforce and its wielders sustain the Sacred Realm. The artifact has shown it can easily warp the location into what reflects the user's personal desires with its Magic being directly linked to its power output. It has allowed many other users to reach a comparable level of universal power too.
- Koi-Zilla and the other Koi fish have shown to directly sustain the moon and ocean with full control. When Aang fused with La, the Avatar Extras labeled Koi-Zilla as the wrath of the ocean and could produce high levels of Waterbending to back it up.
- Magolor has shown to sustain and immediately collapse an entire dimension after his defeat. It is heavily suggested that he gained this level of power when possessing the Master Crown, and he has shown to manipulate the setting and even using the dimension itself for attacks when fighting against Kirby. He has been stated to control this dimension as well.
Non-Combat Applicable Attack Potency Examples
- Chronoa sustaining history, while one may argue it's through her energy, Chronoa has on many occassions noted that the collapse of history will kill everyone, including herself and beings above her in power. Along with characters comparable to her being afraid of universal destruction. This thus shows her death causing history to collapse is an example of Environmental Destruction or Chain Reactions.
- The Administrator (Tenkuu Shinpan) has shown to sustain an entire realm but can be killed by even a hammer. This seems to suggest that their realm sustenance is more directly tied to their abilities given their title too.
Other Examples
- Vortigern has shown the capability to collapse a tower upon his death. However, the tower was magical. It increased his strength as more levels were added to it, until Vortigern eventually rivalled the original bearer of the power he gained because of the tower's nature.
- Data-Riku has shown to be the embodiment of the journal and the Datascape. However, his existence collapsing the Datascape is more along the lines of that altering his code would alter the rest of the Datascape because he had all of the data inside of him. He essentially acted as a lynchpin to keep the data and records of the journal together rather sustaining it via his own power.
Discussions (Link For Mobile Users):
Discussion threads involving Stabilization Feats |