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

Bleach Calc issues

Status
Not open for further replies.
16,960
4,860
Since it was mentioned in Kepekley's post that some bleach calcs were purposely inflated by user's, who are now banned, it's better to make this thread now to get it settled.

If there really are bleach calcs, most notbly ones like the Aushwhalen one, that were purposely done wrong to give them better ratings, then at least some if not all of the bleach calculations need to be looked over and talked about, or just flat out redone, to get better precise results. I for one don't have a clue about whats wrong and what isn't but just wanted to make this thread just in case it's never made so we can correct the mistakes that were made.

That is all.
 
The problem is Bleach isn't so much that but rather that we probably need a whole read of the manga to revise it.
 
Who was the one that re-read Bleach before and made blogs about it?

Im pretty sure it was someone who wasn't banned and is still here IIRC.
 
Thats at least a good start.

Because of the unexpected and unfortunate turn of events, most likely the whole majority or center of Bleach's statistics have suffered a very big blow from this. Until someone has re-read the manga to redo or revise certain important calcs for Bleach, should we just temporarily restrict CRT's about Bleach for a while then?
 
Soldier Blue said:
I honestly think we need to take another look at the High 6-A and Tier 5 calcs. The Tier 7 ones are mostly not controversial.
Anything above tier 6 like Gremmy's meteor to the better stuff definitely needs to be looked at again. The lower stuff can probabaly stay or just be revised later on for not being as important.
 
Matthew Schroeder said:
Prom and I talked about doing it in the future potentially.
I recently re-read the entire manga myself. Some feats I think are wanked (like Petaton level Gremmy meteor) and some may have been underestimated (like lifting and speed feats for Lieutenant level characters).
 
ProfessorKukui4Life said:
Anything above tier 6 like Gremmy's meteor to the better stuff definitely needs to be looked at again. The lower stuff can probabaly stay or just be revised later on for not being as important.
Funny thing is that the 7-A stuff is actually somewhat consistent, since there are three feats on that level.

What bugs me are the following:

High 6-C Hitsugaya (child form)

6-A to High 6-A Gremmy

I even have doubts about a High 6-C calc I myself did.
 
Wrath Of Itachi said:
Isn't Grammys feat only that high because of the new size of the SS?
He stated that his meteor was going to destroy Seireitei. Assuming the currently accepted Seireitei diameter and playing around with the impact calculator, the meteor could be downgraded to 6-B or lower end of High 6-B.
 
6-B is honestly far more believable. And that's if we are going with that size, too.

At least we don't have 5-B Meteor using Mach 1 Travel Speed to calculate Seireitei's size, lmao.
 
Honestly, with everything thats happend, a huge chunk of mathematics for Bleach will probably need to be revised, more than expected anyway.
 
The main problem with the Seireitei size is that uses a statement to get a size which contradicts all visuals (Which itself wouldn't be that bad), but then apply this calculated size to panels where Seireitei is demonstrably not drawn as that large, to calculate the size of the meteor.

It's the same as Island level Beefcake via calculating his largest possible size, and then applying that size to his crater feat - Even though you can perfectly scale Beefcake's size in the same panel due to the buildings on the shot.
 
I am not familiar with One Punch Man, so I won't comment about Beefcake.

But I will say this about Seireitei: The walking statement was made by someone who lived there for a long ass time. And being the former head of an organization that specializes in espionage and assassination, she seems unlikely to be the type to exaggerate. There is also that one instance where two characters seemingly took three days to walk from one part of Seireitei to another.

That all being said, Seireitei being the size of the Korean peninsula and High 6-A Gremmy do seem wanked.

@Matthew

Remind me again: What is the currently accepted Seireitei size?
 
It's something like 500 km wide which seems very unrealistic and unbeliavable.

@Soldier Blue

Beefcake has an official height in the guidebook, but literally every single panel of reference for his size in the manga contradicts that.
 
The Gremmy Meteor calc is an exact Carbon Copy Calculation of the previous 6B calculation. Everything, the method, the steps and the scalings are 100% taken by the previously accepted 6B calculation.

The thing which changed the result fromn 6B to 6A is just the new Seireitei Size.

There wasnt a new calc made. Just the already in effect calculation for years has been updated with new numbers.
 
Just revert the god tiers back to 6-A then.

EZ

On serious note, what if we're use the old size of 32 km while using 20km/s for meteor speed? That'll be less "controversial" IMO.
 
"If there really are bleach calcs, most notbly ones like the Aushwhalen one, that were purposely done wrong to give them better ratings, then at least some if not all of the bleach calculations need to be looked over and talked about, or just flat out redone, to get better precise results. I for one don't have a clue about whats wrong and what isn't but just wanted to make this thread just in case it's never made so we can correct the mistakes that were made. "

Like i said on the message wall: " we are only using calcs made by raven, kep and blue and calcs that were approved by them". We have not accepted a calc like what you described.
 
Matthew Schroeder said:
It's something like 500 km wide which seems very unrealistic and unbeliavable.
@Soldier Blue

Beefcake has an official height in the guidebook, but literally every single panel of reference for his size in the manga contradicts that.
Question: Didn't you accept the new size?
 
The Causality said:
i hope my calc about Mountain level isn't inflated
I don't think it is. Kepekley revised my Shikai storm calc to 513 Megatons. That is bordering on Mountain level+ already.
 
the point is that we need to figure out if they did inflat their math since someone said they had a way to do it without calc members finding out. We dont know if its right since it could be covered up. We're just beign safe and checking the calcs over again
 
I don't understand how could someone inflate calculations, but at the same time make it look good in the eyes of those who's job is to verify calculations.

Though it might just be my lack of understanding on how the calc group works (I'm kinda new here).
 
AstralKing7 said:
the point is that we need to figure out if they did inflat their math since someone said they had a way to do it without calc members finding out. We dont know if its right since it could be covered up. We're just beign safe and checking the calcs over agai
They didn't, if they did it would've been delt with
 
you do understand the guy said he had a way that wouldnt let people know?? He could have easily showed others how to do it since they were in the same discord. The point is just to double check, whats the problem
 
AstralKing7 said:
you do understand the guy said he had a way that wouldnt let people know?? He could have easily showed others how to do it since they were in the same discord. The point is just to double check, whats the problem
You do understand the calcs i posted were from admins and calc group members that weren't apart of the discord fiasco right?
 
I'd sill rather it we checked through the calcs again to be on the safe side, especially after what Matt and Blue talked about above.
 
Ok, the size of Seireitei has to be sorted out once and for all (as if, lol). I think Soldier should talk with Kep to get a solution to this, at least for the foreseeable future since 32km is too small.

Assuming the size doesn't reduce, the 5-C calc should be okay. I believe what Soldier is referring to about the Gremmy calc is the method used or something, judging by this:

He stated that his meteor was going to destroy Seireitei. Assuming the currently accepted Seireitei diameter and playing around with the impact calculator, the meteor could be downgraded to 6-B or lower end of High 6-B.
 
Didn't Raven just changed the size of seirietei based on the accepted low end and used the exact same method as before?

I think the "inflated" calc is because the size of seireitei, which people found 458 km diameter is too unrealistic.

Isn't there's another low end of around 203 km of diameter?
 
The only person that said they inflated calcs was Thebluedash who has ironically not done any of the recent accepted calcs for Bleach (and Blue hasn't even done a calc since August 23, 2017).

If you assume the other banned calc member inflated calcs then it effects nothing since UMR hadn't done Bleach calcs.

The current accepted calcs are by RavenSupreme and Soldier Blue, so they're really all fine since those calcs went through the normal process and were accepted.
 
Wasn't there a calc made scaling the size of the meteor to the Wandenreich (and getting the size of the Wandenriech by scaling from Uyru's height)?

I think that result was lower than the currently accepted result.
 
Status
Not open for further replies.
Back
Top