@urndel

You already have an option to remove claims for players who have been offline for a long time, which is turned off by default. See administrative details page.

I think you may have misread my post below. I was saying that if a player does not build something in a claim AND is offline for a long time, then the claim will be removed. I did not say that claims which aren't built in will always be removed, even if the player is active. None of GP's features automatically remove claims which belong to active players.

@Feaelin

Yep that's correct, except that the area will ONLY be restored in creative mode worlds. In survival mode worlds, the build will remain, so there's a chance that the player could one day come back and reclaim it (and also a chance that it may be looted or destroyed if he doesn't come back). My intent is to permanently preserve anything bigger than a tiny wooden house. I'm not trying to pressure players into building bigger, only to clean up unused and forgotten claims. Note that an active player's claims will never expire, even if he literally just claims a tree and never builds anything in the area.

@DrFusion

That's already done, but it's not only for the same IP address. If the join/leave messages are coming too fast, even from multiple player accounts and IP addresses, they will be temporarily muted.

@bigscary

is blocking the join message in a defined interaval from the same ip address? ex. ip 1.2.3.4 is joining several username within a 30 secs, they it mutes their "player has joined message" sounds like a idea, it possible?

@bigscary

If I understand you correctly, the new feature will delete claims (and restore nature) in a claim if the number of player placed blocks doesn't exceed a threshold value? So if someone logs on, builds a chest and a dirt hut and then quits, that claim (and its contents) will disappear after two weeks. But if someone logs on, builds a larger, more elaborate structure, regardless of inactivity, the claim will remain?

@bigscary

I want claims by a certain player to expire after a configurable amount of offline time. I do not want claims to expire if no blocks are placed in the specific claim. If that happens that means that players will be forced to change builds even if it doesn't require any changes. If claims expire due to players not placing blocks in them I will abandon GriefPrevention.

Just a heads-up on what I'm working on. I have a concern that on servers which are up a very long time (many months), the total number of claims may EVENTUALLY become a performance issue. Just to be clear, what I mean by "maybe eventually" is that even after 9 months of uptime, my test server has about 2500 claims owned by 800 or so unique players, and with the recommended RAM for 30 slots (1.5 GB), I still don't see any issues with performance.

So what I'm going to do is try to determine which player claims are largely "unused" by scanning them for player-placed block types, similar to the approach the /restorenature command uses to remove player builds and restore a natural environment. Any which aren't used and are owned by players who've been gone a full two weeks will be automatically deleted. In creative mode, the land will be reverted to a natural state. Administrative claims and very large claims (due to the performance cost in scanning them) will be exempt.

This is even more important for creative mode worlds, where players commonly create claims beacuse they have to, then lose interest in creative mode and leave without really building anything. On my creative mode server which has been up only a few months, I already have more than 5000 claims, and many of those are getting in the way of new players placing claims.

If you see any potential issues with this approach, let me know. Thanks. :)

@zempire2010mjk

Even if I coded it so that playres could break blocks but not build outside claims, then you'd still have a sprawl problem because players can move their claims, or create additional claims. If you take all that away, you end up with a management problem because players get pissy about not being able to manage their own stuff, always having to call an admin every time they want to adjust. It's a no-win situation, I think. :\

@DrFusion

Right, I understand that. I'm saying that there's no way to fix that - there shouldn't be a rule, for example, that a player can't send a reasonable looking chat message when he first logs in, or that two players shouldn't be allowed to say the same thing. I beleive that what we have right now from GP is the best anyone can get from any anti spam plugin without running the risk of also muting or banning players who aren't really spamming. The additional "spam" cases that can't be covered with code have to be covered by real people, just like chat trolling has to be covered by humans, and rules against building "offensive stuff" must be enforced by humans.

Fortunately, all of these problems are relatively rare in general, although I believe your server may be an exception and I'm sorry to hear that.

@bigscary

But i meant those join bots, random usernames which every username say "welcome to so and so" not those join and leave spam by one username spam

Sorry folks I was away for the national holiday. :)

@08havoc

You just don't get blocks when you are idling. It's very smart - you can't work around it by riding around in a minecart or spinning in circles, for example.

@Nenestar

Assuming you're running a survival server, they can build anywhere they want. But they should claim the areas they have built to avoid future grief.

I don't know the details of the spells plugin. You will probably want to change the stick tool to something else, because I think spells uses the stick as a wand. Also you need to test yourself to make sure that none of the "spells" can be used to circumvent anti grief (hopefully the answer is no). That will depend on how well the spells developer coded his plugin.

@BorzoyExist

As mentioned in the documentation above, something like /accesstrust public or /containertrust public will grant permissions to everyone.

@ksisa112

I'm glad you got it figured out. For anyone tuning in, the issue had nothing to do with GP.

@ha11oga11o

This is a vanilla bug that has to do with latency. Basically, the player clicks fast enough that his client allows him to stand on the blocks, and the server is too slow to tell the client "you weren't allowed to build there". There's nothing a plugin can do to fix this, sorry. :\

@zlepper

I dunno what you mean by version check. You're on your own for connection problems. Look up ODBC connectivity on the internet to troubleshoot your database problems. You can't add damage values there, yet. It's coming later, but you shouldn't need it because that is for Tekkit servers, which do not currently support Minecraft 1.3.1.

@Dr_Shankums

You've probably mismatched your versions. You need to get a version of GriefPrevention which was built for Minecraft 1.2.5, because that's the version your Tekkit server is running.

@iTristan

This is by design. Due to the TNT cannon (basic Minecraft physics), it's never safe to allow tnt to destroy blocks in a claim, because it's impossible to be certain that the TNT was placed by the claim owner and not a griefer.

@Patrick_Janson

/ignoreclaims

@Jeanzl2000

This has nothing to do with anti grief, you need to download an additional plugin if you want that feature.

@revels21

Yes, you can grant blocks based on permissions. See administrative details page. :)

@JustinM511

Yes, /accesstrust all or /accesstrust public, for example.

No sorry, I don't think animals despawning is a grief problem. :) I do agree it's a problem.

@zempire2010mjk

It's designed for weird servers who want to manually create land claims for survival mode players to play in. I'm sorry it didn't meet your expectations, but I don't plan to add a feature to reduce "sprawl", as that's not related to anti grief.

@flimsy888

Do you mean you have a world with creative mode rules but your players are in survival mode? Then remove the survival worlds from the list of create mode rules worlds in the config file.

@DrFusion

It's impossible to reliably detect a URL because there are too many workarounds. Consider for example myawesomeserver,com. Even if I could, you'd be blocking all kinds of reasonable chat like "minecraftwiki.net" and youtube links, which are common amongst Minecraft players.

This is one area where no code can do the job right. It requires a human eye (similar to ugly build detection... no code can automatically remove ugly builds without also removing pretty builds).

@Smudge202

If you get the error message about not having permission, that means GP is doing its job. The fact that you still get the UI for the timer is a bug in your mod, because it's showing the UI even though the player interaction event was cancelled by GP. Please contact the developer, sorry for the trouble. :\

@Feaelin

Ouch! I'm glad you figured it out. :)

@DrFusion

Already done months ago. Join/leave messages will be muted if they are coming too fast, and if the jerk is reusing accounts, he'll find he has a 2 minute cooldown between logins on each account. The only alternative is to actually stop all joins temporarily while the attack is underway, but that would actually be helping the griefer because you're also preventing non-jerk players from joining.

@PCGeek971

Nope, sorry. I believe you must have good reasons for asking, but I also believe almost nobody else would want those permissions, and it would add a lot of complication to permissions management for everyone.

@Jeanzl2000

You need to get one of the versions which was built for Minecraft 1.2.5. I think 5.5.1 was the last one.

@Jeanzl2000

All bukkit plugins work with tekkit.

@Feaelin

My dear...

im talking about exploit glitch where players actually build inside protected area couple of blocks just enough to climb up the walls.

Those blocks dissapearing with message you cannot build here, but not quick enough. So they use it to climb fast.

cheers!

suggestion: stop massive about of join bots from spamming and crashing server

@Feaelin

Turns out the backup plugin was misconfigured and derailed the scheduler. That stopped claimblock earning and for some reason the routine to make the glowstone & gold bordering blocks appear.

suggestion: u current has no ip ads, why not but no link? like greifers cant put an ip in chat, might as well but their website of the server which has their ip, hmmm?