You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When executing mvtp and moving to a new world, the world is not loaded correctly and the user hits the terrain of the default world, which is not visible on the screen.
Also, when executing commands in this state, the client outputs "Chat disabled in client options" and the command cannot be executed.
If you then log out, you will get a timeout and not be able to log back in.
Similar problems occurred in PhantomWorlds, MyWorlds, and Universes.
Step to reproduce
1,Install multiverse-core
2,run server
3,Join the Game
4,Execute the command "/mv create test normal"
5,Execute the command "/mvtp test"
A little summary of what I need to do to run into issues with Multiverse Core.
So basically I'm using Multiverse-core to setup two extra worlds in my server and whenever I do /mvtp to any other world I get stuck at the spawn point and the chat gets disabled automatically, in the attached video im using vanilla client to rule out any client side issues. log attached below.
log -https://mclo.gs/FK2uEOA
Video - https://youtu.be/Z10XeOFMrgM
I have confirmed that ...
Arclight version
arclight-1.21-1.0.0-SNAPSHOT-b3349e9
OS & Java versions
OS:windows11 java:openjdk-22
Plugins and Mods
Description
When executing mvtp and moving to a new world, the world is not loaded correctly and the user hits the terrain of the default world, which is not visible on the screen.
Also, when executing commands in this state, the client outputs "Chat disabled in client options" and the command cannot be executed.
If you then log out, you will get a timeout and not be able to log back in.
Similar problems occurred in PhantomWorlds, MyWorlds, and Universes.
Step to reproduce
1,Install multiverse-core
2,run server
3,Join the Game
4,Execute the command "/mv create test normal"
5,Execute the command "/mvtp test"
Logs
latest.log
Server pack link (Optional)
No response
The text was updated successfully, but these errors were encountered: