Solved "Don't nag on old event yet" warn

shampoo got into the eyes

shampoo got into the eyes

New member
Feb 24, 2022
3
0
1
Hello. I am running a server on a PaperMC core and have faced with such a problem. Some plugins send these warnings to the console at startup:
[Server thread/WARN]: [[I]Plugin[/I]] "[I]Plugin[/I]" has registered a listener for org.bukkit.event.player.AsyncPlayerChatEvent on method "public void di.dilogin.minecraft.event.UserBlockEvents.onPlayerChat(org.bukkit.event.player.AsyncPlayerChatEvent)", but the event is Deprecated. "Don't nag on old event yet"; please notify the authors [[I]AuthorName[/I]]. org.bukkit.plugin.AuthorNagException: null
Here is the full text of the error, using the Chatty plugin as an example:
YAML: 
[00:54:28] [Server thread/INFO]: [Chatty] Enabling Chatty v2.19.5
[00:54:28] [Server thread/INFO]: [PlaceholderAPI] Successfully registered expansion: chatty [2.19.5]
[00:54:28] [Server thread/INFO]: [Chatty] PlaceholderAPI has successful hooked.
[00:54:28] [Server thread/WARN]: [Chatty] "Chatty v2.19.5" has registered a listener for org.bukkit.event.player.AsyncPlayerChatEvent on method "public void ru.mrbrikster.chatty.chat.ChatListener.onSpyMessage(org.bukkit.event.player.AsyncPlayerChatEvent)", but the event is Deprecated. "Don't nag on old event yet"; please notify the authors [MrBrikster].
org.bukkit.plugin.AuthorNagException: null
    at org.bukkit.plugin.java.JavaPluginLoader.createRegisteredListeners(JavaPluginLoader.java:331) ~[paper-api-1.18.1-R0.1-SNAPSHOT.jar:?]
    at org.bukkit.plugin.SimplePluginManager.registerEvents(SimplePluginManager.java:661) ~[paper-api-1.18.1-R0.1-SNAPSHOT.jar:?]
    at ru.mrbrikster.chatty.Chatty.onEnable(Chatty.java:132) ~[Chatty.jar:?]
    at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:264) ~[paper-api-1.18.1-R0.1-SNAPSHOT.jar:?]
    at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:370) ~[paper-api-1.18.1-R0.1-SNAPSHOT.jar:?]
    at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:501) ~[paper-api-1.18.1-R0.1-SNAPSHOT.jar:?]
    at org.bukkit.craftbukkit.v1_18_R1.CraftServer.enablePlugin(CraftServer.java:561) ~[paper-1.18.1.jar:git-Paper-207]
    at org.bukkit.craftbukkit.v1_18_R1.CraftServer.enablePlugins(CraftServer.java:475) ~[paper-1.18.1.jar:git-Paper-207]
    at net.minecraft.server.MinecraftServer.loadWorld0(MinecraftServer.java:727) ~[paper-1.18.1.jar:git-Paper-207]
    at net.minecraft.server.MinecraftServer.loadLevel(MinecraftServer.java:503) ~[paper-1.18.1.jar:git-Paper-207]
    at net.minecraft.server.dedicated.DedicatedServer.initServer(DedicatedServer.java:313) ~[paper-1.18.1.jar:git-Paper-207]
    at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1202) ~[paper-1.18.1.jar:git-Paper-207]
    at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:317) ~[paper-1.18.1.jar:git-Paper-207]
    at java.lang.Thread.run(Thread.java:833) ~[?:?]
[00:54:28] [Server thread/WARN]: [Chatty] "Chatty v2.19.5" has registered a listener for org.bukkit.event.player.AsyncPlayerChatEvent on method "public void ru.mrbrikster.chatty.chat.ChatListener.onChatMonitor(org.bukkit.event.player.AsyncPlayerChatEvent)", but the event is Deprecated. "Don't nag on old event yet"; please notify the authors [MrBrikster].
org.bukkit.plugin.AuthorNagException: null
    at org.bukkit.plugin.java.JavaPluginLoader.createRegisteredListeners(JavaPluginLoader.java:331) ~[paper-api-1.18.1-R0.1-SNAPSHOT.jar:?]
    at org.bukkit.plugin.SimplePluginManager.registerEvents(SimplePluginManager.java:661) ~[paper-api-1.18.1-R0.1-SNAPSHOT.jar:?]
    at ru.mrbrikster.chatty.Chatty.onEnable(Chatty.java:132) ~[Chatty.jar:?]
    at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:264) ~[paper-api-1.18.1-R0.1-SNAPSHOT.jar:?]
    at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:370) ~[paper-api-1.18.1-R0.1-SNAPSHOT.jar:?]
    at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:501) ~[paper-api-1.18.1-R0.1-SNAPSHOT.jar:?]
    at org.bukkit.craftbukkit.v1_18_R1.CraftServer.enablePlugin(CraftServer.java:561) ~[paper-1.18.1.jar:git-Paper-207]
    at org.bukkit.craftbukkit.v1_18_R1.CraftServer.enablePlugins(CraftServer.java:475) ~[paper-1.18.1.jar:git-Paper-207]
    at net.minecraft.server.MinecraftServer.loadWorld0(MinecraftServer.java:727) ~[paper-1.18.1.jar:git-Paper-207]
    at net.minecraft.server.MinecraftServer.loadLevel(MinecraftServer.java:503) ~[paper-1.18.1.jar:git-Paper-207]
    at net.minecraft.server.dedicated.DedicatedServer.initServer(DedicatedServer.java:313) ~[paper-1.18.1.jar:git-Paper-207]
    at net.minecraft.server.MinecraftServer.runServer(MinecraftServer.java:1202) ~[paper-1.18.1.jar:git-Paper-207]
    at net.minecraft.server.MinecraftServer.lambda$spin$0(MinecraftServer.java:317) ~[paper-1.18.1.jar:git-Paper-207]
    at java.lang.Thread.run(Thread.java:833) ~[?:?]

A list of plugins that have sent me such warnings:
DICore v2.0.4 (GitHub | SpigotMC)
DILogin v3.0.6 (GitHub | SpigotMC)
Chatty v2.19.5 (GitHub | SpigotMC)
DynMap v3.3.2-696 (GitHub | SpigotMC)
WorldsColor v1.0.2 (SpigotMC)
Plan v5.4 build 1583 (GitHub | SpigotMC)

List of plugins installed on the server:
Plugins (21): BetterSleeping4, Chatty, CoreProtect, DICore, DILogin, DiscordSRV, dynmap, EasyWhitelist*, F3Name, LuckPerms, MOTD, Orebfuscator, PL-Hide, PlaceholderAPI, Plan, PlasmoVoice, ProtocolLib, SFRP*, SimpleLay, SkinsRestorer, WorldsColor

What can I or plugin developers do to fix the bug? Or is it a PaperMC problem?
 
Logs
https://paste.gg/p/anonymous/65b8022d661a43edb3814dadab298550
Timings
https://timings.aikar.co/?id=bcc0ca9ac56e47faa46c5f7082d62dcb
Version Output
This server is running Paper version git-Paper-207 (MC: 1.18.1) (Implementing API version 1.18.1-R0.1-SNAPSHOT) (Git: b757019)
You are 7 version(s) behind
Download the new version at: https://papermc.io/downloads
Previous version: git-Purpur-1562 (MC: 1.18.1)
Solution
electronicboy
bukkit.yml deprecated-verbose: true

You have enabled an option which makes all deprecated loggers warn about the fact that they're deprecated, turn that off if you don't want that
Sort by date Sort by votes
electronicboy

electronicboy

Administrator
Staff member
Dec 11, 2021
225
10
38
28
basically, paper is moving away (slowly) from the "deprecated 7 years ago text format", and so for now, they're fine, but, eventually, in probably a good time away, they'll need to move towards the modern events inside of paper
 
Upvote 0 Downvote
You must log in or register to reply here.