Resetpos bug?

[JohOply]

Hi guys,

What behaviour is observed:

I want to reset last pos with command /authme resetpos , but when player come back it is always at the same location.

What behaviour is expected:

Player is not teleported to latest location and stay at spawn point after login (like purgelastpos in older versions)

Environment description

Bungeecord network and MySql

AuthMe build number:

Build 1877

Error Log:

N/A

Configuration:

https://pastebin.com/WY9u1yjb If I made something wrong, please tell me!

[sgdc3]

do you have caching enabled?

[JohOply]

Nop

# Enable the database caching system, should be disabled on bungeecord environments
# or when a website integration is being used.
caching: false

[ljacqu]

Nothing noticeably wrong with your config. If you look at a user's data with /authme debug db <name> do you see what you'd expect as the last location? Or does the spawn point show up there?

[JohOply]

It displays "Quit location: (0, 0, 0) in 'world'". When I login again, I am still at the last location.

I tried to restart server after leave the game and reset pos, but there is still the bug

[JohOply]

Do you know any way/command instead of purgelastpos to fix it or to teleport to the first login position?

[ljacqu]

Sorry for the late reply; I've been abroad. Allowing purgelastpos to reset the location to the (first) spawn point would be a pretty cool new feature. Given that this issue is about your players' last location not being saved, I'd like to invite you to create a separate issue for that feature (this simplifies our tracking).

Unfortunately, the config is no longer available. You said that it displayed "Quit location: (0, 0, 0)" so that's what's in the database... So why isn't it being set if your config was right? Would you mind posting your config.yml again and I'll take it over and I'll try to reproduce it locally. Sorry for the trouble :)

[JohOply]

New upload https://pastebin.com/mKsPUJUi

[ljacqu]

Thanks for the config. What I've determined is that AuthMe doesn't perform any teleports on join, yet I can confirm that the user ends up at the old place anyway. This must be the server itself remembering the player's last location.

Therefore, if you want to hide the last location before logging in, I suggest you enabled the following setting:

        # Should not logged in players be teleported to the spawn?
        # After the authentication they will be teleported back to
        # their normal position.
        teleportUnAuthedToSpawn: true

[JohOply]

Nice news! :D

Thank you for your suggest. I will release a Premium server with Authme, so I will not enable "TeleportUnAutheToSpawn" because I think usurpation risk is very low. What do you think about?

Also, do you think it is safe to use a devbuild on a released server?

[sgdc3]

@JohOply Yeah it should be safe atm ;)

[sgdc3]

About the teleport unauthed to spawn thing, it depends, personally i don't use it.

[JohOply]

Hi! I comeback later, but I'm not sure to understood your explainations... Today, in latest devbuild, there is still the same bug (tested in 1.13.2). It was never fixed. The bug appear even if teleportUnAuthedToSpawn is set to true or false

Some years ago, "/authme purgelastpos" could be used to reset old position then, de facto, teleport player to the spawn (because there is not any location linked with its account). That's the point and that's what I want to do.

Do you have any idea to help me (if I made something wrong or misunderstanding something), or could you fix it please?

Thank you in advance, a lot :)