I'm getting strange behavior on this. When I take an old test server from 1.4.7, upgrade the jar to 1.5, clear white-list.txt, and start the server, the bug still exists:
2013-03-18 18:29:45 [INFO] Starting minecraft server version 1.5
2013-03-18 18:29:45 [INFO] Loading properties
2013-03-18 18:29:45 [INFO] Default game type: SURVIVAL
2013-03-18 18:29:45 [INFO] Generating keypair
2013-03-18 18:29:45 [INFO] Starting Minecraft server on *:25565
2013-03-18 18:29:45 [INFO] Preparing level "world4"
2013-03-18 18:29:45 [INFO] Preparing start region for level 0
2013-03-18 18:29:46 [INFO] Preparing spawn area: 80%
2013-03-18 18:29:46 [INFO] Done (1.246s)! For help, type "help" or "?"
whitelist list
2013-03-18 18:29:56 [INFO] There are 0 (out of 2 seen) whitelisted players:
2013-03-18 18:29:56 [INFO]
whitelist add DMBuce
2013-03-18 18:30:01 [INFO] Added DMBuce to the whitelist
2013-03-18 18:30:08 [INFO] Disconnecting DMBuce [/127.0.0.1:32934]: You are not
white-listed on this server!
whitelist add dmbuce
2013-03-18 18:30:14 [INFO] Added dmbuce to the whitelist
2013-03-18 18:30:17 [INFO] DMBuce[/127.0.0.1:32940] logged in with entity id 331
at (173.5, 68.0, 68.5)
whitelist list
2013-03-18 18:30:32 [INFO] There are 2 (out of 2 seen) whitelisted players:
2013-03-18 18:30:32 [INFO] DMBuce and dmbuce
If I nuke the server directory completely and start fresh, the bug goes away, so it apparently only affects servers that existed before 1.5 for some reason.
If I nuke the server directory completely and start fresh, the bug goes away, so it apparently only affects servers that existed before 1.5 for some reason.
NVM about this, I had forgotten to re-enable whitelisting after nuking the server dir. The bug exists regardless of whether the server was upgraded from 1.4 or started fresh in 1.5.
2013-03-18 19:09:14 [INFO] Starting minecraft server version 1.5
2013-03-18 19:09:14 [INFO] Loading properties
2013-03-18 19:09:14 [WARNING] server.properties does not exist
2013-03-18 19:09:14 [INFO] Generating new properties file
2013-03-18 19:09:14 [INFO] Default game type: SURVIVAL
2013-03-18 19:09:14 [INFO] Generating keypair
2013-03-18 19:09:14 [INFO] Starting Minecraft server on *:25565
2013-03-18 19:09:14 [WARNING] Failed to load operators list: java.io.FileNotFoundException: ./ops.txt (No such file or directory)
2013-03-18 19:09:14 [WARNING] Failed to load white-list: java.io.FileNotFoundException: ./white-list.txt (No such file or directory)
2013-03-18 19:09:14 [INFO] Preparing level "world"
2013-03-18 19:09:15 [INFO] Preparing start region for level 0
2013-03-18 19:09:16 [INFO] Preparing spawn area: 8%
2013-03-18 19:09:17 [INFO] Preparing spawn area: 23%
2013-03-18 19:09:18 [INFO] Preparing spawn area: 38%
2013-03-18 19:09:19 [INFO] Preparing spawn area: 53%
2013-03-18 19:09:20 [INFO] Preparing spawn area: 69%
2013-03-18 19:09:21 [INFO] Preparing spawn area: 85%
2013-03-18 19:09:22 [INFO] Done (7.234s)! For help, type "help" or "?"
2013-03-18 19:09:23 [INFO] DMBuce[/127.0.0.1:33235] logged in with entity id 232 at (128.5, 68.0, 257.5)
2013-03-18 19:09:26 [INFO] DMBuce lost connection: disconnect.quitting
2013-03-18 19:09:29 [WARNING] Can't keep up! Did the system time change, or is the server overloaded?
whitelist on
2013-03-18 19:09:30 [INFO] Turned on the whitelist
2013-03-18 19:09:38 [INFO] Disconnecting DMBuce [/127.0.0.1:33242]: You are not white-listed on this server!
whitelist add DMBuce
2013-03-18 19:09:43 [INFO] Added DMBuce to the whitelist
2013-03-18 19:09:47 [INFO] Disconnecting DMBuce [/127.0.0.1:33248]: You are not white-listed on this server!
whitelist add dmbuce
2013-03-18 19:09:53 [INFO] Added dmbuce to the whitelist
2013-03-18 19:09:57 [INFO] DMBuce[/127.0.0.1:33254] logged in with entity id 3124 at (128.5, 68.0, 257.5)
I have been experiencing this on seed 7470478852514497265 in a world I created
in 1.18.
I did a few things to try and get a rough idea of how widespread the issue is on
different seeds, and how badly the issue affects the seed above in particular. (Edit: All testing was done on 1.19.)
I can't say I accomplished my goal but I am sharing the info on the offhand
chance that it's even slightly useful. Sorry in advance for the wall of text.
To get a rough idea of how widespread the issue is, I collected data as
follows:
Create a new Creative world
Find the nearest shipwreck with `/locate structure minecraft:shipwreck` and teleport to it
Swim over to the shipwreck and give myself a shipwreck map chest with `/give @s chest{BlockEntityTag:{LootTable:"minecraft:chests/shipwreck_map"}}`
Place the chest on the shipwreck and check its contents to see if a treasure map generates, noting the outcome as "chest failed" or "chest succeeded"
Try to find the buried treasure nearest to the shipwreck with `/locate structure minecraft:buried_treasure`, noting the outcome and distance to it
In cases where the chest failed to find a buried treasure and /locate
succeeded, I placed a second chest to see if the game would be able to
generate a treasure map after /locate found a buried treasure. But it never
did, so it seems that finding a buried treasure with /locate does not "help"
the game to generate treasure maps.
Given the 8th and 9th entries in the data above
(i.e. seeds -6749222809994879243 and 6711456787853967883),
it seems that shipwreck map chests start having difficulty generating treasure
maps at around 60 chunks (960 blocks) away.
It's interesting that a buried treasure 951 blocks away failed to generate
while one 956 blocks away succeeded, however this could be explained by the
fact that I was not careful about positioning. When running the /locate
command, I was always standing 1-4 blocks away from the chest, and when
placing the chest, I placed it in an arbitrary location in the shipwreck and
and arbitrary location in a chunk. I suppose it could also be explained if
/locate searches in a square area rather than a circular one.
Before collecting the data above, there was another 5 worlds I did this in where
I was just testing and didn't record anything.
Similar to the above data, there were several worlds where a chest failed to
generate a treasure map while /locate succeeded to find a buried treasure.
However, there was also one world where BOTH the chest and /locate failed to
find a buried treasure. Unfortunately, I did not keep the world and I do not
have the seed for it.
I wanted to do some testing with such a world, so I checked the world in which
I've been experiencing this issue since 1.18 (the one mentioned at the
beginning of this comment, seed 7470478852514497265). To the east of
spawn off the shore of a village is a shipwreck that fails to find a buried
treasure. I loaded a new creative world with the seed, checked the chest to
verify it failed to find a buried treasure, switched into spectator mode,
ran `/tp @s 119 46 -82` to position myself within the chest, and ran
`/locate structure minecraft:buried_treasure` to find a buried treasure.
Sure enough, the command reported 'Could not find a structure of type
"minecraft:buried_treasure" nearby'.
Before continuing my testing, I checked the save data. The world had grown to
156MB in size, which seems pretty large for a newly generated world.
Looking in the region folder, the /locate command had created a 7x7 grid of
region files from (-3,-4) to (3,2):
$ ls region/r.{-3..3}.{-4..2}.mca [same output as above]
Anyway, after entering spectator mode and positioning myself in the chest with
`/tp @s 119 46 -82`, I ran `/tp @s ~500 ~ ~` followed by
`/locate structure minecraft:buried_treasure`, which found buried treasure at
2057, -503 (1498 blocks away).
Then I positioned myself back at the chest (`/tp @s 119 46 -82`) and ran
`/tp @s ~-500 ~ ~` followed by `/locate structure minecraft:buried_treasure`
over and over until, at ~-2500 ~ ~, the /locate command found buried treasure
at -4791, 713 (1618 blocks away). Here is a screenshot with partial command
output: https://i.imgur.com/GbQQFVX.png
Then from that position of ~-2500 ~ ~ relative to the chest, I switched back
to creative, gave myself a shipwreck command chest, knocked out the block at
my head and two blocks above me, placed the chest directly above my head, and
opened it. It failed to find a buried treasure, so I continued teleporting in
increments of 500 blocks (`/tp @s ~-500 ~ ~`) and placing shipwreck map chests
in the same way until one of them successfully generated
a treasure map at ~-3500 ~ ~ .
However, after using the map to track down the location of the buried
treasure, it was a different one than the one that /locate found.
At the very least, it seems that on this map,
there is a line extending 4000 blocks or so in
length from roughly (-3379, -82) to (619, -82) where /locate can't find buried
treasure. And the situation is worse for shipwreck map chests, which have a
harder time finding buried treasure than /locate.
I am out of time to test and can't investigate further at the moment,
but hopefully this gives
at least a vague sense of how sparse buried treasure chests can be. Although
upon further reflection perhaps the info isn't that useful. For one, it could
be that, by teleporting in 500 block increments, I ended up "skipping" some
chests that /locate would have found. And also, much of the time I
was teleporting into solid terrain where a shipwreck probably wouldn't
generate anyway.
At any rate, in the past I have created a datapack that makes shipwrecks generate hearts of the sea instead of treasure maps in order to work around the issue on a checkerboard map that doesn't generate any beaches near oceans. In the future I am planning on making it simply generate a barrel full of buried treasure loot instead. The pack in its current form is here: https://github.com/dmbuce/bucepack#no-treasure-maps
At any rate, in the past I have created a datapack that makes shipwrecks generate hearts of the sea instead of treasure maps in order to work around the issue on a checkerboard map that doesn't generate any beaches near oceans. In the future I am planning on making it simply generate a barrel full of buried treasure loot instead.
A similar bug also occurs for non-default presets if you select the world type before adding the datapack in the Select Data Packs screen. AFAICT you must select a world type after adding a datapack for a custom preset to be used.
MC-4499
Just came here to report the same bug. Can confirm, /whitelist add YourUsername does not work as expected on 1.4.7.
I'm getting strange behavior on this. When I take an old test server from 1.4.7, upgrade the jar to 1.5, clear white-list.txt, and start the server, the bug still exists:
If I nuke the server directory completely and start fresh, the bug goes away, so it apparently only affects servers that existed before 1.5 for some reason.
NVM about this, I had forgotten to re-enable whitelisting after nuking the server dir. The bug exists regardless of whether the server was upgraded from 1.4 or started fresh in 1.5.
I have been experiencing this on seed 7470478852514497265 in a world I created
in 1.18.
I did a few things to try and get a rough idea of how widespread the issue is on
different seeds, and how badly the issue affects the seed above in particular. (Edit: All testing was done on 1.19.)
I can't say I accomplished my goal but I am sharing the info on the offhand
chance that it's even slightly useful. Sorry in advance for the wall of text.
To get a rough idea of how widespread the issue is, I collected data as
follows:
My results are below:
In cases where the chest failed to find a buried treasure and /locate
succeeded, I placed a second chest to see if the game would be able to
generate a treasure map after /locate found a buried treasure. But it never
did, so it seems that finding a buried treasure with /locate does not "help"
the game to generate treasure maps.
Given the 8th and 9th entries in the data above
(i.e. seeds -6749222809994879243 and 6711456787853967883),
it seems that shipwreck map chests start having difficulty generating treasure
maps at around 60 chunks (960 blocks) away.
It's interesting that a buried treasure 951 blocks away failed to generate
while one 956 blocks away succeeded, however this could be explained by the
fact that I was not careful about positioning. When running the /locate
command, I was always standing 1-4 blocks away from the chest, and when
placing the chest, I placed it in an arbitrary location in the shipwreck and
and arbitrary location in a chunk. I suppose it could also be explained if
/locate searches in a square area rather than a circular one.
Before collecting the data above, there was another 5 worlds I did this in where
I was just testing and didn't record anything.
Similar to the above data, there were several worlds where a chest failed to
generate a treasure map while /locate succeeded to find a buried treasure.
However, there was also one world where BOTH the chest and /locate failed to
find a buried treasure. Unfortunately, I did not keep the world and I do not
have the seed for it.
I wanted to do some testing with such a world, so I checked the world in which
I've been experiencing this issue since 1.18 (the one mentioned at the
beginning of this comment, seed 7470478852514497265). To the east of
spawn off the shore of a village is a shipwreck that fails to find a buried
treasure. I loaded a new creative world with the seed, checked the chest to
verify it failed to find a buried treasure, switched into spectator mode,
ran `/tp @s 119 46 -82` to position myself within the chest, and ran
`/locate structure minecraft:buried_treasure` to find a buried treasure.
Sure enough, the command reported 'Could not find a structure of type
"minecraft:buried_treasure" nearby'.
Before continuing my testing, I checked the save data. The world had grown to
156MB in size, which seems pretty large for a newly generated world.
Looking in the region folder, the /locate command had created a 7x7 grid of
region files from (-3,-4) to (3,2):
$ ls region/*.mca
region/r.0.0.mca region/r.-1.-2.mca region/r.2.1.mca region/r.3.-1.mca
region/r.0.-1.mca region/r.-1.2.mca region/r.-2.-2.mca region/r.3.1.mca
region/r.0.1.mca region/r.1.-2.mca region/r.-2.2.mca region/r.-3.-2.mca
region/r.0.-2.mca region/r.1.2.mca region/r.2.-2.mca region/r.-3.2.mca
region/r.0.2.mca region/r.-1.-3.mca region/r.2.2.mca region/r.3.-2.mca
region/r.0.-3.mca region/r.1.-3.mca region/r.-2.-3.mca region/r.3.2.mca
region/r.0.-4.mca region/r.-1.-4.mca region/r.2.-3.mca region/r.-3.-3.mca
region/r.-1.0.mca region/r.1.-4.mca region/r.-2.-4.mca region/r.3.-3.mca
region/r.1.0.mca region/r.-2.0.mca region/r.2.-4.mca region/r.-3.-4.mca
region/r.-1.-1.mca region/r.2.0.mca region/r.-3.0.mca region/r.3.-4.mca
region/r.-1.1.mca region/r.-2.-1.mca region/r.3.0.mca
region/r.1.-1.mca region/r.-2.1.mca region/r.-3.-1.mca
region/r.1.1.mca region/r.2.-1.mca region/r.-3.1.mca
$ ls region/r.{-3..3}.{-4..2}.mca
[same output as above]
Anyway, after entering spectator mode and positioning myself in the chest with
`/tp @s 119 46 -82`, I ran `/tp @s ~500 ~ ~` followed by
`/locate structure minecraft:buried_treasure`, which found buried treasure at
2057, -503 (1498 blocks away).
Then I positioned myself back at the chest (`/tp @s 119 46 -82`) and ran
`/tp @s ~-500 ~ ~` followed by `/locate structure minecraft:buried_treasure`
over and over until, at ~-2500 ~ ~, the /locate command found buried treasure
at -4791, 713 (1618 blocks away). Here is a screenshot with partial command
output: https://i.imgur.com/GbQQFVX.png
Then from that position of ~-2500 ~ ~ relative to the chest, I switched back
to creative, gave myself a shipwreck command chest, knocked out the block at
my head and two blocks above me, placed the chest directly above my head, and
opened it. It failed to find a buried treasure, so I continued teleporting in
increments of 500 blocks (`/tp @s ~-500 ~ ~`) and placing shipwreck map chests
in the same way until one of them successfully generated
a treasure map at ~-3500 ~ ~ .
However, after using the map to track down the location of the buried
treasure, it was a different one than the one that /locate found.
At the very least, it seems that on this map,
there is a line extending 4000 blocks or so in
length from roughly (-3379, -82) to (619, -82) where /locate can't find buried
treasure. And the situation is worse for shipwreck map chests, which have a
harder time finding buried treasure than /locate.
I am out of time to test and can't investigate further at the moment,
but hopefully this gives
at least a vague sense of how sparse buried treasure chests can be. Although
upon further reflection perhaps the info isn't that useful. For one, it could
be that, by teleporting in 500 block increments, I ended up "skipping" some
chests that /locate would have found. And also, much of the time I
was teleporting into solid terrain where a shipwreck probably wouldn't
generate anyway.
At any rate, in the past I have created a datapack that makes shipwrecks generate hearts of the sea instead of treasure maps in order to work around the issue on a checkerboard map that doesn't generate any beaches near oceans. In the future I am planning on making it simply generate a barrel full of buried treasure loot instead. The pack in its current form is here: https://github.com/dmbuce/bucepack#no-treasure-maps
I just released a new version of this datapack with the changes noted above as a workaround for this issue: https://github.com/DMBuce/bucepack#no-treasure-maps
A similar bug also occurs for non-default presets if you select the world type before adding the datapack in the Select Data Packs screen. AFAICT you must select a world type after adding a datapack for a custom preset to be used.