Welcome to Smashboards, the world's largest Super Smash Brothers community! Over 250,000 Smash Bros. fans from around the world have come to discuss these great games in over 19 million posts!
You are currently viewing our boards as a visitor. Click here to sign up right now and start on your path in the Smash community!
lol
I had completely forgotten about my application so getting an infraction out of nowhere kinda scared me lol
I read you beat Megafox, hype
Hover over your name in the top right, go to Preferences, and it's under Style Options
Shroobers, that's a new one lolDoing god's work Shroobers.
Okay, thanks!
What sort?
I'd say go for it. This is a forum after all where we discuss things
I was thinking on it, but I havent worked much on customs, and it would be much work for me (although i alreay have all custom moves)
What do you mean by this? Like what are you trying to determine with this equation?
I'm going to figure everything out. Distance, speed, the ties between knockback and velocity, vectoring and DI, accelerations... establish it so that we can measure these values in the real game
how are you going to ddo this? There are obviously in game parameters for values like that, but first you would need to fin a constant value to depart from and actually knowing what you are looking for
I'm already done with that part! Only about 2% error
Mind if I see it? Im curious about this. Also, if you are trying to get something with speed and mobility, you may want to be wary of terrain an tractiond differences. (This is actually one of the topics i have in min, no much discussing, but labbing)
I'd like some opinions on something I've been working on, if y'all don't mind.
Here's one of mysecretprojects:
https://docs.google.com/spreadsheets/d/1_IAFcQB-EnN1jC_hQ6zuGAHBx-9kD7syEMn0sbV8Ibo/edit?usp=sharing
I went through all the sets in Shine's Top 8 and recorded the opponent's percent and the user's percent for every kill. With that data, I originally wanted to compare the approximate ranges at which characters tend to kill. So I averaged the percents of when each character killed their opponents. After doing that, it became clear to me that the data wasn't showing an accurate picture. Only using data when characters kill doesn't say anything about when they fail to kill. Using Pikachu as an example, only using data when he killed said nothing about the fact that ZeRo's Diddy survived until 199%, never getting killed, during Grand Finals. And such an occurrence is important to note when talking about a character's ability to kill. So then I looked at the peak damage for every character's opponent in every individual game. Oftentimes, an opponent reached their peak damage when they were killed. But there were some key places where it was different (like in ESAM's and ZeRo's set during Grand Finals). Using the data from both of these categories (if a datum appeared in both categories, it was only used once), I averaged them and called it the survivability of the opponent, meaning how long we can expect an opponent to live against a given character. It seemed to make logical sense to me: Using the percent damage of an opponent when they were and weren't killed to come to an approximate percent range we can expect the opponent to survive 'til, thus giving us something somewhat concrete to use to compare characters' killing abilities. Then again, I could be missing something. Which is why I'm sharing this with all of you. Input from other people would certainly help and ensure that this isn't a misguided approach or something.
You probably will end up with some bias from your fairly niche group. Recording data from just top 8 limits the applicability away from non-top 8 circumstances.I'd like some opinions on something I've been working on, if y'all don't mind.
Here's one of mysecretprojects:
https://docs.google.com/spreadsheets/d/1_IAFcQB-EnN1jC_hQ6zuGAHBx-9kD7syEMn0sbV8Ibo/edit?usp=sharing
I went through all the sets in Shine's Top 8 and recorded the opponent's percent and the user's percent for every kill. With that data, I originally wanted to compare the approximate ranges at which characters tend to kill. So I averaged the percents of when each character killed their opponents. After doing that, it became clear to me that the data wasn't showing an accurate picture. Only using data when characters kill doesn't say anything about when they fail to kill. Using Pikachu as an example, only using data when he killed said nothing about the fact that ZeRo's Diddy survived until 199%, never getting killed, during Grand Finals. And such an occurrence is important to note when talking about a character's ability to kill. So then I looked at the peak damage for every character's opponent in every individual game. Oftentimes, an opponent reached their peak damage when they were killed. But there were some key places where it was different (like in ESAM's and ZeRo's set during Grand Finals). Using the data from both of these categories (if a datum appeared in both categories, it was only used once), I averaged them and called it the survivability of the opponent, meaning how long we can expect an opponent to live against a given character. It seemed to make logical sense to me: Using the percent damage of an opponent when they were and weren't killed to come to an approximate percent range we can expect the opponent to survive 'til, thus giving us something somewhat concrete to use to compare characters' killing abilities. Then again, I could be missing something. Which is why I'm sharing this with all of you. Input from other people would certainly help and ensure that this isn't a misguided approach or something.
Just passing by, but very interested in seeing this in the future.
)
I'm not really bothered to look through and check, but do you also account for or factor in the reeling animation? Some tests I did a while ago showed that it would let you act 1 frame sooner unless there was a cap in place. https://smashboards.com/threads/untechable-reel-animations.439039/page-2#post-21320830
It should give Knockback to the 7th decimal place. I pretty much have all of the necessary data for it to output the proper result almost all of the time. The only places where there are gaps in the data are with "Frames Until Air Dodge" and "Frames Until Attack". You see, at high knockback values, "Frames Until Air Dodge" and "Frames Until Attack" change at an irregular pattern (it doesn't even follow changes in hitstun, lol). Once they pass certain knockback values, they increase by 1. I have no easy way of identifying the exact KB values for when they change. The best I could do was narrow down the possibilities. The way I collected data was by using Pikachu's Up Throw on Bayonetta at various percents and then counting the number of frames until a certain action was performed. Because Pikachu has quite a few moves that do decimal damage, I could check different percents to the tenths place. Thanks to that, the range of possibilities for each individual KB threshold is only 0.0570652. Thus, when someone uses the calculator, there is a only small chance that the calculator will give them an error. Even if someone does get an error, I ask for that to be reported to me so that I can personally recreate the situation, identify the "Frames Until Air Dodge/Attack" and further narrow down the range. So it's a win-win. c:
I did not. But I will add this information to the calculator page.
Myran
and Olimar. You can read it here:
