- 4,736
- 4,308
Gonna keep this short and sweet.
This calc was rejected by DMUA for calc stacking, specifically because it assumes Pochita's speed is Supersonic based on scaling from Quanxi. The logic there is that Quanxi is canonically Supersonic in base, becomes faster when transformed and Pochita is able to speed blitz her in that state. He can also blitz characters who are capable of perceiving fighters on her level and is generally portrayed as moving so fast that he kills people and destroys objects simply because he can't control his speed or strength.
That said, DMUA brings up a fair point: character speeds are not consistent across every context. Even if Pochita is far beyond baseline Supersonic overall, that does not automatically mean he is moving at that level in every single scene.
In this particular moment, Pochita is visibly far more restrained. There's a noticeable lack of the effort we normally associate with him when he's actually trying or acting on instinct. This is especially important because later in the manga, we repeatedly see Pochita interrupt Yoru's weaponization outright. In contrast, here we have a situation where weapons are able to travel from places like the Gulf of Mexico and Mount Elbrus, complete their weaponization and reach Yoru before Pochita can even touch her.
That difference in portrayal strongly suggests that Pochita is holding back in this scene, or at the very least moving well below his usual combat speed.
Because of that, I made a completely separate calculation that does not rely on scaling from Quanxi or assuming Supersonic chainsaw speed. Instead, I treated Pochita's movement here as Superhuman as a conservative low-end, since we can actually see him moving in the moment, unlike other scenes where he casually kills or destroys things against his will (see the above). This is also a stronger version of Pochita, which further goes to show that this is him not going all out.
If the counter arg is that this entire situation comes down to panel perception or timing ambiguity, that's fine. I'm open to adjusting the endpoint. I'm not trying to push anything above the norm here. If there's a better conservative speed assumption to use for this scene, I'm open to hearing it. The new calc, is also consistent with speeds that Pochita already scales to.
Agree: (0:1) @Breadbear83
Disagree: (3:1) @ElJoaki5 (Believes the former calc is fair game), @Drite77, @Saqphire, @Dalesean027
Neutral: (0:0)
This calc was rejected by DMUA for calc stacking, specifically because it assumes Pochita's speed is Supersonic based on scaling from Quanxi. The logic there is that Quanxi is canonically Supersonic in base, becomes faster when transformed and Pochita is able to speed blitz her in that state. He can also blitz characters who are capable of perceiving fighters on her level and is generally portrayed as moving so fast that he kills people and destroys objects simply because he can't control his speed or strength.
That said, DMUA brings up a fair point: character speeds are not consistent across every context. Even if Pochita is far beyond baseline Supersonic overall, that does not automatically mean he is moving at that level in every single scene.
In this particular moment, Pochita is visibly far more restrained. There's a noticeable lack of the effort we normally associate with him when he's actually trying or acting on instinct. This is especially important because later in the manga, we repeatedly see Pochita interrupt Yoru's weaponization outright. In contrast, here we have a situation where weapons are able to travel from places like the Gulf of Mexico and Mount Elbrus, complete their weaponization and reach Yoru before Pochita can even touch her.
That difference in portrayal strongly suggests that Pochita is holding back in this scene, or at the very least moving well below his usual combat speed.
Because of that, I made a completely separate calculation that does not rely on scaling from Quanxi or assuming Supersonic chainsaw speed. Instead, I treated Pochita's movement here as Superhuman as a conservative low-end, since we can actually see him moving in the moment, unlike other scenes where he casually kills or destroys things against his will (see the above). This is also a stronger version of Pochita, which further goes to show that this is him not going all out.
If the counter arg is that this entire situation comes down to panel perception or timing ambiguity, that's fine. I'm open to adjusting the endpoint. I'm not trying to push anything above the norm here. If there's a better conservative speed assumption to use for this scene, I'm open to hearing it. The new calc, is also consistent with speeds that Pochita already scales to.
Agree: (0:1) @Breadbear83
Disagree: (3:1) @ElJoaki5 (Believes the former calc is fair game), @Drite77, @Saqphire, @Dalesean027
Neutral: (0:0)
Last edited: