- 555
- 47
But that would be calc stacking 
-
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.
isshiki iron rod speed
- Thread starter 4candies
- Start date
-
- Tags
- #isshiki ōtsutsuki
- 555
- 47
The never ending cycle of VsBattle arguments
- 555
- 47
Not a calc guy, so I really don't know honestly
- 555
- 47
and given the less attention there giving to this thread, they are probably trying to avoid the can of worms this is going to open
Testarossa002
Username Only- 1,389
- 1,194
The calc from it is not exactly relevant
He could react "naturally" to a light speed attack
The basis for Thunder bagua was that Luffy called a LS attack "slow" even though the feat was like sub Rel+
Applying the same logic here wouldn't be a stretch
No to mention that the version of Naruto that could react naturally to the LS attack was <<His usual base self as he couldn't use chakra at all
- 634
- 606
Testarossa002
Username Only- 1,389
- 1,194
Well yeah
It was working on a premise that hasn't been accepted yet
That's what this thread is for
- 14,866
- 12,373
If the speed wasn't stated for the object itself, it's calc stacking.
We don't do calc stacking because it applies a large multiplier on characters' stats for every single decent feat they perform, gradually getting further and further away from anything actually shown in the text. Even if you think those calcs multiplying on each other is justified in the text, it amplifies errors in our calcs. If pixel-scaling in our calcs is off by 10% that doesn't really matter in one calc, but over 10 calcs stacking on each other it gets huge.
We don't do calc stacking because it applies a large multiplier on characters' stats for every single decent feat they perform, gradually getting further and further away from anything actually shown in the text. Even if you think those calcs multiplying on each other is justified in the text, it amplifies errors in our calcs. If pixel-scaling in our calcs is off by 10% that doesn't really matter in one calc, but over 10 calcs stacking on each other it gets huge.
