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

WAHOOOO! Mario Bros AP Revisions (M&L Brothership Spoilers) - Part 1 (Feat-Gathering)

There already is a recalc, but it seems to be HEAVILY lowballed as it only considers the volume of the hole itself without considering the fact that the entirety of the storm was likely moving
The clouds do extend past that yeah, we see them moving still when we see cap. And by the end, the horizon is cleared. We could do omnidirectional to horizon KE with that timeframe. Or if we have a bigger size like via the map, we can do that instead.
 
I just noticed a pretty big problem with the Dark Bowser calc, it used 1/4 mass for omnidirectional KE when it should’ve used 1/12 mass

(1/12) * 1,392,214,139,175,340,000 * 632497.112^2 = 4.641324e+28 Joules or 11.093031 Exatons of TNT (Multi-Continent level)

So, yeah… no tier 5 yet I guess
 
Last edited:
I just noticed a pretty big problem with the Dark Bowser calc, it used 1/4 mass for omnidirectional KE when it should’ve used 1/12 mass

(1/12) * 1,392,214,139,175,340,000 * 632497.112^2 = 4.641324e+28 Joules or 11.093031 Exatons of TNT (Multi-Continent level)

So, yeah… no tier 5 yet I guess
In the case of such an omnidirectional expansion one could use the formula "kinetic energy = 0.25 * cloud mass * (Speed of cloud movement)2" to account for the different speeds involved.
 
Idk if the Wario cloud feat is gonna get that high. The thickness is like, 1000000x lower than the old calc, so even if we extend the radius based off the map, it might get like, idk, 6-C? Like it's a feat, and 100% should be recalced given he just kinda facetanks it so it's at least a solid bit feat, but if the goal is "shit within the peta to exa" range, this ain't it.
 
Idk if the Wario cloud feat is gonna get that high. The thickness is like, 1000000x lower than the old calc, so even if we extend the radius based off the map, it might get like, idk, 6-C? Like it's a feat, and 100% should be recalced given he just kinda facetanks it so it's at least a solid bit feat, but if the goal is "shit within the peta to exa" range, this ain't it.
Getting closer at least, somewhat.
 
Idk if the Wario cloud feat is gonna get that high. The thickness is like, 1000000x lower than the old calc, so even if we extend the radius based off the map, it might get like, idk, 6-C? Like it's a feat, and 100% should be recalced given he just kinda facetanks it so it's at least a solid bit feat, but if the goal is "shit within the peta to exa" range, this ain't it.
Actually, I take issue with the recalc’s cloud thickness.

The way Migue measured it was based on the beam of light, but if that were the case, Shake King’s castle (which is bigger than the beam) would have to be visible. But, if you look at the shot that was used to measure the clouds, the castle is completely invisible.

Also, it fails to take into account the fact that light sources produce a lot of exposure (I think that’s the term, at least; idk I’m not a photographer), resulting in the actual size of the thing being obscured, especially at far distances.

Finally, looking at the cloud calculations page, 130 meters is very small for most clouds. The only two that would actually work for that thickness is stratocumulus and cirrus, both looking nothing like the storm in this case. If anything, the storm looks most like a Nimbostratus, something the calc itself agrees with in regards to density.

As such, I think it would be better to use Nimbostratus thickness (3 km) instead. And if anyone is curious, doing some quick angsizing, (3 * 729/[195*2*tan(70deg/2)] = 8.0086 km), it doesn’t actually conflict with the 20 km horizon line, so this should be completely fine.

EDIT: This would also dramatically increase the speed of the storm when dispursing, so, while maybe not a full-on High 6-A feat, it would be a pretty damn decent supporting feat.
 
Last edited:
Oh, actually there's another Wario-based feat I remembered recently. Wario Land 1's best ending, the genie (which Wario beat the crap out of a few minutes prior) creates a separate-from-Earth planetoid with Wario's face visibly carved into it.

Since it's meant to be a "castle" and that was literally what Wario wished for, I'd think it has to be a large enough planetoid to maintain a breathable atmosphere, likely a Tier 5 feat. Even if he just terraformed an existing planetoid that just happened to already exist not too far from Earth, that'd probably still be Tier 6.
 
Oh, actually there's another Wario-based feat I remembered recently. Wario Land 1's best ending, the genie (which Wario beat the crap out of a few minutes prior) creates a separate-from-Earth planetoid with Wario's face visibly carved into it.

Since it's meant to be a "castle" and that was literally what Wario wished for, I'd think it has to be a large enough planetoid to maintain a breathable atmosphere, likely a Tier 5 feat. Even if he just terraformed an existing planetoid that just happened to already exist not too far from Earth, that'd probably still be Tier 6.
That looks relative to Wario's size. He even stands on top of it as if it was a boulder, are you sure that's an actual planetoid?
 
That looks relative to Wario's size. He even stands on top of it as if it was a boulder, are you sure that's an actual planetoid?
Seems to be. The next result down is a castle, and then a pagoda, and both are far back enough to fit entirely on the Gameboy screen. The castle is the canon ending, since Wario has that same castle in Wario Land 2, and in that game it's a full "World 1" in a 5-World game.

I'm willing to chalk up the "stands on top of it" bit to cartoon physics. He walks through/in front of the planet repeatedly during the credits, so it's clearly not on the same 2D axis as Wario.
 
Actually, I take issue with the recalc’s cloud thickness.

The way Migue measured it was based on the beam of light, but if that were the case, Shake King’s castle (which is bigger than the beam) would have to be visible. But, if you look at the shot that was used to measure the clouds, the castle is completely invisible.

Also, it fails to take into account the fact that light sources produce a lot of exposure (I think that’s the term, at least; idk I’m not a photographer), resulting in the actual size of the thing being obscured, especially at far distances.

Finally, looking at the cloud calculations page, 130 meters is very small for most clouds. The only two that would actually work for that thickness is stratocumulus and cirrus, both looking nothing like the storm in this case. If anything, the storm looks most like a Nimbostratus, something the calc itself agrees with in regards to density.

As such, I think it would be better to use Nimbostratus thickness (3 km) instead. And if anyone is curious, doing some quick angsizing, (3 * 729/[195*2*tan(70deg/2)] = 8.0086 km), it doesn’t actually conflict with the 20 km horizon line, so this should be completely fine.

EDIT: This would also dramatically increase the speed of the storm when dispursing, so, while maybe not a full-on High 6-A feat, it would be a pretty damn decent supporting feat.
Ok, so I may have made a bit of a mistake in my math regarding the horizon

Apparently, Migue's image was actually scaled down from its original size, as when I did my own measurements, the height of the clouds was 199 px, and the screen height was 2160. This resulted in a distance of 23.252 km.

But I still think that the cloud height would be reasonable mathematically. If you look at the shot again, you'll realize the "camera" is on top of a hill rather than on sea level. And looking at some online formulas, you'd only really need to be 40 m above sea level for the center of the cloud to be below the horizon line.

Besides, just 3 km more than the average horizon distance is a way more reasonable amount of artistic liberty than the shit-trillion the original calc got, so I'd say it should still be fine, but I'd be willing to see if anyone disagrees.
 
For timeframe, wouldn't it be like 25 seconds?


Here is the final shot, we see the horizon very clearly and it's completely gone, and this is the shot of the island the lil ***** were on too.

You don't need to do a minute, we know for a fact it's at most like 25 seconds~.
 
Just do 25 seconds or whatever. The intent is pretty blatant that shit's gone by the end of that cutscene, which is only like 10 extra seconds while also being not an omega inflated like 1 second but also not an arbitrary 1m lowend. Still tier 6.
 
For timeframe, wouldn't it be like 25 seconds?


Here is the final shot, we see the horizon very clearly and it's completely gone, and this is the shot of the island the lil ***** were on too.

You don't need to do a minute, we know for a fact it's at most like 25 seconds~.

@Mr. Bambu this should be fine no? Just getting rid of the other ends entirely and just doing the full dispersal for 25 seconds since thats how it seems to take

@IDK3465 just make the fix from what Chariot said
 
Last edited:
Just do 25 seconds or whatever. The intent is pretty blatant that shit's gone by the end of that cutscene, which is only like 10 extra seconds while also being not an omega inflated like 1 second but also not an arbitrary 1m lowend. Still tier 6.
@Mr. Bambu this should be fine no? Just getting rid of the other ends entirely and just doing the full dispersal for 25 seconds since thats how it seems to take

@IDK3465 just make the fix from what Chariot said
The main problem is that we don’t really know for sure if the storm’s completely gone by then. For all we know it could still be dispersing past the horizon and we just don’t get to see it. While I personally do agree that it likely is fully away by then, I wasn’t too sure if Bambu might agree with that, hence why I made the minute assumption for the high end.

I’ll personally wait to see what Bambu thinks and handle it from there
 
A minute wouldn't work by that logic, at that point you'd just have to find the speed and figure out the timeframe based on that, based on the total radius. It ain't gonna be 1 minute. Gonna be way longer if that's the argument.
And then you gotta figure out, what speed, it isn't consistent at all between parts of the scene, you'd need to cherry pick which isn't good.

Regardless that's just jumping through hoops, the final part of the scene is obviously supposed to be going "yeah shit's gone now yay!" while showing a zoomed out horizon from pretty damn high in the sky (would make to horizon line like 50-60km at least), like there's trying to prevent inflation and there's just lowballing for the sake of it.
 
A minute wouldn't work by that logic, at that point you'd just have to find the speed and figure out the timeframe based on that, based on the total radius. It ain't gonna be 1 minute. Gonna be way longer if that's the argument.
And then you gotta figure out, what speed, it isn't consistent at all between parts of the scene, you'd need to cherry pick which isn't good.

Regardless that's just jumping through hoops, the final part of the scene is obviously supposed to be going "yeah shit's gone now yay!" while showing a zoomed out horizon from pretty damn high in the sky (would make to horizon line like 50-60km at least), like there's trying to prevent inflation and there's just lowballing for the sake of it.
Yes, and I already get that. I already agreed with Bambu on the minute-long timeframe being too arbitrary within the comments on the calc. I just wanted to get the go-ahead from him to make sure it was fine.

But, just to be sure, are you saying a 25 second timeframe for the storm to go past the horizon, or to fully dissipate? (as in, the full radius of the storm)
 
Yes, and I already get that. I already agreed with Bambu on the minute-long timeframe being too arbitrary within the comments on the calc. I just wanted to get the go-ahead from him to make sure it was fine.

But, just to be sure, are you saying a 25 second timeframe for the storm to go past the horizon, or to fully dissipate? (as in, the full radius of the storm)
Full thing, that's obviously what the scene is trying to convey. It's the "clouds go away" scene, and it shows it start to vanish, continue to vanish, and ends with a completely clear horizon. Like shit is obvious what it's trying to say.

As an fyi, you need to actually get the exact timeframe, it isn't exactly 25 seconds, it's just "about that", make sure you get the full timeframe.
 
Full thing, that's obviously what the scene is trying to convey. It's the "clouds go away" scene, and it shows it start to vanish, continue to vanish, and ends with a completely clear horizon. Like shit is obvious what it's trying to say.

As an fyi, you need to actually get the exact timeframe, it isn't exactly 25 seconds, it's just "about that", make sure you get the full timeframe.
Yeah, disagree. The scene is obviously "the evil is gone" or whatever, but it doesn't fundamentally mean it's gone everywhere- it will be, soon, obviously, but you're dealing in hazy interpretations rather than objective fact. We're talking about timeframes that multiply the end result by like. Thousands of times.

If the calc was just about the horizon, I'd agree with it. But using that approximate timeframe to justify continentally sized areas seems insane, especially when as you said, we can determine how long it would take, based on how fast it was going from the beginning bit we see. I don't see the logic of what you're suggesting.
 
Yeah, disagree. The scene is obviously "the evil is gone" or whatever, but it doesn't fundamentally mean it's gone everywhere- it will be, soon, obviously, but you're dealing in hazy interpretations rather than objective fact. We're talking about timeframes that multiply the end result by like. Thousands of times.
Big number bad, cool, I get it, we don't wanna be to generous as that can lead to wank, inflation, whatever.
But let's not pretend it's secretly still expanding offscreen though. It isn't.
There comes a point when you need to stop inflation, like that one second timeframe? Yep bad, wank even.
And then there's a point we're you just ignore the very blatant obvious intent of a cutscene for the **** of it. (Fyi when I say "you" I'm talking generally, don't treat this shit as some sort of attack 🗿 ).

The cutscene is literally showing it "gone" everywhere, why do you think we get a big zoom out at the end? Lingering on for several seconds? Clear blue skies? In a cutscene showing dedicated to showing the clouds parting? Do you really think the intent behind that is to show it was simply vanishing, and not already vanished?
If the calc was just about the horizon, I'd agree with it. But using that approximate timeframe to justify continentally sized areas seems insane, especially when as you said, we can determine how long it would take, based on how fast it was going from the beginning bit we see. I don't see the logic of what you're suggesting.
Yeah and I also said that'd be hyper inconsistent given it changes between instances of the scene, you'd have to arbitrarily pick one, it starts off fast, goes slower, and then is super ultra fast again (literally cleared like 60km within a few seconds, when before it took a few seconds to do a few hundred). So which one should we pick? If we pick the most recent one, we don't actually know how fast it'd be because it cleared the whole horizon in a instant. If most recent it'd be over 30000ms fyi (horizon line from hundreds of meters up in about 2 seconds).

But, to give an example. Let's assume the lowend speed for argument's sake. That would mean it took 19.04 minutes for the storm to clear completely, yet in the immediate next cutscene they're yapping about how shit's back to normal and he saved them and they he takes the funny bag and dips tf out.
It evidently didn't take that long. Why would the game actively show the the storm very visibly gone in a wideshot, and then 1 second later yap about how shit's normal again, everywhere for the whole dimension? Mind you there wasn't a timeskip, the funny bag and chick were right were Wario was in the final boss arena, he didn't leave or need to go anywhere. Even if, you assume only up to the very moment she says that, we'd be looking a timeframe of idk 35 seconds?

So, what's actually the argument? We have a very blatant case of it being visibly completely gone in a scene dedicated to showing it vanishing, followed by a statement seconds later that the whole dimension is cool again. If the intent isn't obvious, idk what is. But in that case, what, exactly, would you have be done? Because Shit sure ain't taking 20 minutes.
 
Last edited:
Big number bad, cool, I get it, we don't wanna be to generous as that can lead to wank, inflation, whatever.
But let's not pretend it's secretly still expanding offscreen though. It isn't.
There comes a point when you need to stop inflation, like that one second timeframe? Yep bad, wank even.
And then there's a point we're you just ignore the very blatant obvious intent of a cutscene for the **** of it. (Fyi when I say "you" I'm talking generally, don't treat this shit as some sort of attack 🗿 ).

The cutscene is literally showing it "gone" everywhere, why do you think we get a big zoom out at the end? Lingering on for several seconds? Clear blue skies? In a cutscene showing dedicated to showing the clouds parting? Do you really think the intent behind that is to show it was simply vanishing, and not already vanished?
By "expanding", you mean the cloud? I didn't imply that.

There's also a point where you need to have object permanence, in that when a thing is not visibly offscreen, you can't forget that it can exist, offscreen. I'm not positing a position that says "Actually this only dispersed the cloud in the immediate area". Obviously the spirit of the thing is that it is being dispersed entirely. I contend the arbitrary timeframe used on it, though, because we can see how long it takes to disperse just that original area. We have no reason to make assumptions outside of that regarding its speed offscreen. Just use the displayed speed lol.

For the record. And I feel this is very important.

The Calc is calculating a cloud being gone over continents. A very very large area. I recognize it is hard to imagine that. And this is the shot I'm meant to take as the dispersal being concluded over continental landmasses? Because the process has finished over this one, very small, island? That doesn't make any sense.

Yeah and I also said that'd be hyper inconsistent given it changes between instances of the scene, you'd have to arbitrarily pick one, it starts off fast, goes slower, and then is super ultra fast again (literally cleared like 60km within a few seconds, when before it took a few seconds to do a few hundred). So which one should we pick? If we pick the most recent one, we don't actually know how fast it'd be because it cleared the whole horizon in a instant. If most recent it'd be over 30000ms fyi (horizon line from hundreds of meters up in about 2 seconds).
That's how physics works. That isn't arbitrary. Wind resistance, gravity of the earth, etc- objects (even gases) tend to slow down, not speed up. We have a basis by which we can make our judgements. The current one is arbitrary in that it does not align with that basis. There's also the notion of cinematic time to crease over some of these bumps you're mentioning, a notion one feels we don't evoke as the creators of our given media.

I stand by just using the speed derived from the initial clearing period and then recognizing the actual value would be lower, but marking it any lower is arbitrary.

But, to give an example. Let's assume the lowend speed for argument's sake. That would mean it took 19.04 minutes for the storm to clear completely, yet in the immediate next cutscene they're yapping about how shit's back to normal and he saved them and they he takes the funny bag and dips tf out.
It evidently didn't take that long. Why would the game actively show the the storm very visibly gone in a wideshot, and then 1 second later yap about how shit's normal again, everywhere for the whole dimension? Mind you there wasn't a timeskip, the funny bag and chick were right were Wario was in the final boss arena, he didn't leave or need to go anywhere. Even if, you assume only up to the very moment she says that, we'd be looking a timeframe of idk 35 seconds?

So, what's actually the argument? We have a very blatant case of it being visibly completely gone in a scene dedicated to showing it vanishing, followed by a statement seconds later that the whole dimension is cool again. If the intent isn't obvious, idk what is. But in that case, what, exactly, would you have be done? Because Shit sure ain't taking 20 minutes.
Cinematic timing, again. No video game is going to make you sit through everything that happens in real time. It'd be like... you're playing a game, you get on an airplane, then suddenly you're on the other side of the world. It makes no sense to presume, then, that the airplane is actually Massively Hypersonic. There's just time passing in greater quantities than what is shown. Furthermore, they are allowed to say things are back to normal, even if it is implied it's actually getting back to normal in the near, immediate future. 20 minutes is an insanely short time! It's basically no time at all. This statement has no bearing on the displayed speed, the speed we can physically see, of the clouds.

The actual argument is that you're wrong, plainly and simply. It's taking 20 minutes. Or more, really, but I admit it's arbitrary to go lower, even though it would not be arbitrary to recognize that the value is certainly even lower.
 
By "expanding", you mean the cloud? I didn't imply that.
Literally did but sure. What else would you mean by "the cloud is still dispersing offscreen"?
There's also a point where you need to have object permanence, in that when a thing is not visibly offscreen, you can't forget that it can exist, offscreen.
Yep, unfortunately that isn't an argument Bambu.
They say it's back to normal, they also actively try to convey as such with visuals. We know the finaltimeframe more or less, the only way this would work if there's a substantial timeskip, but we get to that later.

"Can" exist, and "does" exist, are not the same. We have no reason to assume it exists offscreen beyond using faulty logic, inconsistent onscreen visuals, and a whole other bunch of slop that gets immediately shot down.

This, would work, if it was consistent, in fact I even argued something similar for the Dark Star feat where we didn't have much of an established window and speeds only went one way, not all over. That isn't the case here though.
I'm not positing a position that says "Actually this only dispersed the cloud in the immediate area". Obviously the spirit of the thing is that it is being dispersed entirely. I contend the arbitrary timeframe used on it, though, because we can see how long it takes to disperse just that original area. We have no reason to make assumptions outside of that regarding its speed offscreen.
Doesn't matter if that isn't what you're positing if that's the end result.

Your contention with the timeframe is, quite frankly, ridiculous.
The original area clear has 3 to 4 seperate speeds, it isn't consistent within itself. The original area doesn't matter, when we're told the whole dimension is fine now.
Just use the displayed speed lol.
Varies exponentially. Inconsistent.

You want the displayed speed, we'd be using like 1800kms because that's the final displayed speed taken at face value. You see the issue yes? If we go with your premise, it only bloats it.
For the record. And I feel this is very important.

The Calc is calculating a cloud being gone over continents. A very very large area. I recognize it is hard to imagine that.
Stop the condescending remarks, that is beyond irrelevant, it could be smaller, bigger, how big it is doesn't matter, what matters is the timeframe for which it disperses.
And this is the shot I'm meant to take as the dispersal being concluded over continental landmasses? Because the process has finished over this one, very small, island? That doesn't make any sense.
Yes. Especially because they say as much five seconds later.

This is an argument from incredulity. Who gives a shit how big it is? Fact is, it's evidently supposed to be gone by then. They show us it parting, they show us completely clear skies, it is followed by a statement saying the whole dimension has been brought to peace, whole confirming it isn't just that area atm. It is worded present tense, not future tense, so it going back to normal, isn't an argument, that is objectively not what is said.

Despite your claims, there is no relevant timejump, that room is on the very island Wario fought the final boss on, they even drop into it. We know he's still on the island because that's where the beam originates from in the cutscene, and we know Wario has a straight shot to that room and would take him literally not even 10 seconds to get back there, which he would, because his ass straight up doesn't care about being there and wants his money pronto.

Whether or not it makes sense doesn't matter, it just is. Like that's what happened. What do you want me to say? That's the intent behind the scene, that's also what they say, so it took that amount of time.
That's how physics works. That isn't arbitrary. Wind resistance, gravity of the earth, etc- objects (even gases) tend to slow down, not speed up.
Wild then that it literally sped up then no? (These clips, idk why they ain't loading as such, click them idk).


Look, it's a mere, idk 100-200ms a second in this instance. Absolute crawl, would take hours.

Yet suddenly


Gets quicker and we can visibly see it move at a far quicker speed from below as it passes by them (Completely ignoring it randomly got to the island, even though at the speed it was 5 seconds ago, it'd have taken like tens of minutes or something, which needless to say, they weren't jumping up and down looking at the sky in the same position for that long).

Only to then instantly clear the horizon even a second after that from a even higher PoV.

Why did it get quicker at least twice, visually, after slowing down to a crawl? Could it be that it's just super inconsistent and the animators just weren't thinking nerds on the internet in idk 18 years(?) would try to dissect the cloud dispersal speed? Probably. Now I will say, that IS problematic, or at least it would be if we didn't have an approximate timeframe for the whole thing clearing out, that being 25 seconds, or if you really wanna lowball it, when she says their world is normal again (Don't think I need to say this, but the dark clouds were kind of one of their big problems).

Now you argue physics, sure, I get it, I get wanting to work with what see, but what we see doesn't align with your arguments or proposals. We have a workaround, you don't want to use it, or argue unfounded assumptions like cinematic cuts.
We have a basis by which we can make our judgements. The current one is arbitrary in that it does not align with that basis.
Hence the 25 seconds, 35 seconds if you want to stretch it to the statement.

Your basis mind you doesn't actually work with what we know, or even what we see (which isn't ideal given your argument hinges on visuals), but that's beside the point.
There's also the notion of cinematic time to crease over some of these bumps you're mentioning, a notion one feels we don't evoke as the creators of our given media.
Not an argument, you think Wario sat on his ass for half an hour? When he was literally there?

Prove there's a notable time jump. You made the claim, burden is on you.
I stand by just using the speed derived from the initial clearing period and then recognizing the actual value would be lower, but marking it any lower is arbitrary.
Except by your very own arguments that's objectively false. It actively speeds up, in fact it clears about 30km in one second.

The "initial" clearing is wrong. This simply isn't up for debate, we know it changes speed after the initial burst, and it isn't slower.
Cinematic timing, again.
Not how this works, you need to prove there's cinematic timing at play.

We have ample reason to believe there isn't. assuming there's a cut also causes numerous contrivences like him just sitting there doing nothing for an unrealistic amount of time. You argue this because the initial speed wouldn't possibly clear the whole radius within the alleged time, which fair, but we know because we outright see the cloud's move at inconsistent speeds, even speed up twice after the fact, and the final velocity is also, ironically, the quickest as it cleared a high-end horizon in seconds, and as such we can't actually use this argument for cinematic timing because it's just strictly all over to begin with, and even then, the final speed would be negligible based off the visuas if that's the argument. Coupled with a statement saying it's normal anyway in what, at worst, straight up being ignorant, would maybe be a minute or three, they say whole place is cool again.

This doesn't work Bambu. You think they sat there for whatever relevant amount of time before saying a single word to each other?
No video game is going to make you sit through everything that happens in real time. It'd be like... you're playing a game, you get on an airplane, then suddenly you're on the other side of the world. It makes no sense to presume, then, that the airplane is actually Massively Hypersonic.
False equilavence. Wario is in the SAME place as the money bag and the chick, they're all on that island, in fact he has a straight shot to them. The only timegap, is the gap between the boss dying and that scene, aka, about 25 seconds, as in, the cloud dispersal scene. Which is also reasonable amount of time for him to get back there.

A better example would be how long would it take you to walk across your house? You start at the front door, a cutscene plays, and then it goes back to you opening the backdoor and beginning to talk to whoever is there. We'd just say to timegap between Point A and B is however long the cutscene is, hell we might not even do that if the cutscene is to long.

Your airplane example doesn't work here.
There's just time passing in greater quantities than what is shown.
You need to prove that, simply saying it means nothing when there's ample evidence to the contrary, while your basis for claiming that is based on a faulty inconsistent speed that varies multiple times within the very scene itself.
Furthermore, they are allowed to say things are back to normal, even if it is implied it's actually getting back to normal in the near, immediate future.
Back to normal for the whole world, and will be back to normal soon, are not the same.
20 minutes is an insanely short time!
It's actually unrealistically long given the character's locations. You talked about object permeance yes? Why should we ignore it in regards to the characters?
It's basically no time at all. This statement has no bearing on the displayed speed, the speed we can physically see, of the clouds.
20 minutes isn't short, even if we take the final speed we see, it'd happen well beyond that. The speed we physically see of the clouds, as stated like 10 times now, is inconsistent, I can frame by frame it for you if need be.

No time had passed, we have no reason to BELIEVE any time had passed. It's the same location, the boss fight even crosses into that very room.
The only time shown, is the cloud parting scene Point A and Point B, and that's also a completely reasonable amount of time for Wario to simply walk back into the room.

You'd have to make extra assumptions any relevant amount of time passed within the same cutscene in the same place, that or they sat there doing nothing despite the fact Wario could not give less of a shit about anyone and just wants his money bag.

The statement does have bearing. They say the whole dimension is cool again, whole dimension, not some, not a bit, not going to, it just is. You're adding extra assumptions to arbitrarily extend the limit the scene takes place, and then arguing cinematic timeframe based off literally nothing, to argue the timeframe is actually longer than shown.
The actual argument is that you're wrong, plainly and simply.
Feeling's mutual.

Your argument is literally "use the objectively wrong initial speed" and "cinematic timeframe".
One is straight up incorrect onscreen.
And the other is headcanon, and wouldn't make sense anyway because that means it took Wario 20 minutes to walk into the room again. When he was literally already there.
It's taking 20 minutes. Or more, really, but I admit it's arbitrary to go lower, even though it would not be arbitrary to recognize that the value is certainly even lower.
I'd argue 1 minute is already an asinine assumption given Wario was already there.

What's arbitrary, is your arguments. You want to run with the objectively incorrect initial speed? You argue physics yet ignore the clouds literally parted about 2km in a second, then about 10 in ten seconds, and then like 60 in 2 seconds. Notice the problem there? There's no time skip, that's all in real time. We can literally hear the characters yap and cheer as it happens and switches without any cut off (Hard confirming there isn't any secret extra timeskip, otherwise the audio would jump as it's the lil ***** going yay!). Why'd it suddenly get like 30x quicker? After stopping almost even? That doesn't make much sense does it?
At worst you'd pick the last seen


(That one frame there at the end is intentional, it's the horizon view cleared).
Here, the clouds moving quite a bit slower compared to whatever, yet the immediate next frame is a clear sky.
Wild isn't? That doesn't make sense? Even the final frame you can see a bit of cloud in the corner, but, yet, we get a horizon shot from hundreds of meters high in the next frame that would make the horizon about 60km at minimum from the PoV? Without a timejump, given as mentioned, the merf's cheering isn't cut.
So, what's the speed? This whole clip? About 3 seconds? For 20kms at worst (60km horizon line, about 3 seconds)? The inbetween frame for 1800kms (60km, 1/30th of a second)?

Like what are you talking about? The speed isn't consistent all throughout, it changes, you'd have to arbitrarily pick one. You want to run with the initial one, yet the initial one isn't the final speed we see and thus not the speed we'd use for the exponential mass cleared after the initial area, based on your very own argument.

Worse case scenario is you'd calc the Pov distance between the up-angled shot, and then the wide view, get the speed from that, and maybe subtract the initial area? And I can assure you it's gonna be a hell of a lot quicker than what you're arguing.

As an aside, you're gonna have to prove cinematic timing, half your argument hinges on it, burden of proof is on you here. Quite frankly there's no reason to assume cinematic timing, and given you flatout said it's 100% taking 20 minutes, you best have good reason to explain why they'd just sit there for that long doing nothing.

Tldr.
1. Your argument hinges on the initial visual speed, this is visually shown to be contradicted, change multiple times, and even speed up. As such arguing based on it being consistent all throughout, doesn't work.
2. You argue cinematic timing despite no reason to assume as such beyond the already faulty point 1. With there being multiple reasons to assume it happening in real time, with it actively causing unrealistic assumptions should we assume as such. The burden of proof is on you here.
3. Twisting what is actually said, your argument hinges on the statement being future tense, even though it's stated in present tense. The words used state the whole of it, and in the present. Not will be in like a hour, or if we use the slowed down speed, like, a few days? Which should already tell give a big red flag back to point 1.
4. Even if we used visual speed, we'd use the last shown speed, not the initial, which is in and of itself contradictory to your argument as it's quicker by the end, not slower. And would be quicker then the final 1m and 25 seconds at face value (would clear it in a few seconds total), or based on the horizon line 3 second one, about like, 100-150 second time frame (aka, like, about between 1 and 3 minutes anyway).

You're wrong here, the only real compromise would be to use final displayed speed, which all things considered would just make it worse. And to also ignore blatant intent of the scene and the following statement, making extra assumptions as to what's being said based off an already contradictory point.

An easy way around the contradictory speeds and variances would be to just take the final timeframe, that being 25, like 35 if ya really wanna stretch it, seconds, as we can all but directly conclude that the storm is gone within that timeframe. This avoids using blatantly wrong speeds like your proposition, inflated speeds like 1800kms, and doesn't change the fact that by the end it's gone because they say it do so like, it's AT LEAST that and also basic media literacy, like it's pretty obvious what the intent is idk why we gotta jump through hoops. Otherwise, we would be using the final displayed speed over the initial speed because that's the final speed we seen, we'd have to assume it changed again, changed to the initial speed at that, all while ignoring it already covered exponentially more area in the final instance so assuming it slowed down just off screen is an even extra assumption. In no world would we ever do that.

Anyway I really, really, do not feel like dying on this hill i would rather waste my free time translating zelda and jojo yap, not **** with wario, so like, idk, I'd much rather have 3rd party CGM's weigh in, preferably those who even know wtf we're talking about. If need be I'll reply back in like idk, whenever, after I'm done tossing ch21 and Farore's Wind in shit if need be.
 
Last edited:
As an fyi, the whole "it don't fit with physics thing, so don't calc it" due to funny speed shit, nuh uh.
The alternative is to use like almost 100kms off that 1 second gap because it cleared the horizon between the cheering and the overhead beach view so we know the speed at some point, was at least that much, if not drastically higher (If it wasn't obvious, the horizon view being almost clould level itself, increases the horizon distance exponentially, hence the numbers I'm throwing out).

Obviously I think that's inflation, should just use the end of scene as timeframe, that's obviously the intent behind what we're being shown, but like, that's the alternative, technically not wrong, better than using the false initial velocity as that isn't the velocity most of the clouds would be cleared with, literally more accurate to the feat given it was the last seen velocity too thus the speed the majority of mass was pushed away at.

So either way.
 
Last edited:
Before I go into literally every single thing here, I want to provide a visual aid to show why this is all very silly.

Refer to the original calc for the math. Per the pixel scaling used, a pixel equates to 13.02 kilometers. While I disagree with its use, the calc suggests 40 kilometers as the initial area dispersed.

The image below is a slightly modified image used in the calc. It features a line representing the initial dispersed area of the storm, 40 kilometers in length, for comparison to the width of the full storm per the calc's math.

9GfPWSz.jpeg



I encourage you to look closely, it's a particularly vibrant pink, right about the mouth of Bowser's castle. It is three pixels long, because that is 40 kilometers on this map.

The calc as it currently stands suggests it took approximately 10 seconds to clear that 3 pixel hole in the cloud. It then suggests the entire rest of the red line took about 50 seconds over that. 3 pixels took 20% of the time it took to do 459 pixels, not even accounting for the fact that this is the direct inverse of how we should interpret its speed (that if anything, it ought to get slower, if we're applying real world physics to it).

This is so obviously, painfully wrong, that it is bizarre that it is being defended as though it wasn't. I will engage with the above post, but given that this cannot be interpreted as reasonable under any definition, I don't think it's really worth it to continue debate around this as though a point is had. It is not my intent to be rude, mind, it's plausible people don't really recognize the full error of their ways until it is presented visually. That is what evaluations are for, after all- to rectify such things. So, I'll reply as is necessary to the last thing, and then firmly state that this particular interpretation is self evidently nonsense.
 
Before I go into literally every single thing here, I want to provide a visual aid to show why this is all very silly.

Refer to the original calc for the math. Per the pixel scaling used, a pixel equates to 13.02 kilometers. While I disagree with its use, the calc suggests 40 kilometers as the initial area dispersed.

The image below is a slightly modified image used in the calc. It features a line representing the initial dispersed area of the storm, 40 kilometers in length, for comparison to the width of the full storm per the calc's math.

9GfPWSz.jpeg
Lad, this reeks of argument from incredulity, we obviously know the sizes involved, the sizes don't matter, what matters is the timeframe.
I encourage you to look closely, it's a particularly vibrant pink, right about the mouth of Bowser's castle. It is three pixels long, because that is 40 kilometers on this map.
Bro didn't watch the videos....
The calc as it currently stands suggests it took approximately 10 seconds to clear that 3 pixel hole in the cloud. It then suggests the entire rest of the red line took about 50 seconds over that. 3 pixels took 20% of the time it took to do 459 pixels, not even accounting for the fact that this is the direct inverse of how we should interpret its speed (that if anything, it ought to get slower, if we're applying real world physics to it).
So not an argument. But rather acknowledgment the visual speed is ******.
And then harping on physics, again.

I looked, I don't think you have though, you're saying the exact same thing you did before. That shit don't work my dude, no shit the speed is ******,

like dude, it straight up doesn't matter what you say at this point because no matter what you say, there's two facts that can't be debated. 1. The speed actively increases, this isn't up for debate. We see it happen.

Why even mention "it goes slower", it doesn't, it's wrong, we see it go FASTER, it shouldn't even be a thought that crossed your mind?
This is so obviously, painfully wrong, that it is bizarre that it is being defended as though it wasn't.
The feeling is mutual.
I will engage with the above post, but given that this cannot be interpreted as reasonable under any definition, I don't think it's really worth it to continue debate around this as though a point is had.
Unfortunate as it may be, it will be continued unless you can properly adress the numerous objectively faulty premises with your claims. And moreover prove why they're more reasonable over the alternative. We will see if that happens. If it doesn't happen, it will be continued because that is how this works.
It is not my intent to be rude, mind, it's plausible people don't really recognize the full error of their ways until it is presented visually.
This in itself is kinda rude. Mayhaps think people just don't agree with you?
That is what evaluations are for, after all- to rectify such things. So, I'll reply as is necessary to the last thing, and then firmly state that this particular interpretation is self evidently nonsense.
I mean we'll see, I sincerely pray to God your arguments don't rely on cinematic yap though.
 
Literally did but sure. What else would you mean by "the cloud is still dispersing offscreen"?
No, I didn't. Disperse is not the same as expand. This cloud is being dispersed, unless the implication is they're just shipping it off to somewhere else? It is being separated such that it is no longer a singular body of water vapor. By moving it in such an extreme way, the cloud is functionally destroyed. It doesn't just get pushed over, it's not a solid and doesn't act like that.

Yep, unfortunately that isn't an argument Bambu.
They say it's back to normal, they also actively try to convey as such with visuals. We know the finaltimeframe more or less, the only way this would work if there's a substantial timeskip, but we get to that later.

"Can" exist, and "does" exist, are not the same. We have no reason to assume it exists offscreen beyond using faulty logic, inconsistent onscreen visuals, and a whole other bunch of slop that gets immediately shot down.

This, would work, if it was consistent, in fact I even argued something similar for the Dark Star feat where we didn't have much of an established window and speeds only went one way, not all over. That isn't the case here though.
It doesn't fall to you to decide what is or isn't an argument; furthermore, not all I say must be an argument. I am not dedicated to debating. I am dedicating to evaluation. I am the one who must be convinced via debate. That is my role in the ecosystem.

Regardless. I talked about this on the calc itself, that saying "it's over" is a plausible and in fact normal thing to say when something is in the immediate process of becoming over. 20 minutes is comparatively zero time at all in such a situation. World War 2 was over for many years before the physical results of its existence were washed away. Some never will be. And yet, the war is still over- in that it is no longer producing those effects.

We don't know the final timeframe. You imply the final timeframe, but it does not align with what is realistic in this case.

Doesn't matter if that isn't what you're positing if that's the end result.

Your contention with the timeframe is, quite frankly, ridiculous.
The original area clear has 3 to 4 seperate speeds, it isn't consistent within itself. The original area doesn't matter, when we're told the whole dimension is fine now.
And none of them align with the end result. Relatively speaking those speeds are very minor fluctuations when compared to what you present as the most sensible option.

Varies exponentially. Inconsistent.

You want the displayed speed, we'd be using like 1800kms because that's the final displayed speed taken at face value. You see the issue yes? If we go with your premise, it only bloats it.
Not really? Exponentially is a strong word to use.

1800 kms isn't displayed, it's interpreted. You're being dishonest.

Stop the condescending remarks, that is beyond irrelevant, it could be smaller, bigger, how big it is doesn't matter, what matters is the timeframe for which it disperses.
Sincerely, this appeal to tone- I have no idea what in this was condescending, or could be interpreted as such. If you wanted to harp on my use of "lol" before, I don't intend for that to be condescending (I find part of this at least a little funny, not in a "I'm smarter teehee" way but a sincere level of incredulity), I'd have gotten it, but if anything, you are coming off as far more condescending. Regardless, this isn't relevant nor particularly out of the norm.

Yes. Especially because they say as much five seconds later.

This is an argument from incredulity. Who gives a shit how big it is? Fact is, it's evidently supposed to be gone by then. They show us it parting, they show us completely clear skies, it is followed by a statement saying the whole dimension has been brought to peace, whole confirming it isn't just that area atm. It is worded present tense, not future tense, so it going back to normal, isn't an argument, that is objectively not what is said.

Despite your claims, there is no relevant timejump, that room is on the very island Wario fought the final boss on, they even drop into it. We know he's still on the island because that's where the beam originates from in the cutscene, and we know Wario has a straight shot to that room and would take him literally not even 10 seconds to get back there, which he would, because his ass straight up doesn't care about being there and wants his money pronto.

Whether or not it makes sense doesn't matter, it just is. Like that's what happened. What do you want me to say? That's the intent behind the scene, that's also what they say, so it took that amount of time.
See my above comparison to World War 2.

No, it isn't. You keep presenting things as fact when they aren't. The fact is that we can see how long it takes to disperse over a comparatively small area. It doesn't matter what they say, because what they say is not a strict truth about reality. These are not Reality Warpers. It is over, because the cloud is dispersing.

I don't know how to explain Cinematic Timing further to you, so I guess I'll say "alright" and move on, acknowledging I don't accept your reasoning here.

We don't need to twist the vision to take the higher interpretations every time. This requires obvious obfuscations of certain facts to be sensible. I don't want or need you to say anything. Much like you believe of yourself, I am explaining to you How It Is. This isn't a debate, in that sense. It is an explanation.

Wild then that it literally sped up then no? (These clips, idk why they ain't loading as such, click them idk).


Look, it's a mere, idk 100-200ms a second in this instance. Absolute crawl, would take hours.

Yet suddenly


Gets quicker and we can visibly see it move at a far quicker speed from below as it passes by them (Completely ignoring it randomly got to the island, even though at the speed it was 5 seconds ago, it'd have taken like tens of minutes or something, which needless to say, they weren't jumping up and down looking at the sky in the same position for that long).

Only to then instantly clear the horizon even a second after that from a even higher PoV.

Why did it get quicker at least twice, visually, after slowing down to a crawl? Could it be that it's just super inconsistent and the animators just weren't thinking nerds on the internet in idk 18 years(?) would try to dissect the cloud dispersal speed? Probably. Now I will say, that IS problematic, or at least it would be if we didn't have an approximate timeframe for the whole thing clearing out, that being 25 seconds, or if you really wanna lowball it, when she says their world is normal again (Don't think I need to say this, but the dark clouds were kind of one of their big problems).

Now you argue physics, sure, I get it, I get wanting to work with what see, but what we see doesn't align with your arguments or proposals. We have a workaround, you don't want to use it, or argue unfounded assumptions like cinematic cuts.
Listen. I get it. The speed fluctuates. Call it intentional, call it the animators of a children's game not necessarily having the greatest respect for consistency of such a trivial detail, call it literally anything- it doesn't fluctuate enough to enable the interpretation sought out here. Like. Of all your points, this is the realistic one. I agree this shit fluctuates. But not to this degree.

Hence the 25 seconds, 35 seconds if you want to stretch it to the statement.

Your basis mind you doesn't actually work with what we know, or even what we see (which isn't ideal given your argument hinges on visuals), but that's beside the point.
It does. It sincerely does. Yours does not. And since all of this is... just "what I said is correct" vs "what I said is correct", I don't feel like offering further explanation.

Not an argument, you think Wario sat on his ass for half an hour? When he was literally there?

Prove there's a notable time jump. You made the claim, burden is on you.
No, he probably did what he did immediately after that scene, more or less immediately after that scene- we both agree that bit was approximately 10 seconds. But he also didn't necessarily stick around to make sure every bit of cloud vapor was cast out, did he?

Except by your very own arguments that's objectively false. It actively speeds up, in fact it clears about 30km in one second.

The "initial" clearing is wrong. This simply isn't up for debate, we know it changes speed after the initial burst, and it isn't slower.
Is it the bolding of words you interpreted as condescending? If so, what gives?

Regardless: no, it isn't? We can even kind of prove it doesn't speed up notably after the first bump, given that the speed at 3:34 is approximately equal to the speed at 3:29. To match the proposed model, it would need to be significantly quicker- it isn't, it's the exact same. So the only jump in speed is after the initial burst. Which is fine, because I don't suggest using the initial burst, I suggest using clearing the horizon.

Not how this works, you need to prove there's cinematic timing at play.

We have ample reason to believe there isn't. assuming there's a cut also causes numerous contrivences like him just sitting there doing nothing for an unrealistic amount of time. You argue this because the initial speed wouldn't possibly clear the whole radius within the alleged time, which fair, but we know because we outright see the cloud's move at inconsistent speeds, even speed up twice after the fact, and the final velocity is also, ironically, the quickest as it cleared a high-end horizon in seconds, and as such we can't actually use this argument for cinematic timing because it's just strictly all over to begin with, and even then, the final speed would be negligible based off the visuas if that's the argument. Coupled with a statement saying it's normal anyway in what, at worst, straight up being ignorant, would maybe be a minute or three, they say whole place is cool again.

This doesn't work Bambu. You think they sat there for whatever relevant amount of time before saying a single word to each other?
I don't really, it just needs to be reasonable. And it is, here- there are many jump cuts and a major event unfurling. Our own page on the subject even suggests that cinematic time (that is, the time occurring on-screen) is generally different from the literal time counter, the issue lay in determining how different the two are. In many cases, the differences aren't extreme, but given the circumstances of this feat, it seems plausible it's making some minor difference. I don't feel it's worth contemplating much, given it isn't the main deciding factor of the whole feat, though. It just is an actual thing that is likely happening, so much so that the calc creator (who I note is opposed to my interpretations as well, and is seemingly supporting yours) suggested it as well (albeit in the other direction). We, as humans, can interpret things with startling accuracy, in this instance it just seems very obvious.

False equilavence. Wario is in the SAME place as the money bag and the chick, they're all on that island, in fact he has a straight shot to them. The only timegap, is the gap between the boss dying and that scene, aka, about 25 seconds, as in, the cloud dispersal scene. Which is also reasonable amount of time for him to get back there.

A better example would be how long would it take you to walk across your house? You start at the front door, a cutscene plays, and then it goes back to you opening the backdoor and beginning to talk to whoever is there. We'd just say to timegap between Point A and B is however long the cutscene is, hell we might not even do that if the cutscene is to long.

Your airplane example doesn't work here.
Yeah, we mentioned this before (in this comment, specifically)- for some reason, you're assuming Wario has to stay around to wait until the end of the storm's dispersal. He doesn't, as far as I can tell he can have his scene on him approximately 10 seconds later, 20 seconds, 60 seconds, whatever you want- that's perfectly allowed. Given I don't contest this, but it also isn't mutually exclusive to the issue, I don't see this as constructive.

Back to normal for the whole world, and will be back to normal soon, are not the same.
This isn't how writing works, man. I don't have a way to explain to you that it's an art form and you can't have every character say 100% exactly what they mean every time. That's bad writing. The concept of language always has contextual information within it. The writing further isn't going to say this because it's a children's game. You're expecting a level of exactitude that no children's game has ever offered on anything.

It's actually unrealistically long given the character's locations. You talked about object permeance yes? Why should we ignore it in regards to the characters?
No it isn't. It is realistically very likely. Where they are doesn't really mean anything- the characters are on a beach surrounding the castle, or in the castle (fortress? whatever you'd like to call it).

20 minutes isn't short, even if we take the final speed we see, it'd happen well beyond that. The speed we physically see of the clouds, as stated like 10 times now, is inconsistent, I can frame by frame it for you if need be.

No time had passed, we have no reason to BELIEVE any time had passed. It's the same location, the boss fight even crosses into that very room.
The only time shown, is the cloud parting scene Point A and Point B, and that's also a completely reasonable amount of time for Wario to simply walk back into the room.

You'd have to make extra assumptions any relevant amount of time passed within the same cutscene in the same place, that or they sat there doing nothing despite the fact Wario could not give less of a shit about anyone and just wants his money bag.

The statement does have bearing. They say the whole dimension is cool again, whole dimension, not some, not a bit, not going to, it just is. You're adding extra assumptions to arbitrarily extend the limit the scene takes place, and then arguing cinematic timeframe based off literally nothing, to argue the timeframe is actually longer than shown.
Yes, it is. Practically any full task you do in life will take 20 minutes or more time.

We have reason to believe time has passed. This is objectively incorrect. It's obviously incorrect, even. Some amount of time passed from Point A to Point B- you guys have just latched onto 1 minute for some reason. I hope you'll forgive me not addressing points I either don't think are relevant or are already handled- the Wario walking point is in the former camp.

No I wouldn't.

This last part doesn't even really make sense. "Your courage has restored peace to the whole of the Shake Dimen-" isn't about the speed or rate of completion of the storm's dispersal. Again, these aren't mutually exclusive. The whole storm being gone isn't the requirement for peace to be restored here. The requirement is that the step necessary for it to end has been done. This isn't evidence it isn't a curretly ongoing thing.

I'd argue 1 minute is already an asinine assumption given Wario was already there.

What's arbitrary, is your arguments. You want to run with the objectively incorrect initial speed? You argue physics yet ignore the clouds literally parted about 2km in a second, then about 10 in ten seconds, and then like 60 in 2 seconds. Notice the problem there? There's no time skip, that's all in real time. We can literally hear the characters yap and cheer as it happens and switches without any cut off (Hard confirming there isn't any secret extra timeskip, otherwise the audio would jump as it's the lil ***** going yay!). Why'd it suddenly get like 30x quicker? After stopping almost even? That doesn't make much sense does it?
At worst you'd pick the last seen
You can argue what you want, Wario being where Wario is isn't an element of my position.

I've gone over this, as well. I don't contend that the speed of the initial burst is the same as the speed after that. I do contend that this doesn't justify the ramping up of speed implied. I will disagree with the audio bit, although if it were something with more inclination to adhere to reality, I'd be more inclined to agree. Soundbites carrying over from one scene to another isn't a particularly uncommon thing.

(That one frame there at the end is intentional, it's the horizon view cleared).
Here, the clouds moving quite a bit slower compared to whatever, yet the immediate next frame is a clear sky.
Wild isn't? That doesn't make sense? Even the final frame you can see a bit of cloud in the corner, but, yet, we get a horizon shot from hundreds of meters high in the next frame that would make the horizon about 60km at minimum from the PoV? Without a timejump, given as mentioned, the merf's cheering isn't cut.
So, what's the speed? This whole clip? About 3 seconds? For 20kms at worst (60km horizon line, about 3 seconds)? The inbetween frame for 1800kms (60km, 1/30th of a second)?

Like what are you talking about? The speed isn't consistent all throughout, it changes, you'd have to arbitrarily pick one. You want to run with the initial one, yet the initial one isn't the final speed we see and thus not the speed we'd use for the exponential mass cleared after the initial area, based on your very own argument.

Worse case scenario is you'd calc the Pov distance between the up-angled shot, and then the wide view, get the speed from that, and maybe subtract the initial area? And I can assure you it's gonna be a hell of a lot quicker than what you're arguing.

As an aside, you're gonna have to prove cinematic timing, half your argument hinges on it, burden of proof is on you here. Quite frankly there's no reason to assume cinematic timing, and given you flatout said it's 100% taking 20 minutes, you best have good reason to explain why they'd just sit there for that long doing nothing.

Tldr.
1. Your argument hinges on the initial visual speed, this is visually shown to be contradicted, change multiple times, and even speed up. As such arguing based on it being consistent all throughout, doesn't work.
2. You argue cinematic timing despite no reason to assume as such beyond the already faulty point 1. With there being multiple reasons to assume it happening in real time, with it actively causing unrealistic assumptions should we assume as such. The burden of proof is on you here.
3. Twisting what is actually said, your argument hinges on the statement being future tense, even though it's stated in present tense. The words used state the whole of it, and in the present. Not will be in like a hour, or if we use the slowed down speed, like, a few days? Which should already tell give a big red flag back to point 1.
4. Even if we used visual speed, we'd use the last shown speed, not the initial, which is in and of itself contradictory to your argument as it's quicker by the end, not slower. And would be quicker then the final 1m and 25 seconds at face value (would clear it in a few seconds total), or based on the horizon line 3 second one, about like, 100-150 second time frame (aka, like, about between 1 and 3 minutes anyway).

You're wrong here, the only real compromise would be to use final displayed speed, which all things considered would just make it worse. And to also ignore blatant intent of the scene and the following statement, making extra assumptions as to what's being said based off an already contradictory point.

An easy way around the contradictory speeds and variances would be to just take the final timeframe, that being 25, like 35 if ya really wanna stretch it, seconds, as we can all but directly conclude that the storm is gone within that timeframe. This avoids using blatantly wrong speeds like your proposition, inflated speeds like 1800kms, and doesn't change the fact that by the end it's gone because they say it do so like, it's AT LEAST that and also basic media literacy, like it's pretty obvious what the intent is idk why we gotta jump through hoops. Otherwise, we would be using the final displayed speed over the initial speed because that's the final speed we seen, we'd have to assume it changed again, changed to the initial speed at that, all while ignoring it already covered exponentially more area in the final instance so assuming it slowed down just off screen is an even extra assumption. In no world would we ever do that.

Anyway I really, really, do not feel like dying on this hill i would rather waste my free time translating zelda and jojo yap, not **** with wario, so like, idk, I'd much rather have 3rd party CGM's weigh in, preferably those who even know wtf we're talking about. If need be I'll reply back in like idk, whenever, after I'm done tossing ch21 and Farore's Wind in shit if need be.
Listen man. This is a lot of typing and a lot of it is what we've gone over already. So, cool. I'm also probably not going to reply to the message I see you've posted already, because I get the sense that this is getting unnecessarily heated over Mario, for God's sake. Nothing that has been said is particularly compelling reason to not take the on-screen speed (the second, sped up one). If you want to grab CGMs, that's fine, although this isn't really a matter of CGMs anymore, given that the math itself has been evaluated and accepted by Dalesean. Interpreting non-calc issues relating to a calc is a hazy issue, could be interpreted as a thread mod issue or a CGM issue. Regardless, I'll ping a few of each, if it is of concern.

@Armorchompy @Ugarik @SeijiSetto @DMUA @AbaddonTheDisappointment @Agnaa @Damage3245 (I'm pinging a lot of you so buckshot can take effect- lot of shrapnel, bound to hit one of ya).

For incoming staff to evaluate. This is the calc at issue, and the only messages you really need to read (sparing you eleven pages of agony) are those following this one. You're free to read more, if you want, although nothing of that pertains to my particular grievances with the calc, and thus will be variably relevant. I thank you personally for those of you who do evaluate.

I'm going to issue now an informal warning to @Chariot190 to approach this matter with respect, as I do not feel you have been doing so and this has been an issue in the past: play nice. Read out what you're typing before you hit enter. For my part, I will try to observe, but will not likely be replying much, unless there's something particularly worthy of discussion.
 
Even if the warning's informal, there's really no reason to give it. Yeah, it's necessary to play nice, but that wasn't really being adhered to with the implication that people who disagree with your interpretation "don't recognize the error of their ways until something is presented visually." People can just... disagree, y'know?

As for the issue at hand, I'm out of town at the moment, so I may or may not get to it at my earliest convenience. I could at least get to this, though, which really did not sit right with me
 
Even if the warning's informal, there's really no reason to give it. Yeah, it's necessary to play nice, but that wasn't really being adhered to with the implication that people who disagree with your interpretation "don't recognize the error of their ways until something is presented visually." People can just... disagree, y'know?

As for the issue at hand, I'm out of town at the moment, so I may or may not get to it at my earliest convenience. I could at least get to this, though, which really did not sit right with me
An informal warning isn't a warning, Clover. It's the step before to not continue on along the path. I give it, because Chariot was being rude, and I've acquiesced with his request to summon some CGMs here to speak on the matter. Treating me with rudeness is one matter, treating those I ask a favor of is another. Only if the surly attitude is sustained will a warning be given. This isn't "because he disagrees with me", and I take offense at the implication.
 
An informal warning isn't a warning, Clover. It's the step before to not continue on along the path. I give it, because Chariot was being rude, and I've acquiesced with his request to summon some CGMs here to speak on the matter. Treating me with rudeness is one matter, treating those I ask a favor of is another. Only if the surly attitude is sustained will a warning be given. This isn't "because he disagrees with me", and I take offense at the implication.
You kinda missed what I was saying. I'm not saying your informal warning was because of you being disagreed with. I'm just saying that I don't think you were necessarily playing nice either (I used the whole "error of their ways" response to being disagreed with to show that), so even an informal warning on your end is strange to me. I agree with your sentiment, I'm sure most people would, but it doesn't land as well if you're doing the same thing you're telling someone else not to do, y'know?

That said, if we're to continue this, it's best kept somewhere else that isn't here
 
I don't intend to discuss the feat further, as mentioned, so I suppose I didn't even consider that. Presumably Chariot intends to debate against any further points, hence my saying. I also wish to say I do not consciously denigrate others, and still am not certain what condescension was interpreted from my words- even the bold thing is only a hazarded guess.

Regardless. The informal warning remains. Now, you wait for others to come along.
 
Back
Top