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 a player connects to a server (whether via logging in or via switching through bungee), the will get spawned into a random world (whether or not that world is currently loaded).
Ideally, I would like for players to be spawned in at their last known location. But having them spawn in at the spawn point would be fine as well (in fact, the latter is our temporary solution). The downside is that forcing players to run /spawn after logging in interferes with the cross-network teleporting (Rededit TP commands) because the forced /spawn prevents the player from getting to the player destination and only materializes at the server destination.
The text was updated successfully, but these errors were encountered:
I installed the latest RedEdit that you gave me with the increased debugging for teleporting. But I did //tpg 1 and was teleported to the "node4" server but ended up spawning in a player's build world. There was no extra messages except "[TP] Teleporting to node4"
When a player connects to a server (whether via logging in or via switching through bungee), the will get spawned into a random world (whether or not that world is currently loaded).
Ideally, I would like for players to be spawned in at their last known location. But having them spawn in at the spawn point would be fine as well (in fact, the latter is our temporary solution). The downside is that forcing players to run /spawn after logging in interferes with the cross-network teleporting (Rededit TP commands) because the forced /spawn prevents the player from getting to the player destination and only materializes at the server destination.
The text was updated successfully, but these errors were encountered: