Two Minecraft Bedrock Server Questions: server.properties & seed generation
I created an Ubuntu server via Linode. I created a Minecraft Bedrock server. Connected and generated a world. I want to use a particular seed. I changed the seed value to the desired seed in the server.properties file; however, when I login it continues with the old seed. I've read multiple tutorials about changing the 'world' file to a new name and then regenerating the world and it would generate a world with the seed. I could not find a 'world' file to rename. I find a 'world' directory with ". .." files in them which were both blank. I decided to rename 'server.properties' expecting it would generate a new seed when I restarted server. This worked, but did not generate the desired seed I had put in the original server.properties file.
I then had both a 'server.properties' file, and a file i had named 'server.properties.1' …. expecting server.properties to generate when i re-started the server, i deleted both server.properties files and re-started the server. Thus have I have two issues:
- How do I get my server.properties file to generate or come back without deleting the entire server and reinstalling the minecraft server files.
- Assuming I can do that, is there any tutorial on generating a desire seed via the linux terminal for a bedrock minecraft server. i can only find Windows, or GUI based tutorials, which doesn't help because I'm on a cloud server running Ubuntu.
I'm also a novice at linux. This was part of a project for me to learn more about servers and using linux system. Any help would be greatly appreciated!!
I found Minecraft to be a great project for people who are new to Linux! Bedrock servers using LinuxGSM are pretty easy to maintain, but there's definitely enough to play with to be a challenge as well.
worlds directory should include your database and level information for your Minecraft world, but this isn't generated until the world itself is generated. This is the most likely reason as to why your directory was empty. Regarding the seed value, you should be able to change the
level-seed value in server.properties to change your seed. This may require regenerating the server to pick up the new seed, so you were on the right track there.
How do I get my server.properties file to generate or come back without deleting the entire server and reinstalling the minecraft server files.
I don't know that this is possible without uninstalling and reinstalling Minecraft, though you wouldn't need to delete the whole server in order to do so. You can try to recreate the file by creating a new file within the
/home/mcbserver/serverfiles directory (where
mcbserver is your Minecraft user; it's commonly
mcbserver) with the same permissions, named
server.properties. The file will need permissions of
644, or read-write for the owner, read for the group, and read for all other users. I've included the content of the
server.properties file below my response, and this output is essentially the default values for that file.
If you'd rather uninstall and reinstall, you can use your system's package manager to do so.
Assuming I can do that, is there any tutorial on generating a desire seed via the linux terminal for a bedrock minecraft server. i can only find Windows, or GUI based tutorials, which doesn't help because I'm on a cloud server running Ubuntu.
To change your seed value, you need to edit the
server.properties file and fill in the
level-seed value. You would need to restart the Minecraft process after changing that value in order for it to go into effect. I found this thread to be helpful in doing so.
server-name=LinuxGSM # Used as the server name # Allowed values: Any string gamemode=survival # Sets the game mode for new players. # Allowed values: "survival", "creative", or "adventure" difficulty=normal # Sets the difficulty of the world. # Allowed values: "peaceful", "easy", "normal", or "hard" allow-cheats=false # If true then cheats like commands can be used. # Allowed values: "true" or "false" max-players=25 # The maximum number of players that can play on the server. # Allowed values: Any positive integer online-mode=true # If true then all connected players must be authenticated to Xbox Live. # Clients connecting to remote (non-LAN) servers will always require Xbox Live authentication regardless of this setting. # If the server accepts connections from the Internet, then it's highly recommended to enable online-mode. # Allowed values: "true" or "false" white-list=false # If true then all connected players must be listed in the separate whitelist.json file. # Allowed values: "true" or "false" server-port=19132 # Which IPv4 port the server should listen to. # Allowed values: Integers in the range [1, 65535] server-portv6=19133 # Which IPv6 port the server should listen to. # Allowed values: Integers in the range [1, 65535] view-distance=32 # The maximum allowed view distance in number of chunks. # Allowed values: Any positive integer. tick-distance=4 # The world will be ticked this many chunks away from any player. # Allowed values: Integers in the range [4, 12] player-idle-timeout=0 # After a player has idled for this many minutes they will be kicked. If set to 0 then players can idle indefinitely. # Allowed values: Any non-negative integer. max-threads=8 # Maximum number of threads the server will try to use. If set to 0 or removed then it will use as many as possible. # Allowed values: Any positive integer. level-name=Bedrock level # Allowed values: Any string level-seed= # Use to randomize the world # Allowed values: Any string default-player-permission-level=member # Permission level for new players joining for the first time. # Allowed values: "visitor", "member", "operator" texturepack-required=false # Force clients to use texture packs in the current world # Allowed values: "true" or "false" content-log-file-enabled=false # Enables logging content errors to a file # Allowed values: "true" or "false" compression-threshold=1 # Determines the smallest size of raw network payload to compress # Allowed values: 0-65535 server-authoritative-movement=true # Enables server authoritative movement. If true, the server will replay local user input on # the server and send down corrections when the client's position doesn't match the server's. # Corrections will only happen if correct-player-movement is set to true. player-movement-score-threshold=20 # The number of incongruent time intervals needed before abnormal behavior is reported. # Disabled by server-authoritative-movement. player-movement-distance-threshold=0.3 # The difference between server and client positions that needs to be exceeded before abnormal behavior is detected. # Disabled by server-authoritative-movement. player-movement-duration-threshold-in-ms=500 # The duration of time the server and client positions can be out of sync (as defined by player-movement-distance-threshold) # before the abnormal movement score is incremented. This value is defined in milliseconds. # Disabled by server-authoritative-movement. correct-player-movement=false # If true, the client position will get corrected to the server position if the movement score exceeds the threshold.