![]() |
VOOZH | about |
I've recently added classic and alpha server histories (as much as I could), I just put the name of the server version (as it differed from client version), I guess this is okay?
Also, are there any Beta server software changelogs anywhere? Couldn't find them on the wiki, unless I'm blind.
--Chewsterchew2001 (talk) 01:07, 2 May 2020 (UTC)Chewsterchew2001
I think that `hide-online-players` is missing from the list. It is mentioned in the `History` section, but it is missing from the list od properties. – Unsigned comment added by KRunchPL (talk • contribs) at 10:34, 30 January 2022 (UTC). Sign comments with ~~~~
In previews-chat, the lines "true - Enabled. Server prevents users from using vpns or proxies. false - Disabled. The server doesn't prevent users from using vpns or proxies." should be in the cell above, 'prevent-proxy-connection' – Unsigned comment added by Batpope (talk • contribs) at 08:13, 14 July 2022 (UTC). Sign comments with ~~~~
Through testing I have found that "op-permission-level" was added in the 1.7.2 release version, it was not present in 1.7.1 or prior I cannot however find any documentation for this addition This could also be added to the history for w/Permission_level Rickiegamer (talk) 06:29, 18 December 2023 (UTC)
There is no row in the Java Edition keys table for the log-ips property. --Contrabass27 (talk) 23:25, 29 December 2023 (UTC)
The part on the resource-pack-sha1 states:
That is very wrong. The nature of hash functions, and their entire purpose, is based on the mathematical fact that this cannot happen. If that message appears, your client really has downloaded something different than what the server intended you to run. I assume that the client will then refuse to actually use the pack. The SHA1 checksum is meant to prevent errors due to e.g. download corruption. Due to the nature of hash functions there is an extremely tiny chance that your client download went wrong, but the hash is still identical, and this problem is not detected. This may then cause issues such as crashes. Note that it cannot be considered a security feature, as SHA1 is not secure enough for that any more.
Please remove the erroneous statement.
Ghostbird 87.101.7.205 12:15, 23 March 2024 (UTC)
In the last paragraph of the intro (where UTF-8 is mentioned), it would be great to specify that .properties is a relatively standardized format (not specific to Minecraft) and would help people who want to develop tools around it. You could link the Wikipedia page (https://en.wikipedia.org/wiki/.properties and maybe the Javadoc? https://docs.oracle.com/javase/8/docs/api/java/util/Properties.html). It doesn't have to take more than one sentence but I think it's valuable information for a wiki.
Apparently I need to do 5 contributions before being able to edit this page (it's a bit weird to expect free work from users before they're able to contribute more free work...), so I'll let someone else do this. Ans (talk) 16:09, 18 July 2024 (UTC)
Apparently I need to do 5 contributions before being able to edit this page (it's a bit weird to expect free work from users before they're able to contribute more free work...), so I'll let someone else do this.
The current link for its format points to the article about generatorOptions which, as far as I'm concerned, is deprecated since after 1.15. The current file demands formatting as in https://misode.github.io/worldgen/flat-world-preset/ , except only the lines inside of settings{}, so the generator-settings can be viewed as the server.properties equivalent of the settings field in the mentioned Github tool. As far as my testing goes, I also think the server.properties needs this to be a one-liner, so no pressing enter between options. Contrary to the article on the older generatorOptions option, colons also don't need to be escaped with \: Edit to attach a Minecraft bug report for more information on the topic: https://bugs.mojang.com/browse/MC-182421 79.246.220.28 10:15, 6 October 2024 (UTC)
Description of enforce-whitelist is incorrect.
Currently is:
false - Online players that are not on the whitelist are kicked.
true - Online players that are not on the whitelist arekicked.
Should be:
false - Online players that are not on the whitelist arekicked.
true - Online players that are not on the whitelist are kicked. Ohtacaro (talk) 14:23, 18 November 2024 (UTC)
This setting will generate Debug world NikitaCartes (talk) 01:43, 24 December 2024 (UTC)
Add a comment to the description explaining that a value of -1 will disable the functionality. Erik508 (talk) 22:38, 15 March 2025 (UTC)
I have checked the code of versions 1.20.1 up to 1.21.6, and they contain no references of parsing the generator-settings value, only minecraft:flat does anything with the field. 78.63.214.40 12:28, 10 August 2025 (UTC)
The current description for online-mode currently only mentions that it should be false on servers not being connected to the internet.
This leaves out a major point, which is servers that are running under a Proxy such as BungeeCord or Velocity for the purpose of connecting multiple servers together and load-balance large player quantities. No matter the proxy's online-mode settings, the server itself needs to have its online-mode disabled as it would otherwise not function properly.
One can argue that the "Set this to false only if the player's server is not connected to the Internet." line covers this, as in most cases servers under a proxy are under the same physical server/IP and therefore can/should run over localhost and don't need a proper connection to the internet. But I think that's too vague.
So maybe consider that this should be mentioned? After all is running a server under a proxy not that uncommon. Andre601 (talk) 22:58, 20 November 2025 (UTC)
Under "Keys", the description for management-server-tls-keystore includes "A server will not start is TLS is enabled and no keystore is provided." This is grammatically incorrect.
The property "pause-when-empty-seconds" should also have i its description that you can choose a negative number like -1 to disable it.