Mykhailo Ivanchenko 9ecdfca06f Fix lazymc never recognizing the Forge server as ready ...

Missing forge = true under [server] meant lazymc couldn't parse the
Forge status response (extra embedded mod-list payload vanilla
doesn't have), so it never detected the backend as online and always
showed the "still starting" kick screen. Also documents the inherent
~25-30s client-timeout race on the very first cold-boot connection.

2026-10-23 15:50:30 +02:00

..

setup-server.sh

Fix lazymc never recognizing the Forge server as ready

2026-10-23 15:50:30 +02:00