9ecdfca06f7b78a61de70c3277091e33b048a116
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.
mc-lan-party
Lan mc prep
Description
Languages
Shell
55%
PowerShell
37.5%
Python
7.5%