Repository navigation
Consider switching to ComponentLogger #187
Description
With that writing log messages would be more modern and easier. CLI Support would probably also be better (might need some refinements).
Using Java Logger directly is outdated and not recommended especially because Minecraft uses Log4J internally.
If we want component support we can also use the Adventure ComponentLogger (expands SLF4Logger)
We might also want to use the plugin logger where possible instead of creating our own e.g https://jd.papermc.io/paper/26.1.2/org/bukkit/plugin/Plugin.html#getSLF4JLogger()
Activity
OakLoaf commentedon Aug 13, 2026
I'd be happy for this migration, but it's not something that would be top priority for me right now
Zoriot commentedon Aug 14, 2026
Okay i can probably pr it. Do you prefer ComponentLogger or plain SLF4Logger? Creating own or using the Plugin's where possible?
Are you also open to add debug logging? Should i make a separate pr for that or do it in the same one?
OakLoaf commentedon Aug 15, 2026
Let's use ComponentLogger, I reckon we depends on adventure in the API for use in all platforms and for those that don't natively support it then we can package it.
Let's do debug logs in a separate PR just because that'll take more time to review :)
Zoriot commentedon Aug 16, 2026
Will work on it now, hope this does also fixes the issue which accor on cli and paper that some logs get's not printed right away and only when the plugin stops.
feat: ✨ Switch to Adventure ComponentLogger
feat: ✨ Switch to Adventure ComponentLogger
[-]Consider switching to SLF4JLogger[/-][+]Consider switching to ComponentLogger[/+]