Elytrium / Elytrium/LimboReconnect
handling login events poorly 26.2
- Dominant language
- Java
- Stars
- 63
- Forks
- 26
- PR merge metrics
- No merged PRs in 30d
Description
[HorriblePlayerLoginEventHack] You have plugins listening to the PlayerLoginEvent, this will cause re-configuration APIs to be unavailable: [LuckPerms, GriefPrevention, ProtocolLib, WorldGuard]
[18:27:13 WARN]: Failed to update secure chat state for Laukage: 'Chat disabled due to missing profile public key. Please try reconnecting.'
[18:27:13 WARN]: Failed to update secure chat state for Laukage: 'Chat disabled due to missing profile public key. Please try reconnecting.'
>
Latest dev builds of LimboReconnect & LimboAPI
Velocity 4.1.0-SNAPSHOT (git-9eb338bd-b8)
[18:31:01 INFO]: Copyright 2018-2026 Velocity Contributors. Velocity is licensed under the terms of the GNU General Public License v3.
[18:31:09 INFO]: This server is running Purpur version 26.2-2609-HEAD@6726940 (2026-07-17T02:20:48Z) (Implementing API version 26.2.build.2609-stable)
* You are running the latest version
Previous: 26.2-15-0b4fed7 (MC: 26.2)
Contributor guide
No contributing guide indexed for this repository
Research direction
The report provides logs from LimboReconnect, LimboAPI, Velocity 4.1.0-SNAPSHOT, and Purpur 26.2, but names no source file or test. Start by reproducing the login-event behavior with the listed plugin and server versions, then trace the PlayerLoginEvent handling. Done means the affected plugins retain access to their re-configuration APIs and the secure-chat warnings no longer occur.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100