#Uploading a world with non-public spawn or minigame “use own bricks” should warn the user

3 messages · Page 1 of 1 (latest)

hexed blade
#

Lots of people don’t realize that a spawn point needs to be public or their default minigame needs to be “use all bricks” for spawn points to function. Uploading a save with a non-public spawn point (if no minigame) or “use owned bricks” (if default minigame) should warn the user and offer to fix it.
Probably not a long-term solution but people just don’t realize it’s an issue because it work when you load it as the owner.

ocean quarry
#

ah I was about to submit this as a bug but ig I'll just bump this instead

here's the bug report I wrote tho

When I open any downloaded world that has spawnpoints, I do not spawn at the spawnpoint unless the world has a default minigame.

Many people making worlds expect people to be able to spawn from these spawnpoints, but in practice only the world creator can spawn from their spawnpoints, not other players.
(Even though people that download the worlds can modify any bricks in the world, or at least admins/singeplayer players can.)

Expected behavior: All players in a server should be able to spawn at spawnpoints owned by the creator of a world that has been loaded in to the server.
ocean quarry