• This forum is strictly intended to be used by members of the VS Battles wiki. Please only register if you have an autoconfirmed account there, as otherwise your registration will be rejected. If you have already registered once, do not do so again, and contact Antvasima if you encounter any problems.

    For instructions regarding the exact procedure to sign up to this forum, please click here.
  • We need Patreon donations for this forum to have all of its running costs financially secured.

    Community members who help us out will receive badges that give them several different benefits, including the removal of all advertisements in this forum, but donations from non-members are also extremely appreciated.

    Please click here for further information, or here to directly visit our Patreon donations page.
  • Please click here for information about a large petition to help children in need.

Are statements considered calc stacking?

Messages
221
Reaction score
95
In this thread I know it was determined that they were not and a new section was proposed to be added to the calc stacking page specifying that, but the section was never added.

For example, if character A is stated to be 100m/s could you use that to calculate the speed of character B?

What about if character A is stated to be 100m/s and character B is stated to be as fast or faster than character A, could you use character A’s speed in a calculation of character C blitzing character B?

Or what if character A is stated to be 100m/s and character B is shown to be as fast or faster than character A, could you use character A’s speed in a calc for character C blitzing character B?

It seems that most of these were voted on for being usable, but the section on the calc stacking page was never added.
 
Not necessarily, calc stacking is what you get if you use an Accepted calculated feat and simply assume that's the speed and/or energy output of everything else the character does to stack AP or speed multipliers. But if it's literally spelled to us in the text that someone is running exactly 100 m/s, then using that for basis of calculations wouldn't be calc stacking. Also, there is a difference between Calc Stacking and KE fallacy to take into account.
 
But if it's literally spelled to us in the text that someone is running exactly 100 m/s, then using that for basis of calculations wouldn't be calc stacking.
Why was this rejected as calc stacking then smh.

 
Why was this rejected as calc stacking then smh.
It seems like some of the calc group members still consider using statements as calc stacking despite it being voted on. That’s why I feel like the section proposed at the end of the thread should’ve been added to the calc stacking page, or at least a modified version of it to keep a consensus. Why was the section never added in the first place?
Had a similar concern as DMUA recently rejected one of my calculations on the basis that explicit speed statement can constitute calc stacking despite their opinion seemingly being shot down in that very thread.
Same thing here
 
Why was this rejected as calc stacking then smh.

Had a similar concern as DMUA recently rejected one of my calculations on the basis that an explicit speed statement can constitute calc stacking despite their opinion seemingly being shot down in that very thread.
"Calc Stacking" is technically still the wrong terminology. It is important to read this page which elaborates our kinetic energy calculation rules, it might have actually been related to that is why there was some rejection instead of the reason being "Calc Stacking." I believe Agnaa has mentioned the better word usage here before.
 
I am pretty sure blatant in-verse speed statements cannot count as calc-stacking, otherwise every single bullet dodging calc or natural phenomena-dodging calc we have would be null and void by now.

Calc stacking is only when you make a new calc by yourself and then use that value to find another calculated value, bigger or smaller.
 
The only time a statement wouldn't be applicable for a calc is if the statement is completely bullshit and is the author just saying words without knowing what it means (like "oh that's 10 tons" for lifting a mountain or something ridiculous) and thus not applicable, but for completely different reasons that isn't calc stacking, or if for whatever the statement wouldn't apply in that situation like "oh they held back" or the statement itself is context sensitive (they can only hit said speed under certain conditions, etc).

Something like "oh he punches at mach 1", and then some dude dodges his punch, pretty straightforward shit, that isn't calc stacking, it's using a confirmed value to calc, no different from say, a dude dodging a bullet fired from a m16.
 
"Calc Stacking" is technically still the wrong terminology. It is important to read this page which elaborates our kinetic energy calculation rules, it might have actually been related to that is why there was some rejection instead of the reason being "Calc Stacking." I believe Agnaa has mentioned the better word usage here before.
My calc didn’t use KE either.
 
Back
Top