excellent. i have reached the classic game dev nightmare: juggling multiple multipliers from various sources. already had some issues with jumping underwater
3
1
36
Conversation
options:
- halve gravity/speed when entering water, double when leaving (other changes clobber; can desync; terminal velocity is global)
- turn gravity/speed/terminal velocity into properties ("slower" but it's lua who cares)
- explicit support for a fluid resistance multiplier
2
6
thinking about this is also an excellent distraction from figuring out what water should actually /look like/ because i have no idea
4
5
my rendering is also getting increasingly complicated as i try to combine silhouetting, palette shifts for only part of the screen, and distortion effects
1
1
4
aaand i realize that what i'm doing for water will become yet more complicated if i expect to have jagged foreground edges in front of it
1
1
well that didn't quite work right
2
21
oh hell yeah
GIF
6
6
66
hello, my 2D sprite game has fifty postprocessing passes so you will need a $5000 video card to run it
5
3
52
glip held me at gunpoint until i put the palette translation together by hand instead of slopping a multiply layer on it, and now it's good
GIF
Replying to
also re the original problem this thread was about: i think i should actually go with the fluid multiplier, because then when you jump out of water, you'll speed up — which feels Really Good, like breaking free
3
11
i threw the translation on the entire world to see how stuff looks and, whoa, this is rad
2
1
24
