-
Notifications
You must be signed in to change notification settings - Fork 632
Dampe Fire #5521
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dampe Fire #5521
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I realize this is a lot more simple than a slider to adjust the difficulty, but I think additionally allowing to go in the other direction to make dampe harder would be more popular among players. Shouldn't block this just my 2 cents.
|
I would also prefer it to be a difficulty option with a slider, but if you don't want to handle that here, just changing it from CVAR_CHEAT to CVAR_ENHANCEMENT would be enough to get this merged. |
|
Dampe has 2 variables: a 32 frame cooldown & a 3% chance per frame to drop flame I expect slider would want to effectively be a multiplier on frequency. So 2x would halve cooldown & double odds of dropping flame. Amusingly this works out so that at 33x dampe will drop a flame 99% of the time every frame. Does that behavior seem suitable for slider? |
|
My gut feeling is that it would want more precise control than an integer multiplier, similar to have the frogs timer feels awkward for only having whole number increments, but a float would be too precise and could introduce wierd step functions based on the frame cooldown when set very high (which people will do, because it's funny). I think handling it with 2 sliders would be clearest: 1 for the cooldown and another for "aggression" (as I think "flame chance per frame" would be misleading with cooldown, we can be honest with how it works in the tooltip) |
|
2 sliders is excessive. Maybe dropdown inspired by aMannus#9:
|
|
That's fair, but if the highest level isn't "Dampe's Inferno" I'm blocking 😛 |
|
If the averages are accurate for them, I'd be OK with that, too. I love the "Dampe's Inferno" idea, lmao. |
|
Implemented. Added Dampe's Inferno as 20/1s Overall the spicy levels seem alright. The randomness involved dropping the flames really starts to become interesting with Ghost Pepper where you have to weave between flames. I'd want someone to figure out if Dampe's Inferno can be completed in under a minute.. he leaves behind a wall of fire. Maybe using i-frames from rolls |
|
time for some pepper name bikeshedding! i'd like to recommend
|
|
normal -> vanilla? Scotch bonnet is what I use making sauce, same ballpark as habanero Modern Jalapeño is 1/5 imo, https://www.dmagazine.com/food-drink/2023/05/why-jalapeno-peppers-less-spicy-blame-aggies |
|
i agree jalapeño isn't spicy, just figured going off wiki ratings would give us something to point to. i was just going for what i think are super well known peppers which is why i suggested hab but I'm fine with whatever maybe instead of just normal or just default or just vanilla it could be "Default (Vanilla)" - still not certain on that one |
|
I like spiciness, but why not add some milder options between None and Vanilla? Some ideas:
LOL at "Ghost Pepper" |
|
I should also ask, are these cooldowns affected by interpolation? |
No |
|
I don't see value in crowding options between None & Vanilla. There's already a few options more than I'd like |
|
I agree about not wanting to put something between none and vanilla, and I think vanilla by itself as a name is fine, so I'm going to go ahead and merge it. |
* No Dampe Fire * spicy * bikeshed
Particularly important for use with #5435
Build Artifacts