Bukkit

@fungreenfox

I've never seen naturalgrow events, but it seems likely that's newly added since I last worked on it, or perhaps unique to your LogBlock configuration. I'd bet all you have to do to fix that issue is add "NaturalGrow" to the ignored list of players for the LogBlock history manager, link to github here. All of my plugins are built with maven, so building them is a simple matter of running "git clone" to copy the repository to your machine and then "mvn package" to build the JAR. Feel free to add NaturalGrow to the list and give it a test in your environment.

Heimdall does for sure have false positives, the most often I remember seeing was the occasional null owner alert. I don't recall if that was fixed or not.

However, specific to GriefPrevention (don't know what this is, assuming from your description it's a land claim sort of plugin), there's no magic hook in Heimdall to ignore griefing on those plots. Adding one would of course eliminate any false positives. In the mean time, it's possible your LogBlock histories have someone else as owning that block, or that you're seeing the null-owner type bug, not really sure.

Do note that if you trust a player not to grief, you can "/hdi" to temporarily ignore alerts from them. Or better still, promote them to a trusted rank that Heimdall doesn't monitor. On my server, Heimdall only monitors new players for griefing. Once we've promoted them to a regular player, we don't monitor them anymore.

@fungreenfox

If you add a friend, Heimdall will no longer alert on blocks between friends. It has an automated system whereby if it notices people building near each other, it will suggest that they might be friends and allow them to friend each other. This avoids spam when a group of friends login to a server and start building together, you won't get alerts from them working on their shared structure.

You can manually friend someone as it often happens that one person joins and days, weeks or months later they have a friend join and start helping them; once you know they are friends, you can use the /heimdall admin command to tell Heimdall about the friendship so it stops alerting you.

Regarding banning of griefers, no. That was this plugins original intent, but after I wrote the automated alerting piece, my mods asked me not to build the auto ban piece. They liked having something to do by looking into and responding to grief events. While I still like the idea of the auto ban, at this time I'm not actively working on Minecraft plugins beyond keeping mine maintained in their existing state, so it won't be added anytime soon unless some other dev decides to pitch in and write it.

Right now Heimdall serves as a very good notification system of griefing that might be happening on your server. It requires some tuning to weed out false positives (like setting common shared farm items like wheat to 0 points), but once in place, it's a very reliable notification of griefing events.

@fungreenfox

That's as it should be: the block ownership hasn't changed if you restore something through a block logging tool (such as LogBlock) or WorldEdit. If you restore it to it's original state and someone else comes through and griefs the same blocks, you should still get notified.

Regarding blocks in main.yml: just add the ids you want. The ones in the default config are just some defaults. Any block id not in main.yml defaults to 1 point. So if, for example, you decide you don't ever want to be notified about sand, you could set it to 0 points. Or perhaps you still want to know if someone steals sand, but you don't want a ton of notifications, you could set it to 0.1, so someone would have to break 10 blocks in order for a whole point to be accumulated.

Last, Heimdall has a notification anti-spam feature built into it, so if someone is destroying dozens of blocks of sand in a very short time, you might only get one notification: I think it's one notification per 10 seconds. Although I had always intended to make it configurable, I think it's still hard coded at 10 seconds right now.

One item on the "todo" list that was never coded was the ability to exclude warnings for a specific WorldGuard region. The idea being you could set large shared regions (with pass_through set) where you don't care if someone griefs and you want to exclude that region from notifications. I never implemented it because we didn't have a need for it on our server and no users of Heimdall ever asked for it; no point in coding features that no one is going to use. :)

@yaguznal

v1.7.2, tested against CraftBukkit 1.5.1 has just been released. It will be available here whenever the Bukkit admins approve it.

@yaguznal

Hmm, that's an error related to a change in 1.4.6 when the Bukkit team changed the method signature of JavaPlugin. I may have to eat my words here, maybe the latest version *isn't* running against 1.4.7.

I do know that Heimdall it is running fine on my 1.4.7 server. Which means if the latest version available here on DBO isn't working, it's because I fixed the issue and then just deployed it on my server and forgot to release it here.

I'll do some testing with the latest version here on DBO to confirm whether or not it's working against 1.4.7 and if not I'll package up a working release. I may have a chance to do that this weekend, I'll post an update with what I find.

@yaguznal

Heimdall is working on 1.4.7, it's a critical component of my servers anti-grief measures. Its only supported log plugin right now is LogBlock.

As to future development, the truth is I don't play MC anymore and mostly am too busy with other things to develop for it like I once did, though I still stay in touch with my server and would fix any critical issues. Heimdall spits out the occasional benign exception, but for the most part, it just chugs along like a champ and hasn't needed much work since the last version I released however-long-ago.

So there haven't been any new releases because I just don't have the time / motivation to work on it right now, and also in large part because the current version fulfills it's purpose so effectively on the server I originally wrote Heimdall for (my server).

I still enjoy coding when I have time to do it and have future ideas for Heimdall that I never got to finish, whether or not I'll ever get back to it is an open question.. But in the mean time, if you're an admin that doesn't mind a little do-it-yourself work (there's practically no documentation), Heimdall's most recent release is still running great.