Hajt: HTTP fallback guarantees that current implementations keep working without effort. Since it always was HTTP before I don't see a major issue with now using HTTPS first and then HTTP as fallback. It would be another story if I just added HTTP as fallback to an existing system that already offers HTTPS. Also properly configured servers shouldn't even serve HTTP anymore unless there is a good reason to do so.I may remove HTTP entirely later or add an option to disable it.
Regarding Brotli:
CS2D doesn't transfer any big files via HTTP (unless you add http links to servertransfer.lst. I doubt that people are using this feature a lot because it caused lags in the past. Maybe it's not even working anymore). Therefore adding Brotli for HTTP is pretty useless.
I could switch the UDP file transfer compression to Brotli but impact wouldn't be huge. Also Brotli is much heavier on CPU which isn't optimal either.
(Apparently BlitzMax-NG even has modules with Brotli support already. I wouldn't even have to mess with C myself)
In general I'm not planning to continue optimizing tons of things in CS2D now.
@
Mora: If you have a compatible controller it should just work with the controls I explained in the beginning. If you have an unsupported controller you can still try to add the configuration manually to sys/gamecontrollerdb.txthere's an explanation about how to create such a mapping: https://github.com/mdqinc/SDL_GameControllerDB
(if you do the work you can also open a pull request there so other games can benefit from it as well)
Experimental Controller Support


Offline