- 8,126
- 12,354
And so we return... at the turn of the tide...
Yeah, we're back. Upgrading some speed. Applying calcs. Getting faster. You know how it is.
Here is the calc we will be discussing.
Essentially: Lady Nagant's bullets are ridiculously faster than any other known sniper rifle bullets out there. This calculation is finding the speed of her muzzle velocity from her shooting at Deku. The speed found is about Mach 100, meaning any one who scales to 45% Deku will become baseline Massively Hypersonic
Also, in reference to the claims I've seen, Deku absolutely knows how strong a howitzer shot is. He is one of the greatest hero nerds out there, and Bakugo, who he analyzes and notes down and researches more than anyone, has a move that references a howitzer. I don't find it hard to believe at all that he looked up howitzers to see how strong they actually are as a frame of reference for Bakugo's attack.
Anywho, here's what we need to discuss:
Going off of that basis, the people who scale would be:
Lady Nagant (Duh)
45% Deku (Duh)
AFO Shigaraki (Just as fast as 45% Deku if not faster at some points, its back and forth between them)
Gran Torino (Saved Deku from AFO Shigaraki and could react to him before he got faster)
High Ends (Comparable to AFO Shigaraki and Endeavor (Note: Near High Ends during the war suck at hitting things cause they couldn't stabilize, which is why they didn't blitz everyone))
USJ Nomu (Is compared to the other High Ends and Shigaraki as he is a perfect Nomu)
All Might (Weakened, can keep up with the USJ Nomu)
100% Deku (All versions prior to Final Act, just as fast as USJ All Might and gets faster, accidentally did a High Hypersonic+ feat with 1 leg)
OFA Bakugo
Nine with Tubes Broken (Can keep up with FC 100% Deku and Bakugo)
Mirko (Beat up the High Ends)
Hawks (Is the fastest Pro Hero)
Bakugo with Cluster (Reached Deku before AFO Shigaraki could hit him, and was a big part in catching up to Faux 100%)
People who should STAY High Hypersonic+ as they are demonstrably slower than those above:
Endeavor (Can fight AFO Shigaraki and react to his attacks, but is noticeably slower than him and Deku. Slower than High Ends somewhat)
Gigantomachia (Should get a possibly Massively Hypersonic, but in general seems slower than other Nomu despite being the strongest)
Kamino AM (much weaker than his prior state which is comparable to 100% Deku)
Kamino AFO (Comparable to the weakest All Might)
Wolfram (Comparable to weakest All Might)
Best Jeanist (Should be put at High Hypersonic+ rather than Unknown for his feat against AFO)
And that's that I believe.
Now for part 2:
As I am the one making the blog, I decided to do some thinking and looking around for the specifics of what this would be. Here's what I got.
So, the proposal: Use a calculated attack speed to find the movement speed of a character blitzing that same attack.
Counter: This is calc stacking as per our rules.
So, lets look at the rules:
Here is the page for Calc Stacking and our rules on the subject. Immediately, I'm finding a few things that support the usage of Calc Stacking in this specific instance, rather than against.
Important thing to note: Calc Stacking Is Not Instantly Bad
This was something I was led to believe, that Calc Stacking in any scenario whatsoever is not allowed or will always yield terrible results. This is not the case. As specified in the rules, there are several instances where Calc Stacking CAN be acceptable.
Thus, with all of this taken into account, how does the usage of Calc Stacking in the case of Nagant's Bullets fair? I believe that it meets the requirements to be allowed.
The biggest objection to its usage is obviously that "it couldn't be the exact same speed." However, in this specific case, the bullet Nagant fired is actually stated to be a higher shot velocity. For this specific instance, it is not anything vague as "being serious" or "trying harder": She is without question making this bullet faster than any bullet so far seen. Velocity is a big part for Nagant's entire character, and it is her body that's doing the shooting, so she knows precisely how fast her shots are. Yet she asserts that, with this all or nothing bulk up move, she is making her shots even faster.
This is compounded by the fact that even before this panel, Deku notes that her shots have been getting faster the closer he gets to her, a product of being closer to the initial velocity of her gun. He is still able to dodge the bullets, but even through his Danger Sense, it is getting difficult. So for her to then state that she is going to ACTUALLY increase her shot velocity, and the noticeably increasing the strength of her rifle to accomplish this, I believe it is safe to say that the bullet she fires from her gun at this point in time is AT LEAST as fast as the bullet she fired that was calculated.
If this is the case, then all other conditions have already been met. The pixel scaling being used is incredibly consistent with projectile, person and building sizes, and Deku outspeeds the projectile which, as I have argued, is superior in velocity to the previous calculated projectile. This meets the applicable requirements for Calc Stacking to lead to the least inflated results possible.
I understand this is going to cause derision, but this topic needs a dedicated response. I believe we have a genuine case of allowable Calc Stacking, but am open to disagreement or disproval.
Should this be accepted, the most that will happen is 3 people in the verse get to be 1 speed tier higher than the rest. If not, we stay at the same rating but "higher." At the end of the day, the change brought by this is to an incredibly limited amount of characters. However, its better this was said than silently argued.
And that's basically it for the revision.
Yeah, we're back. Upgrading some speed. Applying calcs. Getting faster. You know how it is.
Here is the calc we will be discussing.
Essentially: Lady Nagant's bullets are ridiculously faster than any other known sniper rifle bullets out there. This calculation is finding the speed of her muzzle velocity from her shooting at Deku. The speed found is about Mach 100, meaning any one who scales to 45% Deku will become baseline Massively Hypersonic
Also, in reference to the claims I've seen, Deku absolutely knows how strong a howitzer shot is. He is one of the greatest hero nerds out there, and Bakugo, who he analyzes and notes down and researches more than anyone, has a move that references a howitzer. I don't find it hard to believe at all that he looked up howitzers to see how strong they actually are as a frame of reference for Bakugo's attack.
Anywho, here's what we need to discuss:
The People Who Scale
Obviously, this muzzle velocity needs to scale to people, as Deku at 45% can react to this. He obviously scales, since he can avoid several of Nagant's shots consecutively.Going off of that basis, the people who scale would be:
Lady Nagant (Duh)
45% Deku (Duh)
AFO Shigaraki (Just as fast as 45% Deku if not faster at some points, its back and forth between them)
Gran Torino (Saved Deku from AFO Shigaraki and could react to him before he got faster)
High Ends (Comparable to AFO Shigaraki and Endeavor (Note: Near High Ends during the war suck at hitting things cause they couldn't stabilize, which is why they didn't blitz everyone))
USJ Nomu (Is compared to the other High Ends and Shigaraki as he is a perfect Nomu)
All Might (Weakened, can keep up with the USJ Nomu)
100% Deku (All versions prior to Final Act, just as fast as USJ All Might and gets faster, accidentally did a High Hypersonic+ feat with 1 leg)
OFA Bakugo
Nine with Tubes Broken (Can keep up with FC 100% Deku and Bakugo)
Mirko (Beat up the High Ends)
Hawks (Is the fastest Pro Hero)
Bakugo with Cluster (Reached Deku before AFO Shigaraki could hit him, and was a big part in catching up to Faux 100%)
People who should STAY High Hypersonic+ as they are demonstrably slower than those above:
Endeavor (Can fight AFO Shigaraki and react to his attacks, but is noticeably slower than him and Deku. Slower than High Ends somewhat)
Gigantomachia (Should get a possibly Massively Hypersonic, but in general seems slower than other Nomu despite being the strongest)
Kamino AM (much weaker than his prior state which is comparable to 100% Deku)
Kamino AFO (Comparable to the weakest All Might)
Wolfram (Comparable to weakest All Might)
Best Jeanist (Should be put at High Hypersonic+ rather than Unknown for his feat against AFO)
And that's that I believe.
Now for part 2:
Calc Stacking: Can this be applied further?
One of the more... polarizing questions being asked around about this feat is: can we use the muzzle velocity to find the speed of Faux 100%. We all know the feat.As I am the one making the blog, I decided to do some thinking and looking around for the specifics of what this would be. Here's what I got.
So, the proposal: Use a calculated attack speed to find the movement speed of a character blitzing that same attack.
Counter: This is calc stacking as per our rules.
So, lets look at the rules:
Here is the page for Calc Stacking and our rules on the subject. Immediately, I'm finding a few things that support the usage of Calc Stacking in this specific instance, rather than against.
Important thing to note: Calc Stacking Is Not Instantly Bad
This was something I was led to believe, that Calc Stacking in any scenario whatsoever is not allowed or will always yield terrible results. This is not the case. As specified in the rules, there are several instances where Calc Stacking CAN be acceptable.
- Pixel scaling over several steps is permitted, as long as the size of the scaled objects usually stays constant.
- Using the calculated speed of a projectile to calculate the speed of a character dodging said projectile on the very same occasion is usually permitted, as long as the projectile wouldn't have changed its speed mid flight.
- Using speed of characters or attacks calculated at other instances can't be used, as characters and attacks can vary in speed. This is the case regardless of whether the character is seriously trying to do his best or anything similar.
Thus, with all of this taken into account, how does the usage of Calc Stacking in the case of Nagant's Bullets fair? I believe that it meets the requirements to be allowed.
The biggest objection to its usage is obviously that "it couldn't be the exact same speed." However, in this specific case, the bullet Nagant fired is actually stated to be a higher shot velocity. For this specific instance, it is not anything vague as "being serious" or "trying harder": She is without question making this bullet faster than any bullet so far seen. Velocity is a big part for Nagant's entire character, and it is her body that's doing the shooting, so she knows precisely how fast her shots are. Yet she asserts that, with this all or nothing bulk up move, she is making her shots even faster.
This is compounded by the fact that even before this panel, Deku notes that her shots have been getting faster the closer he gets to her, a product of being closer to the initial velocity of her gun. He is still able to dodge the bullets, but even through his Danger Sense, it is getting difficult. So for her to then state that she is going to ACTUALLY increase her shot velocity, and the noticeably increasing the strength of her rifle to accomplish this, I believe it is safe to say that the bullet she fires from her gun at this point in time is AT LEAST as fast as the bullet she fired that was calculated.
If this is the case, then all other conditions have already been met. The pixel scaling being used is incredibly consistent with projectile, person and building sizes, and Deku outspeeds the projectile which, as I have argued, is superior in velocity to the previous calculated projectile. This meets the applicable requirements for Calc Stacking to lead to the least inflated results possible.
I understand this is going to cause derision, but this topic needs a dedicated response. I believe we have a genuine case of allowable Calc Stacking, but am open to disagreement or disproval.
Should this be accepted, the most that will happen is 3 people in the verse get to be 1 speed tier higher than the rest. If not, we stay at the same rating but "higher." At the end of the day, the change brought by this is to an incredibly limited amount of characters. However, its better this was said than silently argued.
And that's basically it for the revision.