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
Please read "To Reproduce" first.
After the player's first respawning, he or she will respawn at (0, 80, 0).
After the player's second respawning, he or she will respawn at (100, 80, 100).
Expected behaviour
After the player's first respawning, he or she will respawn at (100, 80, 100).
After the player's second respawning, he or she will respawn at (100, 80, 100).
To Reproduce
For instance, the world spawn is at (0, 80, 0), and the player's bed is at (100, 80, 100).
Suicide or get killed. When "You died!" appear on the screen, click on "Title screen", and click on "Title screen" again . For example, our player suicides at (200, 80, 200).
Reconnect to the server.
When "You died!" appear on the screen, click on "Respawn". Then login with the correct password.
Suicide again, and click on "Respawn".
Plugin list
Authme
Server Implementation
Standalone server (no proxy)
Database Implementation
SQLite
AuthMe Version
AuthMeReloaded v5.6.0-beta2 (build: 2453). This bug also exist in commit 9b93e0e
What behaviour is observed?
Please read "To Reproduce" first.
After the player's first respawning, he or she will respawn at (0, 80, 0).
After the player's second respawning, he or she will respawn at (100, 80, 100).
Expected behaviour
After the player's first respawning, he or she will respawn at (100, 80, 100).
After the player's second respawning, he or she will respawn at (100, 80, 100).
To Reproduce
For instance, the world spawn is at (0, 80, 0), and the player's bed is at (100, 80, 100).
Plugin list
Authme
Server Implementation
Standalone server (no proxy)
Database Implementation
SQLite
AuthMe Version
AuthMeReloaded v5.6.0-beta2 (build: 2453). This bug also exist in commit 9b93e0e
Error log (if applicable)
There is no error log in reproducing.
Configuration
https://gist.github.com/BlockyDeer/9c8cca0a5b51e15651e6383cf5cdaa4c
The text was updated successfully, but these errors were encountered: