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
Player go to spawn all time #565
Comments
This is not Multiverse. There is a new option in 'bukkit.yml' called 'use-exact-login-location'. Set this to true and you should be fine =) |
I am having this issue too and I tried to edit bukkit.yml and turn that to true but they are still spawning at the mv spawn every time they log in. multiverse.* stops this for me as well but I need a better fix then that obviously... |
"Since Minecraft added the feature of pushing entities out whenever they are stuck inside a block, players have often found themselves above the location they logged out of when logging back in (especially if they were in a cave). This new bukkit.yml setting allows servers to disable or enable this behaviour. If true, we will bypass Vanilla's behaviour of checking for collisions and moving the player if needed when they login. If false, we will continue to follow Vanilla's behaviour and move players that 'collide' with objects when they login." From what I am reading here, this should have nothing to do with players spawning at the mv spawn vice where they logged out. So this must be a mv bug... |
I hope you guys are on the latest build but without the required info, i'm tempted to close this issue... I've just started running my actual server again and have had no problems with the latest MV, Dynmap and CB-Dev EDIT: And Privileges :D |
This turned out to be a problem with permissions for me. It kept eating my permissions file due to a really small error and so the mv portion of that was not working. Sorry for wasting you time but thank you for your assistance. |
'use-exact-login-location'.= true change nothing. As said iliveforgod347, that only one way to solve it is to put multiverse.* node for all user, and it's very good idea you can imagine it ! Problem not solve. Perhaps i mistaking but what node my user need to have to don't appear to spawn point ? |
ProblemWhen my player logon they always appaear to spawn. Link generated from /mv version -phttp://pastie.org/private/2boylqznagdviykafmj1ga Craftbukkit 1.2.3 R0.3-2063 Startup log (Code formatted with 4 spaces)Any other relevant files:Here is my permissions file for PermissionsBukkit: ONLY op can login spawn at exact logoff position. |
I recently began experiencing this problem, too. Discovered I was missing the access permission for my players which was causing a FORCED multiverse teleport to the default world's spawn. My guess this was a bug fix to players getting access to worlds they lost permission to when the were offline. Make sure your players have this permission for Your_World_Here
or for any and all worlds
|
having 2.4-b527 of multiverse-core and added multiverse.acces.The_Name_of_theworld: true in my permissions for the user group but my users get the message that they arn't allowed to the world and login at spawn, indstead of where they logged off. |
@nosnensius If your users are getting that message then they do not have the |
Old issue, if still occurring, please open a new ticket: https://github.com/Multiverse/Multiverse-Core/wiki/Submitting-a-Bug |
hey peeps. this aint multiverse. i dont got no multiverse and i got da same problem. and yes i did da bukkit.yml thing. it just aint working |
i do have multiworld though |
Hello
When my player logon they always appaear to spawn.
But i have that only for my main world, if my player are in another world, the server remember the last position before logoff.
The main world and others world have the same configuration in worlds.yml.
If i put multiverse.* node permission for my player, server remember the last position before logoff for my main world !
I have the multiverse V 2.4 b 521 and craftbukkit : 1.1 R6 b2034.
The text was updated successfully, but these errors were encountered: