Geoff Bourne

@jcotton42 can you confirm this was absent from your PR. Since you mentioned the use case, it seems like you have included it.

Cool. Just wanted to check. I believe putting the invocation in a conditional should satisfy the `-e` constraint. @Fysac if you're interested in PR'ing this, then that would be great.

The Forge installer failed, so it's beyond my control. It looks like a networking issue so might be temporary.

Looking at the download page, I'm thinking that was before they had installers. Is the download just a server jar, ready to run?

Oh, I remember doing that whole thing. OK, this is becoming an enhancement, not a bug. Quite doable but not trivial.

I have never know why it mentions two or more ports on the logs. 19132 is only one I know needs to be mapped.

@Hamsterman thats odd since that's already the default from the image https://github.com/itzg/docker-minecraft-bedrock-server/blob/8a2f1bfeada27aad8208991ec7de20b23cb376c0/Dockerfile#L46

@Hamsterman with list-style environment don't include the quotes. `"19132"` is getting literally set in server.properties.

That tutorial was contributed by a community member, but you may want to look through and/or comment on this discussion to see if that can help https://github.com/itzg/docker-minecraft-bedrock-server/discussions/386

Sorry, I haven't gotten a chance yet to confirm if it does the same for me.