LogEx
A powerful tool to collect informations
LogEx is a continuation of pokepal101's Log plugin, you can find the original BukkitDev page here. A big thanks to pokepal101 for this awesome plugin and for the permission to publish my version ;)
As the original Log, it collects modifications such as breaking or placing of blocks. But that isn't everything! Now it remembers more modifications like emtying or filling of water and lava buckets (usefull to fight against players who want to live under the sea). LogEx also writes down every login from each player, it remembers the date and the IP. I implemented also a feature which logs informations about picking up an item. Because of the risk that the logfile could be to expensive, I disabled it by default. LogEx also collects mobs spawned by spawneggs and chat messages.
Features
- Block modification logging and viewing
- Bucket (water and lava) logging and viewing
- WorldEdit logging (At the moment only set and only for cuboid regions)
- Chat logging and viewing
- Command logging and viewing
- Death logging and viewing
- Gamemode switch logging and viewing
- Login logging and viewing
- Spawnegg logging and viewing
- World switch logging
- Optional multithreading for Events (1.5+) and Commands to not charge the servers performance
- Efficient database storage system
- Enderchest content viewing via command (1.5+)
- Inventory content viewing via command (1.5+)
- Autocleaner to clean up databases from old entries
- Changelog viewing in-game
- Statistics via command
- Superpickaxe (WorldEdit) logging (1.5+)
- The list is expanding more and more!
What makes LogEx special? Well, gives you the possibility to stay up to date what's going on on your server, even if you're offline.LogEx is always getting even more stable, fluid and better. One more thing that makes LogEx delightful: It won't make an effort to log modifications done by the nature like creeper explosions or enderman griefing, which makes the databases even lighter.
This, my friend, is THE MOST AWESOME THING IN THE WORLD!!!!!
Thank you for this awesome plugin!
But... after using /reload command it somehow increases CPU load, a few reloads can kill server in my case (yeah, i've checked server without other plugins too).
And sorry about my poor english =)
Happy new year everyone!!
This plugin is great! I want to correspond to the version 1.4.6.
Excellent! I would love to co-develop this plugin with you!
This plugin was the simplest yet useful plugin out of all plugins.
@kremi151
Good im glad to hear that I really love this plugin and thats what my server is really hoping for to be in the 1.6 update
Really GREAT !!!!!
I like the way to check blocks history ! Perfect to know who grieffed without having to deal with huge log files !
The only thing missing is to trace TNT grieffers...
Maybe in a first time if we could do something like
/log block <id> <player>
it would become easier to check by player
another great thing would be the ability to write a log to a file on demand ( >file:filename)
ex: /log block 47 Player >file:PlayerTnt.txt
and so it would write a text file called PlayerTnt.txt logging each uses of block 47 for Player
Do you thing you could work on those kind of thing ?
Thanks anyway :)
@Gold363
A rollback feature is in development since 1.4, but I delayed it every time since then because of errors. MAYBE it will find his way into 1.6 ...
Is there any future updates to make a rollbacks like other Logging tools have
@silentnight18
Good idea, I will include it in a future release. (The reload database command reloads only the databases but not the configuration)
also maybe a command to reload the config would be nice. unless that is included in the reload database command.
Patch is on the way but please, use tickets for error reporting!
Getting this error quite often.
2012-12-02 01:09:09 [SEVERE] Could not pass event PlayerCommandPreprocessEvent to LogEx v1.5.2 org.bukkit.event.EventException at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:341) at org.bukkit.plugin.RegisteredListener.callEvent(RegisteredListener.java:62) at org.bukkit.plugin.TimedRegisteredListener.callEvent(TimedRegisteredListener.java:35) at org.bukkit.plugin.SimplePluginManager.fireEvent(SimplePluginManager.java:477) at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:462) at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.java:977) at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:903) at org.bukkit.craftbukkit.entity.CraftPlayer.chat(CraftPlayer.java:233) at de.craftville.ServerSigns.tasks.CommandTask.run(CommandTask.java:76) at org.bukkit.craftbukkit.scheduler.CraftTask.run(CraftTask.java:53) at org.bukkit.craftbukkit.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:345) at net.minecraft.server.MinecraftServer.r(MinecraftServer.java:529) at net.minecraft.server.DedicatedServer.r(DedicatedServer.java:222) at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:493) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:426) at net.minecraft.server.ThreadServerApplication.run(SourceFile:856) Caused by: java.lang.IllegalArgumentException: Offline player not allowed at com.sk89q.worldedit.bukkit.WorldEditPlugin.getSelection(WorldEditPlugin.java:341) at lu.kremi151.logex.LWEListener.getSelection(LWEListener.java:121) at lu.kremi151.logex.LWEListener.hasMadeSelection(LWEListener.java:109) at lu.kremi151.logex.LWEListener.checkSelection(LWEListener.java:114) at lu.kremi151.logex.LWEListener.onWECommandListener(LWEListener.java:46) at sun.reflect.GeneratedMethodAccessor215.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:601) at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:339) ... 15 more
Please dont ever take this plugin down Best logging tool so far better then CoreProtect and the best part it all stores in it folder Great Job remaking it better kremi151 :D
@velasdad
LogEx is working fine on 1.4.4
Thanks. How's 1.4.4 coming along?
@velasdad
You can disable it in the config.yml (I'm probably going to remove that notification, you are not the first one who freaks out )
Is there a way to disable the message that shows up in-game about the backup being complete. People on the server can see it and it freaks them out....
Over 2.000 downloads!! Wow!!
@kremi151
Yes Please!!