Jupeyy
Jupeyy
I guess this is good enough for a first try.
Bounce is relativly easy to fix: https://github.com/Jupeyy/ddnet/commit/55f5da8655f552f47e46c9d35c808e071ecb7937 It would still defs be a physic change and a rethink on how weapons are handled. E.g. should a unfreezing laser be before...
> Speaking of, does anyone know what method KoG uses to fix weak/strong? I'm sure it's not perfect but I've never seen anyone complain about it. Probably the 0.7 approach....
> > Bounce is relativly easy to fix: [Jupeyy@55f5da8](https://github.com/Jupeyy/ddnet/commit/55f5da8655f552f47e46c9d35c808e071ecb7937) > > That doesnt fix the bounce. Can you give the example map? i tested it with a few heights and...
Mh yeah the move is also unfair, and when is moving this indeed is a problem, good find ^^ I dunno if thats fixable in a sense of one having...
fng also uses strong only, and 0.7 too. I won't judge about the need of ddnet tho, but i like it for gores and fng. So i don't see a...
should we merge it inside the look and remove the continue in ```c++ if(i == ENTTYPE_CHARACTER) continue; ``` I know ENTTYPE_CHARACTER is currently last in the enum, but its less...
should we also just rename the name then, else its missleading as in hammer fly
Depends on what you call simpler. 0.7 changes the physics variables. This just moves code around.. But go ahead. I'm five as long we have an option for strong
Ready to merge, fokko already notified avo: https://github.com/ddnet/ddnet/pull/5987#issuecomment-1298281556