Last active 4 days ago
Perhaps you could add a scoreboard tag for when players log in within certain radius (defined in server.properties) of world spawn, then make sure someone has that tag before applying the new player stuff to them. This would work unless someone happened to log out at that specific spot and then change their name.
@CraftyMyner You should try to fix this! :)
Here's a way you could do it:
You could add a filter to the server panel to detect messages (regex form):
\w+ [(]formerly known as \w+[)] joined the game. I'm not sure yet how to use regex capturing groups, but you probably know how to do that. Then you can code it to run an automated command that will disable the server tagging the specified player as new via /scoreboard or something.
The current world format doesn't allow for that many blocks - that's why not too many blocks are being introduced. However, by 1.14, they're rewriting the blockstates code along with some other save format stuff to make it compatible with all the new blocks. There's a post somewhere on Reddit about it.
World save format is changing in 1.13 update I believe, or it may be 1.14.
You should set up a forum bot account that auto posts the results when they're declared
Who was it that ran /kill @a?
This thread should be stickied
Hi, I was wondering why Crafty and staff decided to allow the nether roof. A lot of chunk loading lag can be caused by it, so that's why I was wondering.