Although, I have the feeling that its something to-do with class names, and if it is, Bukkit didn’t have all that [net.minecraft.server.dedicated.DedicatedServer] stuff.
It just makes the log ugly and hard to read on smaller screens.
@Niall7459 you forget that sponge is a forge mod and no server distribution. Ofc sponge could change this using asm, but I see no reason why it would do that. Meaby forge will change it to:
No, you do not want to get rid of that. That is the actual class name doing the logging which is important for debugging. By just replacing it with “[Sponge]” you have no idea where that log originated and what it actually means. e,g, DedicatedServer’s “loading properties” means something completely different than MyMod’s “loading properties”. By removing the class name you lose all context.
Even if they could change it the above one would still be more useful, because it tells you the exact class where the entry came from, which is really useful for debugging (for the developer at least).
But you may have classes with the same name in different packages. It is something that someone would obviously try to avoid, but sometimes it still happens. Then you wouldn’t know which class a problem might be in.
Sorry if this is getting a little off-topic, but on that note, will this require all clients to be forge enabled as well or will Forge eventually allow non forge clients to connect? I’m not personally a fan of adding Forge mods to my servers since I used Spigot prior. Although, if it’s a forced thing to use Sponge, I may consider some forge mods to compliment the server.
It should probably be optional. Without the class name on the line, people trying to debug may have issues. So it wouldn’t be wise to remove it entirely, but rather just clean it up if configured to.
!