Geoff Bourne

...and trying ```yaml environment: EULA: true MOTD: "welcome to §athis server§r!§r\nwe are playing §bVanilla Minecraft §d1.20.2" TYPE: PURPUR ```

Something seems to be unusual with GraalVM. I see what you are reporting with `java17-graalvm` but changing only the image to `itzg/minecraft-server:java17` generates the properties file correctly: ``` motd=Herzlich willkommen...

Agreed, there's entire compatibility suites that the JREs are supposed to comply with...but maybe properties I/O is not part of that 😀 And Oracle gets to do whatever they want...

> That's unusual, i expected the server properties to not be influenced by the bundled java runtime To clarify this, the mc-image-helper tool, which is used for several things including...

> Ah, that's the part that i missed. I thought that that was also part of the shell scripts in the container. Thanks for the clarification. FWIW it used to...

Since you did not provide your container config I cannot confirm how you have TTY or stdin setup. In any case, `docker attach` is a docker leave mechanism that connects...

...one thing you could try it setting the env variable `EXEC_DIRECTLY` to "true". The server may no longer stop gracefully, but that'll eliminate any possible interference in the console attachment.

Thanks, yes, I realized later it was probably that. I'll need to research how to directly associate the stdin/out rather than relaying the content between them.

Thanks for writing this up. So the FastAsyncWorldEdit is an interesting case since there's two files per build: `FastAsyncWorldEdit-Bukkit-2.8.1-SNAPSHOT-575.jar` vs `FastAsyncWorldEdit-CLI-2.8.1-SNAPSHOT-575.jar`. I'm thinking the reference to each "jenkins URL" will...

CommandHelper seems to be an especially strange and difficult one to automate generic retrieval. It's also strange since they used to provide github releases (https://github.com/EngineHub/CommandHelper/releases), but seem to have stopped...