What happened?
When using the "Dialog-based login and registration" feature of AuthMe 6.0.0-R1 on Paper 26.1, FastLogin is unable to correctly auto-login players.
This occurs on the backend server.
[19:37:03 INFO]: [FastLogin] Setups using Minecraft proxies will start delayed when the command from the proxy is received
[19:37:04 INFO]: [FastLogin] Player info LOGIN command for Neko110923 from proxy
[19:37:04 INFO]: [FastLogin] Delaying force login until join event fired?: true
[19:37:04 INFO]: [FastLogin] Logging player Neko110923 in
[19:37:04 WARN]: [FastLogin] Player CraftPlayer{name=Neko110923, uuid=6fee67b8-4e11-469a-95e2-b689145bf8a0} is already authenticated. Cancelling force login.
It seems that AuthMe's dialog is taking precedence over FastLogin, requesting login first.
Versions: Minecraft 26.1.2
Server version: Paper 26.1.2 build 51
FastLogin version: v1.12-SNAPSHOT-65a379c
Proxy server: Velocity
Steps to reproduce
No response
Plugin list
No response
Configuration file
No response
Server log
No response
Plugin version
v1.12-SNAPSHOT-65a379c
Platform
Velocity
Relevance
What happened?
When using the "Dialog-based login and registration" feature of AuthMe 6.0.0-R1 on Paper 26.1, FastLogin is unable to correctly auto-login players.
This occurs on the backend server.
It seems that AuthMe's dialog is taking precedence over FastLogin, requesting login first.
Versions: Minecraft 26.1.2
Server version: Paper 26.1.2 build 51
FastLogin version: v1.12-SNAPSHOT-65a379c
Proxy server: Velocity
Steps to reproduce
No response
Plugin list
No response
Configuration file
No response
Server log
No response
Plugin version
v1.12-SNAPSHOT-65a379c
Platform
Velocity
Relevance
I tried the latest build
(build refers to development builds not necessary a release version; i.e. v1.10 is out of date)
I checked for existing tickets -
If there are, please vote them with a thumbs reaction and not create new ones