• 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 Piece Blue Planet Calc Revisions

Status
Not open for further replies.
A bit unrelated to the topic, but i think Enel's feat itself would need to be recalc with another method anyway.

As it was pointed out by a user called GHOSTPEPPER.282 that what we see may be the dust dispersed by the blast and its not the actual explosion.

So probably need to remade it by using the same formula used in feats like this.
 
A bit unrelated to the topic, but i think Enel's feat itself would need to be recalc with another method anyway.

As it was pointed out by a user called GHOSTPEPPER.282 that what we see may be the dust dispersed by the blast and its not the actual explosion.

So probably need to remade it by using the same formula used in feats like this.
Moon Diameter: 194,019.8418356023 km

Moon Explosion Diameter: 192,831 km

Moon Explosion Radius: 96,415.5 km

Hemisphere Volume Calculator

Volume: 2.34643863057848297826295e+23 m^3

"When it comes to sandstorms, we use 38% hollowness stacked with a 90% hollowness for 0.062x true volume. I will use the same for the dust kick up"

Corrected Volume: 2.34643863057848297826295e+23 * .062 = 1.4547919509586593e+22 m3

Moon Dust Density: 1500 kg/m3

(1.4547919509586593e+22) * (1500) = 2.182187926437989e+25

Mass: 2.182187926437989e+25 kg

“(KE= (1/12) * m * v^2)”

600s
Velocity: 96415500/600 = 160,692.5 m/s
KE: (1/12) * 2.182187926437989e+25 * 160,692.5^2 = 4.6957191869308315e+34 Joules = 11.223 Yottatons of TNT

Rough calc I put together real quick using a massive lowball time of 10 mins.
 
Bump. Someone needs to evaluate Floxy's moon calc.

Although @KingTempest should probably edit the planet calc to account for the minor mistake first as it affects the result of Floxy's moon as well.
 
Bump. Someone needs to evaluate Floxy's moon calc.

Although @KingTempest should probably edit the planet calc to account for the minor mistake first as it affects the result of Floxy's moon as well.
Man got a way to message me on every platform possible and he chooses to do so in the public thread, now just put me on the spot
 
Are you sure you didn't mess up with numbers in the end? Where did 245px and 367 px come from?

You should measure corrected diameter, then divide it by sqrt(1-(tan(35) * (345/526))^2/((tan(35) * (345/526))^2+1)) or 0.90874504509 to find true diameter.
(Shhhhh I can't do math) Fixed
 
Grand Line width:
174100.85714286 km | 38.6 px

Visible/corrected Planet diameter:
345 px | 1556082.79053 km

True diameter:
1556082.79053 / [sqrt(1-(tan(35) * (345/526))^2/((tan(35) * (345/526))^2+1))] = 1712342.53097 km

I think Planet Curvature part should be like this
 
Grand Line width:
174100.85714286 km | 38.6 px

Visible/corrected Planet diameter:
345 px | 1556082.79053 km

True diameter:
1556082.79053 / [sqrt(1-(tan(35) * (345/526))^2/((tan(35) * (345/526))^2+1))] = 1712342.53097 km

I think Planet Curvature part should be like this
Did that
sqrt(1-(tan(35) * (345/526))^2/((tan(35) * (345/526))^2+1)) * 1655311.2583272 = 1580737.14 km


x = 1580737.14 / [sqrt(1-(tan(35) * (526/345))^2/((tan(35) * (526/345))^2+1))]


x = True Planet Diameter = 1950052.88 km
 
sqrt(1-(tan(35) * (345/526))^2/((tan(35) * (345/526))^2+1)) * 1655311.2583272 = 1580737.14 km
You're already measuring visible/corrected diameter, there's no reason to apply PCS on top of that. Just do the reverse after direct pixelscaling.
x = 1580737.14 / [sqrt(1-(tan(35) * (526/345))^2/((tan(35) * (526/345))^2+1))]
Why 526/345? They shouldn't be switched.
 
You're already measuring visible/corrected diameter, there's no reason to apply PCS on top of that. Just do the reverse after direct pixelscaling.

Why 526/345? They shouldn't be switched.

(I hate planet diameter so damn much)
So. just do the bottom half but do 345/526?

Also, where'd u get 1556082.79053 from?
 
This is a tangential point I want to bring up, but whatever value is decided for the planet, should there maybe be some kind of discussion rule in place to prevent the calcs and verse stats from being nuked again and again? I feel like a major part of the verse being in disarray is because nothing is allowed to sit for even a few months
 
This is a tangential point I want to bring up, but whatever value is decided for the planet, should there maybe be some kind of discussion rule in place to prevent the calcs and verse stats from being nuked again and again? I feel like a major part of the verse being in disarray is because nothing is allowed to sit for even a few months
It's counterintuitive to try and forbid a calc from being corrected or removed with a rule. We could be locking ourselves into a flawed foundation for the verse.
 
This is a tangential point I want to bring up, but whatever value is decided for the planet, should there maybe be some kind of discussion rule in place to prevent the calcs and verse stats from being nuked again and again? I feel like a major part of the verse being in disarray is because nothing is allowed to sit for even a few months
Yes.
It's counterintuitive to try and forbid a calc from being corrected or removed with a rule. We could be locking ourselves into a flawed foundation for the verse.
A discussion rule being put in place to stop knocking the One Piece planet size based on certain arguments is logical. Planet can be up or downgraded, that isn't a problem, but some of these arguments should never be seen again

Although, let's wait for Billybobjoe321's response and see if the thread actually passes or not before stuff like that is valid
 
i hate math

aight, done
Evaluated.
This is a tangential point I want to bring up, but whatever value is decided for the planet, should there maybe be some kind of discussion rule in place to prevent the calcs and verse stats from being nuked again and again? I feel like a major part of the verse being in disarray is because nothing is allowed to sit for even a few months
I don't think that's a good idea.
 
It's counterintuitive to try and forbid a calc from being corrected or removed with a rule. We could be locking ourselves into a flawed foundation for the verse.
I don't think that's a good idea.
I probably could have worded it better, but I don't mean "No more calcs for the verse" but rather having a discussion rule for specifically the planet size so that the stats/calcs for the verse isn't in a constant state of flux due to so much of the scaling being dependent on it
 
I probably could have worded it better, but I don't mean "No more calcs for the verse" but rather having a discussion rule for specifically the planet size so that the stats/calcs for the verse isn't in a constant state of flux due to so much of the scaling being dependent on it
Or make sure the verse is consistent with its scaling in the logic of the story.

For example, One Piece's best non-planet calc is 6-B, which is only in Dressrosa and is missing FIVE arcs of the series and missing 300+ chapters of new scaling.

After this thread is done, we need an evaluation on all the new scaling from High 6-A to 5-A, the size of Wano and Elbath, because honestly, this verse has a lot of work to do (in terms of power, speed should be fine), especially since it is almost the 'end' of the story.
 
Thanks. I remade KT's moon excavation calc with your moon size value so we can have something to replace it

Like i already say before, i do think that what we see may not be the actual explosion but rather the dust dispersed by the blast. Which does match with what we see as the color of the explosion does resemble a large cloud dust rather than a fireball, so i think we should at least consider making an alternative calc based on that assumption.

Credits to EtherealCrater for the formula

Moon Explosion Diameter: 212,382.7653909 km

Moon Explosion Radius: 106,191.383 km

Volume: 2.507993718658611617509807e+24 m^3

Corrected Volume: 2.507993718658611617509807e+24*0.062 = 1.55495611e23 m^3

Moon Dust Density: 1,500 kg/m^3

Mass: 1.55495611e23*1,500 = 2.33243416e26 kg

Height Explosion

Moon: 100 pixels (Red Line)

Explosion: 31 (Green Line) = 212,382.7653909*(31/100) = 65,838.6573 km

GPE: 2.33243416e26*1.62*65,838.6573 = 2.4877422e31 Joules or 5,951.339 Zettatons (Small Planet level)
 
Yeah, taking it as shockwave radius makes no sense. However GPE method won't work like that either because only small, negligible part of dust is that far from the Moon (also you'd need find GPE difference when g isn't more or less same for low height calcs). Why don't we use omnidirectional KE?
 
Last edited:
Status
Not open for further replies.
Back
Top