Okay, it looks like I linked directly to ssl libs. I've change it to do late time binding the first time you use ssl or crypto functions i.e. LoadLibrary+GetProcAddress/ this means the problem you mentioned is fixed and there no longer hard requirements for ssl libs on the client machines. Use git pull to stay on top of the latest updates.

https://github.com/sysrpl/Bare.Game/...4b2?diff=split

A side note, in some units which depend on external libs, including sdl2 unit and ssl unit, I provide the option to link statically. This means you can build ssl and sdl into your exe directly through lib.a files. The reason I have it off by default is so that systems can have up to date libs rather than potentially stale static libs. In the future I may maintain static lib.a files more frequently.