ConsoleColor
[ > Features | Commands | Configuration | Permissions ]
- Color console log entries
- Change console log entry format (timestamp, position, etc.)
- Does not change server.log file output, only console display
Do you spend a lot of time in your console? Would you like to enjoy reading through your console entries and not having to decipher a monochrome storm of characters?
Go from this:
To this:
Troubleshooting
If you are having trouble determining why something isn't working, set log-level: ALL
in the /plugins/ConsoleColor/config.yml file and restart your server. Wait for the problem to reoccur then paste the server.log file to somewhere like http://gist.github.com and then create a ticket with a link to the paste.
Please up date the plugin to 1.7.10 or 1.8 please!
Update the plugin to 1.7.2
@EdGruberman
Thanks for the lead on log4j2. :-)
I was able to get something similar to work (I'm running Spigot), though I don't know anything about XML so maybe someone else can tidy this up a bit. Following is a compilation of a couple different solutions I found online. First, you have to modify your startup line by adding:
So, something like:
Here is the log4j2.xml file (you place this in the same folder as your craftbukkit.jar or spigot.jar) Be sure to scroll down and get all of it:
Using this gives you the following:
If anyone can clean this up or simplify it, please do. I just started playing with this so if I improve it, I'll post again. I wasn't able to add the "SEVERE" level to it, nor figure out how to get it to only highlight the level rather than the whole line. Hope someone finds this useful.
any chance of an update just to allow 1.7 compatibility? getting this on boot
[05:17:01 ERROR]: [ConsoleColor] Unsupported CraftBukkit version git-Spigot-1299 (MC: 1.7.2); java.lang.ClassNotFoun dException: edgruberman.bukkit.consolecolor.craftbukkit.CraftBukkit_v1_7_R1
There are major changes in Minecraft's (and CraftBukkit's accordingly) logging mechanism. With the use of log4j you can control a lot of the formatting yourself now with an xml config file by default without a plugin. I need to find time to learn exactly what is possible with that configuration file first before I put too much time into this plugin unnecessarily.
My impression is we are able to at least control date and level names both with format and color. I've also run across ideas of replacing occurrences of text with other characters. It may be possible to replace Minecraft color codes with ASCII equivalents just for the console output with that log4j xml config file. If so, this plugin is no longer necessary.
If any of you that have used this plugin find some time before I do, please share with the rest of us!
@EdGruberman:
Please update! I love this plugin :(
Update this plugin please! :S
Please update :)
Will this be updated?
@EdGruberman
don`t use Libigot. Believe me.
@craftik7
I'm not sure I understand your recommendation entirely. Compiling only against Libigot would restrict this plugin to work with only Libigot servers (and 1.3.2 and earlier CraftBukkit servers actually since those were before the package versioning change). When someone were to attempt to use this plugin on a regular CraftBukkit server they would receive class not found exceptions since this plugin would only reference a non-versioned org.bukkit.craftbukkit package and CraftBukkit servers only have that package suffixed with a version now.
I checked all your plugins and I could not find one that reference any org.bukkit.craftbukkit packages. So, if you are compiling against Libigot it shouldn't matter for your plugins since you are using only Bukkit API references. You could compile your plugins against the Bukkit API and be fine also. There is no reason for you to rely on Libigot.
@EdGruberman
Then use Libigot to compile it. With Libigot, it does not broke and we can use it on every Minecraft version. Thanks.
How to do it:
@Squawkers13
I just uploaded 1.7.0: http://dev.bukkit.org/bukkit-plugins/consolecolor/files/10-console-color-1-7-0/
It breaks because this plugin is dependent on the CraftBukkit server internals (not just the Bukkit API). The Bukkit Team changes the CraftBukkit internal class names whenever significant changes occur to force plugin developers to reassess if their plugin is still safe to use.
This is a safety mechanism to prevent plugins corrupting servers or otherwise causing unforeseen complications and unsupported situations.
I have a long term goal of convincing the Bukkit Team to integrate support of this type of a plugin directly into the Bukkit API which would allow this plugin to work without plugin updates, but so far it's been slow going in that effort.
Why does it break with every Minecraft update? (1.6.2!)
@Squawkers13 No. But I just uploaded 1.6.0. It's still awaiting official BukkitDev approval, but you can access it here if you trust me: http://dev.bukkit.org/bukkit-plugins/consolecolor/files/9-console-color-1-6-0/
@EdGruberman
Does 1.5.0 work with 1.6.1?
@Marium0505
ConsoleColor 1.5.0 does work with CraftBukkit 1.5.2.
I doubt a typical hosted environment would support this. This plugin formats the console output (stderr/stdout) not the server.log file. Even if the game host redirects console output to your admin interface, it probably won't translate the ANSI color codes as proper HTML color codes. (Assuming your admin interface is web based.)
Does this work on hosted server? (server not hosted on the computer)
And does this work on 1.5.2?
@LegndPowerdNube
Somehow I missed your comment originally.. But I'm assuming you made your comment just a bit before ConsoleColor 1.4.0 was released which works with 1.5.1.
This is broken for 1.5.1!