CraftBukkit, Spigot, and Paper have all, for a long time, made changes to the server that changes the behavior to differ from the vanilla game. This is not always wanted by some server owners (see PaperMC/docs#21 and PaperMC/docs#326).
One solution would be to introduce the concept of multiple different configuration presets:
- the "recommended" preset, which would be what our current configuration becomes
- the "vanilla behavior" preset, which sets certain configuration options to the value that restores the behavior to match vanilla
The initial thought for this would be a command line option, such as:
-Dpaper.configurationPreset=<preset name>: Sets the configuration preset to be used. If the configuration files have not been generated, the preset specified will be used when generating them. If the configuration does exist, nothing will change.
-Dpaper.configurationPresetForce=true: Option to force modifying an existing configuration to match the specified preset.
The start script generator could potentially also have an option to specify this option as well.
CraftBukkit, Spigot, and Paper have all, for a long time, made changes to the server that changes the behavior to differ from the vanilla game. This is not always wanted by some server owners (see PaperMC/docs#21 and PaperMC/docs#326).
One solution would be to introduce the concept of multiple different configuration presets:
The initial thought for this would be a command line option, such as:
-Dpaper.configurationPreset=<preset name>: Sets the configuration preset to be used. If the configuration files have not been generated, the preset specified will be used when generating them. If the configuration does exist, nothing will change.-Dpaper.configurationPresetForce=true: Option to force modifying an existing configuration to match the specified preset.The start script generator could potentially also have an option to specify this option as well.