-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Feature Request]: Worldborder Visualisation #790
Comments
How are you feeling defining the world border? I am curious since mapping is all done clientside, vanilla border is easy todo since it just pure numbers I can hardcode, but if the client does not know. It would need a server sided logic to tell the client to stop mapping and display a red area. If it is a mod or plugin, that would make it even more difficult as I could not automatically detect the border. |
For me personally I'm just using the vanilla |
Doesn't the server send the worldborder data to the client? I mean how would the client be able to show the worldborder if it didn't knew what it was? But yeah for starters just the vanilla worldborder would be a great start |
I have no idea honestly, I haven't looked into it yet. |
Describe the new feature.
On servers with smaller world borders than default, journeymap continues to map outside of the world border, this means that you end up with a fuzzy border depending on how close you get to the border, making it difficult to tell where the actual border is.
The feature I'm requesting is either a visualisation of the world border on the map (such as a red box) or the ability to hide content that is outside of the world border, so your map could be "complete" by exploring everything in the world border.
I've uploaded a picture of a map for a server I'm working on where my map contains content that is inaccessible to the player, but still shown on the map due to it not hiding outside of the world border. It's scaled down to fit within the filesize limit, but still gets my point across I think.
Images
The text was updated successfully, but these errors were encountered: