• 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.

One-Punch Man: New (and old) Calcs

Status
Not open for further replies.
Messages
23,603
Reaction score
21,360
So there are a bunch of older calcs I made that were evaluated and accepted by CGMs, but I just never got around to making CRTs for them. I also made a few newer calcs, like the speed of Atomic Samurai's Beeline Atomic Slash, so I figured I'd include everything in one thread

7686335.48 m/s / 0.0256388554c (Sub-Rel)

1.89723427e15 Joules / 453.449873 Kilotons of TNT (High 7-C)

641666762 m/s / 2.14036993c (FTL)

205714496 Newtons / 20977.0407 Metric Tons (Class M)

22672856.6 m/s / 0.075628509c (Sub-Rel)

77054.3698 m/s / Mach 224.6483084548 (Massively Hypersonic)

337544.525 m/s / Mach 984.094825 (Massively Hypersonic)

Pretty much what this changes:
  • Characters that were 16.06 Kilotons of TNT (with the exception of BOS Genos and Mosquito Girl) are now 453.45 Kilotons of TNT due to scaling to House of Evolution Genos
  • Characters that were 32.12 Kilotons of TNT are now upscaled to 1 Megaton of TNT due to powerscaling
  • Characters that were 64.24 Kilotons of TNT are now 2 Megatons of TNT due to powerscaling
  • Pureblood and Zombieman get Class M Lifting Strength (20977 Metric Tons) due to Pureblood's feat
  • Tatsumaki is now 2.14036993c
  • Characters that were Mach 8.2748 and Mach 42.3 are now Mach 224.65 due to scaling to Pre-Training Sonic
  • Characters that were Mach 820.11 are now Mach 984.1 due to scaling to Nyan
  • Characters that were Mach 3550 are now 0.075628509c due to scaling to Atomic Samurai
 
Last edited:
The justification in the blog was also Saitama so it should work as a full rating.
The reasoning for Saitama's speed in the same blog still comes directly from the Geryuganshoop statement that's rated as only possibly
All of it hinges off the sub-light statement
 
Yeah that Tatsumaki feat does NOT work. Out of all calcs that did not work this does not work the most.

First of all Saitama doesn't throw the rock. He deflects a rock thrown by Tatsumaki. So the whole "he threw the rock" thing just isn't true.

Second of all, Saitama considering near light speed rock throws to be nothing to himself doesn't mean every single rock he interacts with will be launched at higher speeds. ESPECIALLY in the case of Saitama who's constantly holding back and tries to use as little power as possible and ESPECIALLY when he's not even actually throwing any rocks.

Lastly, the very statement you're using to calculate Tatsumaki to FTL states she CAN'T move objects at even rel+ speeds. You're using a sub-light cap to get her to FTL. That's the most absurd glaze I've ever seen.


I'm actually flabbergasted you even tried to suggest it and I'm flabbergasted² that neither KT nor Floxy picked up on this when approving it.
 
the Tornado one seems invalid. It contradicts the WoG itself (they say Tornado just can't throw things that fast)
Like I said, there's a difference between tossing something and actively controlling it with KE. It's the difference between throwing a baseball vs holding that baseball and running around. When Tatsumaki does the latter, her psychic aura grants the object a heat resistance, just like it does when it surrounds herself. It's not a contradiction of WoG to say that she can move a car coated with her aura that fast.
 
Like I said, there's a difference between tossing something and actively controlling it with KE. It's the difference between throwing a baseball vs holding that baseball and running around. When Tatsumaki does the latter, her psychic aura grants the object a heat resistance, just like it does when it surrounds herself. It's not a contradiction of WoG to say that she can move a car coated with her aura that fast.
This is just very dishonest semantics. The author statement explicitly says

"But his ability to control flying objects should be above Tatsumaki, because he can eliminate the friction between rocks and air."

"Tatsumaki can throw very large objects, but there's a limit to how fast she can throw them. Geryuganshoop is the greatest psychic in the universe after all. That's what I think. (he repeats this several times)"

The statement is very blatantly meant to refer to their general ability to control objects, not just the speed at which they move when released from her aura. There has never even been aj established difference between controlling and throwing like you're suggesting, and Tatsumaki basically never actually releases her objects from her control while using them in general. Meaning this difference that makes Geryuganshoop the superior psychic wouldn't actually matter.

So it absolutely is a contradiction as saying this would mean Tatsumaki has the superior control over flying objects to Geryuganshoop, and playing semantic games around it is just dishonest.
 
Tatsu’s calc doesn’t work narratively FRA + the calc is assuming Saitama went from basically standing still to reach the assumed speed in an instant, which just completely ignores how acceleration works.

There’s also the fact that the rock itself wasn’t burning when it should’ve because it and Saitama reached the same location at the same time, meaning it was also going at his speed. So neither Saitama nor the rock was going at sub-light speed anyway and I don’t get how everyone missed that part.
 
I also disagree with the Atomic Slash calc because it’s blatant calc stacking
I don’t think it's calc stacking but now that I look at it, it is wrong too.

Firstly I'd like to see where the 340 m/s "minimum" for the sword slash came from.

Secondly and more importantly, the statement Kachon uses says "100 slices per second". And Kachon is trying to apply the 100 number to a completely different, much smaller timeframe of 0.00002938 seconds.

Just because the databook says he can throw over 100 slashes per second doesn't mean he can throw 100 slashes in 29 microseconds. Especially when the number of visibly slashes is less than half of that. Again this application of the statement almost seems to contradict the statement itself
 
Firstly I'd like to see where the 340 m/s "minimum" for the sword slash came from.
What do you mean?
Secondly and more importantly, the statement Kachon uses says "100 slices per second". And Kachon is trying to apply the 100 number to a completely different, much smaller timeframe of 0.00002938 seconds.

Just because the databook says he can throw over 100 slashes per second doesn't mean he can throw 100 slashes in 29 microseconds. Especially when the number of visibly slashes is less than half of that. Again this application of the statement almost seems to contradict the statement itself
That end isn't even accepted or in the OP so I don't know why you're pointing it out.
 
What do you mean?
That's what the original calculation uses to get the timeframe. The distance between AS and the monster divided by the speed of the attack.
And the attack speed of the monster is marked at "at least 340 m/s".

Anyway I found it in the comments of the OG calc. You should paste it in your calc too for readability.
That end isn't even accepted or in the OP so I don't know why you're pointing it out.
Touché. Missed that the low end is not accepted. Still funny af to even imply "100 slices per second" actually meant "over 3 million slices per second"

Also now that I'm rereading the OG calc, it literally existed because assuming 180° per swim was deemed wrong.

So why are you un-fixing the calc? What's the justification for 180° per swing compared to when the 180° assumption was rejected? When replacing an existing calculation you have to provide reasoning why the new one is better than the previous one, and here you're kinda doing the exact opposite.
 
Also now that I'm rereading the OG calc, it literally existed because assuming 180° per swim was deemed wrong.

So why are you un-fixing the calc? What's the justification for 180° per swing compared to when the 180° assumption was rejected? When replacing an existing calculation you have to provide reasoning why the new one is better than the previous one, and here you're kinda doing the exact opposite.
Ugarik's calc is from 2019 which came out before we got direct proof of the Atomic Slash having 180° swings. The CGM that accepted the calc was made aware of this and accepted the calc.
 
Ugarik's calc is from 2019 which came out before we got direct proof of the Atomic Slash having 180° swings. The CGM that accepted the calc was made aware of this and accepted the calc.
Can you put evidence that every slash in the attack being 180° in the calc? Ideally also explain the change in the OP.

These are things that should have been both in the calc and the OP, its the standard for calculation replacement
 
It literally is in the calc. Read it.
Can you highlight where? I've read both the calcs like 3 times and there's no mention of this. Idk if I'm blind but but I don't see it.

The closest thing to a justification I see is a link that leads to 2 random panels of AS slicing his sword. Hell one of the 2 panels is not even a standard "atomic slash" but an "atomic straight slash" so I don't think that's what you mean as the justification…?
That's also in the blog
Seriously, all the questions you're asking are already in the calc @DavidTPPM
The panel being there is not the same as the justification being there.

Especially with imgur where links constantly break. In a years time the link breaks and now there's absolutely nothing.
The monster says something like "Even before monsterization I could swing my sword at the speed of sound" which is why the value was chosen.
Yeah like I said, I noticed it mentioned in the past calc as the reasoning. Either way this isn't really an error in the calc, I just think it'd be better to verbally mention that's the timeframe justification.

It's kinda silly to have to go through multiple different recalcs to find the justification in the comments of the 3rd one from over half a decade ago.
 
I'm actually flabbergasted you even tried to suggest it and I'm flabbergasted² that neither KT nor Floxy picked up on this when approving it.
I'm not a cgm. I'm not obligated to look at calcs which is a problem on the evaluating side instead of me. My only job is evaluating threads. Only rarely do I look at the actual calcs and that's if/when I have time. That's why I said "if the calcs are fine, those are fine"
 
Well I expected you to 🫵 😡
I just didn't want to single Floxy out
Single floxy out

If there's a problem with the calcs they need to be rectified before my agreeal is solid, so work out the calcs then my agreeal will be fine (don't need to re-summon me to re-evaluate unless you need calc expertise)
 
I disagree with Tatsumaki's calc based on using Geryuganshoops statement when the statement itself includes comparison to Tatsumaki.

Maybe making the calc using Saitama's speed could work as Saitama(during training) has his own possibly rel+ mirror feat along with the statement, but it'd require to prove if Saitama would go that fast to save the family.

I'm hesitant about the new 3x monsterization change in atomic slash calc as there isn't any 1:1 statement for speed&strength growth. It doesn't suit with our current multiplier rules. So i disagree with that aa long as there won't be a part that explains why it should include speed.

I agree with the other ones.
 
Status
Not open for further replies.
Back
Top