Skip to content
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

It would be nice to have the feature to recognize the world in some mods. #1358

Open
ocformula opened this issue Jun 17, 2024 · 4 comments
Open

Comments

@ocformula
Copy link

ocformula commented Jun 17, 2024

I run two Paper servers and one Fabric server behind Velocity.
And if using VoxelMap, Xaero's Minimap, JourneyMap, etc. on the client, it's hard to use them properly because they overwrite the map every time moving the server.
But with the WorldNamePacket plugin installed in Velocity, VoxelMap or JourneyMap recognize the server.
However, Xaero's Minimap does not recognize the packet properly, mods like Distant Horizons do not properly support proxy servers.
It would be nice if Velocity standardized on this packet structure and made it easier for mod developers to follow.

@electronicboy
Copy link
Member

The overworld on server A and server B will be the exact same dimension name, as there is no other form of UUID attached, I'm not sure what the expectation from us here would be

@Aaron2550
Copy link

https://modrinth.com/plugin/modmapcompanion works with Xaero's Minimap btw

@minecraftchest1
Copy link

The overworld on server A and server B will be the exact same dimension name, as there is no other form of UUID attached, I'm not sure what the expectation from us here would be

Send an identifier for the backend server. Even the server/group name set in the config would probably work. Anything that would allow clients to know what map to render would be useful.

@electronicboy
Copy link
Member

if mod map makers had an agreed upon means of us sending this to them, we could adopt it; but, there exists 0 gain from us just sending random plugin messages to the client if there is no agreement on a channel name, format, etc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants