No interactive console exists since lazymc/systemd run the server in
the background, and mcrcon isn't packaged for Debian 13. Plain
Python3 RCON client instead, reads the password straight from
server.properties. setup-server.sh now copies it into mcserver/.
v0.2.11 has a confirmed open regression (timvisee/lazymc#65, #86):
it never recognizes a Forge server as online regardless of uptime,
so every connection just times out on the "still starting" screen
forever. forge=true alone doesn't fix it. 0.2.10 correctly detects
readiness (verified: "Server is now online" + successful relay).
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.
Chunky + DH-on-server crashes on first chunk load (confirmed open
upstream bug, DH GitLab #1329). DH's own INTERNAL_SERVER generation
mode does the same pregen job without the conflict, plus streams
accurate LOD to clients automatically (no manual flying pass needed).
Corrects Vivecraft/CPM/ViveCraft Compat to both-sides (needed for
other players to see VR body movement, not just client-only). Fixes
lazymc.toml duration-string bug (sleep_after wants an integer, not
"5m"). Replaces the screenshot-derived mod list with ground truth
from the actual exported client zip.
Drops the standalone fileserver systemd unit from setup-server.sh in
favor of Gitea's already-public raw-file serving. Adds VR (Vivecraft)
and quest (FTB Quests) mod docs, the DH/Chunky server-side crash
warning, and documents the real deployment target (always-on homelab
box, not a venue-local machine).
Mykhailo Ivanchenko