ofilter/Elphelt
1
0
Fork 0
mirror of https://github.com/OriolFilter/Elphelt.git synced 2025-06-25 19:13:23 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity

Deglossed StandardRoutes

Browse Source
This commit is contained in:
oriol
2024-10-20 15:56:52 +02:00
parent 84688fc661
commit 2623b97736
10 changed files with 341 additions and 354 deletions
Download Patch File Download Diff File Expand all files Collapse all files

67
docs/Routes_Optimization/BnB/README.md Normal file
View File

@ -0,0 +1,67 @@
The idea about this doc, is checking when/if its better to "optimize" shit for extra damage
## c.S > f.S > ? > Bridal
> Tested on Sol only.
| Route | Damage | Notes |
|:-----------------------------|:-----------------------------------------------------------|:----------------------------|
| c.S > f.S > Bridal | 88 | |
| c.S > f.S > 2D > Bridal | 114 | |
| c.S > f.S > 2S > 2D > Bridal | 129 | Requires dash momentum 100% |
| c.S > f.S > 5H > Bridal | 100 | |
| c.S > f.S > 2S > 5H > Bridal | 117 | Requires dash momentum 100% |
| c.S > f.S > 2S > Bridal | **FAKE**/**NOT POSSIBLE**, after 2S Bridal won't connect!! | |
TLDR:
With dash momentum:
> c.S > f.S > 2S > 2D > Bridal
Without dash momentum:
> c.S > f.S > 2D > Bridal
## c.S > f.S > ? > Bridal RC > BNB
c.S f.S > ? > Bridal RC > 2H > Pull Berry > c.S > j.S > jc j.K > j.S j.H > j.Toss |> 6H > SG.pull > SG.S > SG.unpull? > c.S > j.KSH
| Route | Damage | Notes |
|:-----------------------------------|:-------|:----------------------------------------------------|
| c.S > f.S > Bridal > ... | 199 | |
| c.S > f.S > 2D > Bridal > ... | 199 | |
| c.S > f.S > 2S > 2D > Bridal > ... | 198 | Requires dash momentum 100%. Makes the combo harder |
| c.S > f.S > 5H > Bridal > ... | 186 | |
| c.S > f.S > 2S > 5H > Bridal > ... | 188 | Requires dash momentum 100% |
**TLDR: Keep it simple.**
> c.S > f.S > Bridal > ...
OR
> c.S > f.S > 2D > Bridal > ...
(Check with sol at low HP)
## c.S f.S > ? > Genoverse > j.KSH |> 2P > c.S > j.KSHD
| Route | Damage | Notes |
|:-----------------------------------|:-------|:---------------------------------------------------|
| c.S > f.S > Bridal > ... | 174 | |
| c.S > f.S > 2D > Bridal > ... | 184 | |
| c.S > f.S > 2S > 2D > Bridal > ... | 190 | Requires dash momentum 100%. |
| c.S > f.S > 5H > Bridal > ... | 178 | |
| c.S > f.S > 2S > 5H > Bridal > ... | 188 | Requires dash momentum 100% |
**TLDR: Keep it simple.**
> c.S > f.S > Bridal > ...
OR
> c.S > f.S > 2D > Bridal > ...
(Check with sol at low HP)

32
docs/Routes_Optimization/Control_Opponent_Height/README.md Normal file
View File

@ -0,0 +1,32 @@
# Controlling opponent height
## Air normals
Saybel video, pgood
https://youtu.be/rii4r63fpZE
## Shotgun
### Walkthrough from interactions
#### 5H Toss/Bridal vs 6H Toss/Bridal
6H reduces the opponent height substantially, 5H not that much, damage difference is usually minimal when at 100%.
### Increase height
#### SG.S Toss
D
### Decrease height
This can mean how to actually decrease opponent height, to how to prevent opponent height to be risen as much as possible.
#### SG.S Toss
Delay toss hit so berry hits 1-3 before about to explode, this will cause opponent to gain a bit of height, then proceed with the falldown.
This is caused to the first frames after being hit by the

3
docs/Routes_Optimization/README.md Normal file
View File

@ -0,0 +1,3 @@
# Routes Optimization
Mostly a mix of comparing multiple routes with the "effort" and "reward", to see if the "reward" compensates.

45
docs/Routes_Optimization/Routing_into_Genoverse/README.md Normal file
View File

@ -0,0 +1,45 @@
# Standard routes
## Comboing into Genoverse
Possible followups.
6H (Ender)
6H (Bridal |> Pickup)
### j.KSH |> (2P >) > (c.S) rejump
`j.KSH` can be perform by doing:
- Genoverse > IAD j.KSH
- Genoverse > 66 ~ j.9KSH
#### General Notes
> Notes:
>
> Depending on the height/distance whatever every single button from `j.KSH` will require some degree of delay, specially the `j.H`, since we are rising the height of the opponent (without getting that high that we can't combo), in order for us to land in the ground before the opponent and still have time to pickup with 2P or c.S.
>
> The damage difference without using `2P` is that low that it's recommended to pickup with `2P > c.S` for more stability/consistency.
>
> Against lightweights I believe `sj.IAD j.KSH` to be more consistent than `IAD j.KSH` (generally speaking).
>
> Stuff like IADs look cool, but as per the moment I cannot justify them over doing the `Genoverse > 66 ~ j.9KSH` except the extremely specific instance where I did `Genoverse > 66 ~ sj.9SH` and allowed for `j.D |> f.S > 5H > Bridal`.
>
> Being able to use IAD also depends on the proximity from the opponent, as being too close would result in dropping the combo (not being able to route j.KSH).
#### On not prorated combos
At very high distances `Genoverse > 66 ~ j.9SH` _can_ route into `j.D |> f.S/5H` Pickup, but no knockdown.
From `Genoverse > 66 ~ sj.IAD 9SH` I was able to get `j.D |> f.S > Bridal`, once. Since it's an IAD, requires some spacing... For reference, I believe it was on Johnny, nevertheless it's a simulation that resembles something that I would call as too much inconsistent, therefore if one is found in such situation, take the j.D knockdown, you can still do the `superjump IAD` stuff, but aiming to get the j.D knockdown, not picking up from that.
#### On prorated combos
> Notes:
>
> Both `IAD` (or `sj.IAD`) should be usable in prorated combo routes, as it's less likely that the opponent goes over your character due to combo gravity, nevertheless I also believe that all the instances that the `IAD` routing can be used, one cana also use the `66 j.9`, therefore for consistency/simplifying things ij recommend going for the `66 j.9` routing on all the main scenarios.