If PATH has a Java version less than 17 (which I need to keep for other reasons), then mcsctl's minimum version check fails when trying to start a modern Minecraft server, even if I have edited the launch script to use a newer version.
Due to the automatic 'sudo -u mcs' redirect not passing through env vars, simply exporting a new PATH before running mcsctl doesn't get around this unless already running as the mcsctl user.
Possible fix: allow setting the java executable to use in mcsctl.conf (default to "java"). This at least allows passing the check and launching modern servers without having to change global PATH.
Ideally, java version could be configurable per server, but we don't have per-server configuration support at the moment (outside of editing the launch script).
If PATH has a Java version less than 17 (which I need to keep for other reasons), then mcsctl's minimum version check fails when trying to start a modern Minecraft server, even if I have edited the launch script to use a newer version.
Due to the automatic 'sudo -u mcs' redirect not passing through env vars, simply exporting a new PATH before running mcsctl doesn't get around this unless already running as the mcsctl user.
Possible fix: allow setting the java executable to use in mcsctl.conf (default to "java"). This at least allows passing the check and launching modern servers without having to change global PATH.
Ideally, java version could be configurable per server, but we don't have per-server configuration support at the moment (outside of editing the launch script).