Repository navigation
0.26.18-beta - August 8, 2026
New
- Bots now play along with a login-wall plugin (nLogin, AuthMe, LoginSecurity, or anything else
built around a/register <password> <password>//login <password>command) instead of
sitting there unauthenticated forever. A bot generates its own password on first join, remembers
it (encrypted), and logs back in with it automatically on every future join, rename, or restart -
see/fpp authandauth.*inconfig.yml.
Improved
- License keys are no longer stored in plain text in
config.yml- pasting one in gets it encrypted
in place automatically on the next start/reload. Each activation locks that encrypted form to the
specific server it was activated on, so copyingconfig.yml(or just that one line) to another
server, or reusing an old encrypted value, doesn't work there - only the real key does, pasted in
fresh./fpp reloadalso now retries activation automatically if you fix a missing/bad key by
hand-editingconfig.yml, instead of requiring/fpp activateor a full restart. - Another pass at the "PacketEvents failed to inject into a channel" bot-kick some servers see from
anti-cheats/protocol plugins: re-verified the existing fix against PacketEvents' actual source
code and a live PacketEvents install, and couldn't find anything wrong with it - so if it still
happens to you, the console now dumps everything needed to pin down the real cause the moment it
occurs: how long the bot had been up, its actual connection state, every enabled plugin (flagging
likely suspects by name), and the full call stack of whatever actually triggered the kick. - If a bot ever disconnects without you running
/fpp despawn(another plugin or anti-cheat
kicking/removing it directly) more generally, the console now logs a warning naming the bot and
the real reason the instant it happens, instead of the bot silently disappearing with nothing in
the log to explain why.