I have a question regarding the Minecraft module in AMP.
Why is the Minecraft Java configuration in AMP so out of date compared to current Minecraft versions?
For example, the default value for the level-type field in server.properties has not been DEFAULT for quite some time. Modern Minecraft versions use minecraft:\normal as the default value, yet AMP still generates:
level-type=DEFAULT
instead of:
level-type=minecraft:\normal
I’ve also noticed that the AMP Configuration page is missing many of the options that exist in the current server.properties file. A number of newer properties—and even some existing ones—aren’t exposed through the panel, so the only way to configure them is by manually editing server.properties. Even then, AMP reverts many of the changes made to server.properties the next time the configuration is saved through the panel.
Is there a reason the Minecraft module hasn’t been kept up to date with changes to server.properties?
It would also be nice if AMP exposed the full set of server.properties options through the Configuration page instead of only a subset. For example, settings related to RCON, the management server, and other server properties currently require manual edits. Having the panel stay in sync with the complete server.properties file would make server administration much easier and eliminate the need to manually maintain settings that AMP doesn’t currently expose.
Are there any plans to update the configuration templates and expand the available configuration options in the AMP panel?