You can write a summary if you wish, yes.
Okay. So, to summarize my entire proposal here.
The Issue With Our Calc Stacking Rule
As written on the calc-stacking page currently, this is the reason why we don't allow the use of calced speed for other feats:
Using speed of characters or attacks calculated at other instances can't be used, as characters and attacks can vary in speed. This is the case regardless of whether the character is seriously trying to do his best or anything similar.
Like I said in the beginning, the
general idea of this is still fine with me for us to use here. My proposal is not to remove this rule. My proposal, however, is for us to change
the way we apply this rule to the site. Here is why this is a problem.
THE ONLY reason why our site considers using calced speed for other feats calc stacking for high results, is because of this idea that a character and their attacks can have varying speeds. Or in other words, character's magically move slower than they normally move at, even when they are serious. Not only was this never given a proper explanation of why this would happen, this literally makes no sense and is inherently flawed logic to an extreme.
Statistics like speed
are not assumed to be at distinctly different levels across instances here, under
normal circumstances. In other words, when a character is serious in the middle of battle,
doesn't lack a power-up,
doesn't purposely lower themselves,
doesn't have their stats altered, and has otherwise
no reason to be moving at slower speeds, we take them to move at the same levels of speed they always move at. Speed isn't something disproportionate like this.
Because speed isn't disproportionate like this, and will not normally change across different instances a character is involved with in their series, there is no legitimate reason to say a character's calculated speed from one instance couldn't ever apply to the character in another instance. How we generally treat a character's speed completely goes against what the calc stacking page says, and gives no real justification to ban the use of calced speed for characters. This is why I advocate for this rule to not be removed, but changed.
My Proposal To Fix This Issue
My proposal is simple. To fix this, we should allow the use of a character's calculated speed, on
a CASE BY CASE basis.
If the Character who has a calced speed is getting blitzed, reacted to, or dodged has
a justified reason to be using their normal speed, that character should be allowed to have there calced speed applied, as they won't be moving slower in this instance to make us think it can't be applied.
At the same time, we can still ban their calced speed from being used if the character has a justified reason to NOT be using their normal speed. Such as, are they fatigued? Are they purposely moving slower? Did they lack a power-up? Did they have their stats altered? Reasons like this would still allow us to restrict calced speed from being used.
Hence forth, we make this rule case by case.
How We Can Restrict Calc-Stacking Under These New Conditions (PLEASE READ!!!)
On top of making this case by case, I also have a proposal on how to restrict the use of accepted calc stacking.
PLEASE READ THIS, as this was said earlier but has only now been noticed.
To prevent someone making chains of calc stacking when using a character's calced speed, we can give calc stacking exactly the same scrutiny we give
Multipliers. We give parameters that need to be met for a character's calced speed to be applied, and then, we increase the burden of proof the higher someone tries calc stacking feats.
@Agnaa summed this up in a great way higher above:
"How would you feel if the standards were essentially just "Give calc-stacked results the same scrutiny as Multipliers"? Substituting "It has to be a statement from a reliable source" with "There cannot be anything indicating they're slower (holding back, being fatigued, lacking a powerup, etc.)
Low increases won't require much scrutiny except for the character with the higher result actually being shown as stronger/faster. While higher increases (over 100x) will start requiring supporting feats on that level not achieved through calc-stacking."
For this reasoning, the solutions given and the parameters set to still safely keep it under control, calc stacking should be able to be accepted on a case by case basis.
