Grief Notice
Description
Tired of griefers? Get notified when it happens!
This plugin will monitor new players login in to your server, checking what blocks they break and making sure it was not one they placed themself. The default config will monitor the first 100 block breaks and then notify people with the announce permission the monitoring stopped.
On join message for people with GriefNotice.announce permission

Grief announce for people with GriefNotice.announce permission

Extensive and easy listing on player activity during illegal block breaks.

Easy porting to the incident allowing you to quickly check and verify the situation

Config.yml
#Change the value of Blockbreaks if you wish for the plugin to monitor more or less blocks Blockbreaks: 100 #Add or delete block ID's in Checkblocks to remove or add more blocks to be monitored Checkblocks: - 5 - 20 - 22
Default materials monitored
- Wood Planks
- Glass
- lapis Lazuli Block
- Dispenser
- Note Block
- Bed
- Powered Rail
- Detector Rail
- Sticky Piston
- Piston
- Piston Extention
- Wool
- Block of Gold
- Block of Iron
- Brick
- Chest
- Redstone Wire
- Block of Diamond
- Furnace
- Burning Furnace
- Iron Door
- Jukebox
- Glowstone
- Redstone Repeater Active/Inactive
- Trapdoor
- Stone Brick
- Iron Bars
- Glass Pane
- Fence Gate
- Enchantement Table
- Brewing Stand
- Cauldron
- Dragon Egg
- Redstone Lamp Active/Inactive
- Ender Chest
- Block of Emerald
- Beacon
- Flower Pot
- Mob Head
- Anvil
- Trapped Chest
- Gold Pressure Plate
- Iron Pressure Plate
- Redstone Comparator Active/Inactive
- Daylight Sensor
- Block of Redstone
- Block of Quartz
- Dropper
- Stained Clay
- Hay Block
- Hardened Clay
- Block of Coal
Permissions
- GriefNotice.announce - Permission that gets block break notifications
- GriefNotice.admin - Permission for all /gn * commands
- GriefNotice.ignore - Permission to ignore monitoring players "use this in worlds you dont wish the monitor to work in"
Commands
- /gn monitor <playername> - Will make the plugin monitor that player again for xx (The value specified in config.yml) blocks
- /gn status - Will list the 10 last players caught breaking blocks
- /gn checkplayer <playername> <pageid> - Gives a detailed list of the players history
- /gn tp <id> - Teleports player to ID of incident
To do
make the plugin log to file and add commands to view log fileadd teleport commands, to teleport to incidents- add smart notice to notify if some players where caught inbetween admin logins
get 1.1b out of beta by adding error messages for wrong commands/syntaxes and pagination for lists "a player with a long history will clutter chat in 1.1b- View comment section for ideas? *hint* ;)
Changelog
Quote from 1.3:- Added teleport feature, easy teleportation to ID of incidents.
- Added command /gn tp <ID> - allowing to teleport to the ID of an incident.
Quote from 1.2:- Updated to CB 1.7.2-R0.2
- Added pageination with /gn checkplayer
- updated command: /gn checkplayer <playername> <pageid> - Will pull the complete information on the player.
- Added MCStats metric
Quote from 1.1b:Update pushed out due to an issue with the monitoring end announce function. Beta version since the new functions are not fully tested, they should still work.
- Added SQLite database. "no configuration needed"
- Added command: /gn status - will show a list of the 10 most recent players the plugin caught breaking stuff.
- Added command: /gn checkplayer <playername> - Will pull the complete information on the player.
Quote from 1.0:Complete rebuild of the plugin with several features / fixes
Updated to 1.6.2
Plugin will now check if blocks are placed by player and not track if true
Added config.yml
You can now customize what blocks to track, supporting all blocks in game.
You can set the amount of blocks you want to track before stopping the monitor.
Added permission to ignore tracking players / players in specific worlds.
Quote from 0.9:Updated to 1.4.7 R0.1
Added Block ID 98 Smooth brick in the check
Quote from 0.8:Added 1.4.2 support
Added command /gn monitor <playername> set the plugin to monitor specific players.
Added GriefNotice.admin permission node for command.
Quote from 0.7:Updated with support for Worldguard and varius other protection plugins, the message will only trigger now if the block actually gets destroyed.
Quote from 0.6:Updated with following blocks being monitored:
- Emerald blocks
- Chests
- Furnaces
- Iron Blocks
- Enchantment Tables
- Powered Rails
- Brewing Stands
Quote from 0.5:First Release
Supported by: mcs-list.org we can help your server grow!
Metrics is used to collect plugin statistics. Only data such as plugin version and players online is collected. If you do not wish for this data to be collected, disable it in the 'Plugin Metrics' folder of your 'plugins' directory.
-
View User Profile
-
Send Message
Posted Dec 25, 2012@hkenneth
Hello, LOVE your plugin! One of the best ones I've installed for Griefing.
I was wondering if you can add itemid: 98 stonebrick to the grief alerts? On our server, it's the most use housing material, so, if you could add it in a future 1.4.6 update, that'd rock and we'd be forever grateful!
Thanks so much for all your hard work and hope you had an awesome holiday.
-
View User Profile
-
Send Message
Posted Dec 14, 2012I'd also just like to say thank you for coding and maintaining this plugin. It is also very useful for me and our moderator team, and has helped us to prevent griefing (in time) several times.
-
View User Profile
-
Send Message
Posted Nov 27, 2012just here to say that my whole team and me loves this plugin and is probably one of the most useful anti-grief plugins. keep up dat good work <3
-
View User Profile
-
Send Message
Posted Nov 9, 2012@NyanCraftDe
Updated to 1.4.2 now, it should work once the 0.8 file gets approved :)
-
View User Profile
-
Send Message
Posted Nov 8, 20122012-11-08 21:01:32 [SEVERE] Could not pass event BlockBreakEvent to GriefNotice v0.7 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.SimplePluginManager.fireEvent(SimplePluginManager.java:477) at org.bukkit.plugin.SimplePluginManager.callEvent(SimplePluginManager.java:462) at net.minecraft.server.ItemInWorldManager.breakBlock(ItemInWorldManager.java:278) at net.minecraft.server.ItemInWorldManager.a(ItemInWorldManager.java:205) at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:552) at net.minecraft.server.Packet14BlockDig.handle(SourceFile:46) at net.minecraft.server.NetworkManager.b(NetworkManager.java:282) at net.minecraft.server.NetServerHandler.d(NetServerHandler.java:111) at net.minecraft.server.ServerConnection.b(SourceFile:35) at net.minecraft.server.DedicatedServerConnection.b(SourceFile:30) at net.minecraft.server.MinecraftServer.r(MinecraftServer.java:578) at net.minecraft.server.DedicatedServer.r(DedicatedServer.java:215) at net.minecraft.server.MinecraftServer.q(MinecraftServer.java:495) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:428) at net.minecraft.server.ThreadServerApplication.run(SourceFile:818) Caused by: java.lang.NullPointerException at grief.winthier.com.GriefNotice.onBlockBreak(GriefNotice.java:54) at sun.reflect.GeneratedMethodAccessor507.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.bukkit.plugin.java.JavaPluginLoader$1.execute(JavaPluginLoader.java:339) ... 16 more
Bukkit 1.4.2-R.02. Can you please help me? I really need this plugin. :/ There is nothing similar here.
-
View User Profile
-
Send Message
Posted Sep 30, 2012@MegaNarwhal
It just counts the blocks destroyed by the player.
I Do'nt see what difference logBlock integration would do, logBlock should record all blocks broken so it would still just display the same blocks regardless of integration or not :)
I do plan on making it optional so you can edit how many blocks you want it to check for however
-
View User Profile
-
Send Message
Posted Sep 30, 2012it would be neat to hook to logblock and run a user defined command if they break too many player placed blocks within a radius of eachother but thats kinda a different plugin all together
-
View User Profile
-
Send Message
Posted Sep 30, 2012How does this only check the first 100 blocks? Could you add LogBlock integration so that it uses the first 100 blocks logged by LogBlock for that player?
-
View User Profile
-
Send Message
Posted Sep 29, 2012@wolfenguard
I'll make sure to add it in the config file so you can customize it. Added it to the To do list :)
-
View User Profile
-
Send Message
Posted Sep 29, 2012can you add multiple world support? I have a survival world and a creative world... and would just want to have survival world monitored.
-
View User Profile
-
Send Message
Posted Sep 29, 2012@Pixiyo
Oh ill be sure to add it in version 0.7 later today or tomorrow currently 0.6 is waiting approval with updated block types, thanks for the feedback however :)
-
View User Profile
-
Send Message
Posted Sep 29, 2012Please add WorldGuard support. Because now if a user breaks something in a worldguard protected area you will get an message too.
-
View User Profile
-
Send Message
Posted Sep 29, 2012It's funny because yesterday, I was thinking it would be useful to have a plugin like this and I thought I'd look into it today. I check the latest updated plugins on bukketdev, and I see this. Amazing! Thanks.
-
View User Profile
-
Send Message
Posted Sep 29, 2012Works great! Using this now.
-
View User Profile
-
Send Message
Posted Sep 28, 2012Great idea. Replaces a lot of tedious checking of logs on new players.
-
View User Profile
-
Send Message
Posted Sep 28, 2012Slick! I look forward to testing it.