@bigscary

Everything loads fine on startup, no errors or anything

@bigscary

I have:

LimitSurfaceWaterBuckets: false

hi bigscary.

I've been using your plugin on localhost for a few weeks now, and are preparing to start another server using your plugin instead of the towny-based one we already have. Firstly I would like to say that the plugin works great, exactly as advertised, and appears to be rock solid and well written - so thank you very much!

But back to the reason of writing, I written a plugin that uses your API, and essentially does the same as the "RealEstate" plugin, with the addition of being able to sell admin sub-claims, and more checks for "potential glitch exploits".

Anyway, to explain my problem, I'm trying to obtain a list of who has permission for a claim or a sub-claim. Straying outside of your recommendation to "not mess with code that wasn't mentioned in the API page" - i quickly found wierd errors to occur, and so am stuck.

Currently there are only two "useable" methods called 'claim.managers.remove("playerName")' and 'claim.dropPermission("playerName")' - however there doesn't appear to be a method or list I can use to either clear all permissions or managers, or where I can obtain a list of existing permissionholders/managers so I can remove them. I see there is a claim.manager property, however that seems to always return an empty list, and there is no list I can see that lists players with a granted permission exposable through your API recommendations.

What I am trying to do is remove any "trust" permission from a plot when a player purchases a claim or sub-claim before adding the purchasing player to the trust list, and verificationally(?) use the list of permissionHolders to determine whether the user is already the owner, and so has no need to buy the plot (if they clicked it either accidentally or testing if the sign works). I could also use this list to determine whether a sub-claim already has an owner(s) with permission to build, and so therefore the sub-plot could not be re-sold until the existing player(s) were removed. Like "if (claim.permissions.build.size() > 0)" would determine that the sub-plot already has somebody/people with builld permissions, and as such, an owner, and so you can't sell it again until they're evicted.

Any help would be greatly appreciated <3 - and I hope I explained properly :p

@notif

It's up to players to decide who they trust to change their areas. While I see it might be helpful for a very few situations, your suggestion would be extremely complex to implement, and even more difficult to explain to players how it works (what exactly the rules would be for this "semi-trust" mode).

The reason the videos exist is because no amount of help text splashed into the chat box could come even close to teaching someone as well as a short video. Providing minimal help as text, then pushing players to click a video link is, I think, minimum time to information. :)

Going to shorter slash commands that don't include "claim" for example runs the risk of conflict with other plugins, so I don't do it by default. You don't need a plugin to create aliases on your server, just add aliases in your bukkit.yml file.

For the last two suggestions, I think there are VERY few cases where they would pay off. I don't think I will take the time to add them, unless more ask for the same in the future.

@Chaett

Sorry, there are a few configuration options which are not per-world. I think you named most of them there. :\ I don't plan to make them per-world because there are very few servers who want that level of customizability, and adding it would make the config file even more complicated for everyone.

Of course I wouldn't presume to tell you how to run your server - have you considered the benefits of leaving these protections on? I understand you don't need the land claims because Factions will take care of that, but if you were to disable these features somehow, you'd have widespread world grief including entire forests burned and a world surface covered with explosion craters. That would be a bad thing, right?

@Harry4of4

Please check your boot logs, when Grief Prevention is loading, to see if there's any error message there about a problem connecting to your database. My guess is that the connection failed, so you're seeing these issues every time GP goes to look for data about land claims.

@arrexel

Have you disabled the water dumping limitations in the config file? There's a very noticeable performance hit for doing that, because it's much more expensive to track fluid flow outside land claims versus inside them. Please check. :)

@ManBeastPigDev

I think the problem is that you've mixed versions. Please make sure the Grief Prevention and Modify World versions you're using is compatible with the CraftBukkit version you have installed. You can check compatibility by clicking the "files" link at the top of plugin pages. If that isn't it, please start your investigation with the ModifyWorld developer, because that's the plugin which is complaining in this case (it may be a GP problem, but please start with the loudest plugin). :)

I'm getting this error at random times, also very often, maybe everyone 10 - 20 seconds http://pastie.org/5369993

Anyone know the problem?

Hi. I am running GP 5.5.1 on my Tekkit server.

Doing a NoLagg Examine shows that GP lowers my servers TPS drastically due to checking flow paths (BlockFromToEvent). I assume there must be many different chunks with flow paths around claimed land to cause so much lag, so its not as easy as find-the-problem-chunk-and-fix-it.

Here is a screenshot of the examine: http://i1121.photobucket.com/albums/l502/arrexel/examine.png

I am wondering if there is a global fix for this, or if it is patched in a later version.

Any help is much appreciated.

@xcb567

What's WoT? What type of documentation are you referring to - public API, administrative details, or player documentation?

If public API, declined. Almost no one uses it, a short page with some quick tips should be enough. Amateur developers can figure out the rest, my source code is available and I'm ready to answer any questions.

If 2 or 3, there are videos demonstrating the use of all the features which aren't super simple. For the rest, there's a quick text description on the administrative details page, which is pretty searchable (I think?). That page also has a quick reference for all the administrative commands along with the relevant permission nodes.

Are there specific features you were trying to learn about which proved difficult to research? I'm happy to do targetted improvements to the existing docs. :)

@bigscary

Alrighty then. :)

@n33dy1

Yep, I see the benefit in adding such flags to the claims, for compete and to stop folks from asking for them. But I'm still clinging to my principles on this one - I really think most folks wouldn't need the flags, and those who do need them probably use a different plugin already for them.

@CompeteToDefeat

It's a log IN cooldown. So unless you log IN within two minutes of your last log IN, you won't have a problem. It's very rare for players to hit the cooldown, because most play at least a few minutes before they log out, and then usually don't log right back in.

You shouldn't expect any performance increase when you switch to SQL, only the additional headache of going to SQL for data backups, edits, etc. I recommend using the file system.

@AnDwHaT5

You need Tekkit Customizer to ban items like those. It's impossible for bukkit plugins to limit Tekkit's tools because Tekkit isn't well made and doesn't play by plugin rules.

Also, if your shovel isn't working it's because you're using the wrong version of GP. Please see "notes for tekkit servers" above for more information on both these points.

@wowlover687

Very glad you like it. :)

@Chriz2012

The total claim blocks limit is enough to prevent players from claiming too much. Actually putting a limit on the number of individual land claims just gets in the way, and will annoy your most valuable (regular) players moreso than anyone else, so I haven't added any such limitation (don't worry, you won't need it - there's automatic cleanup code for forgotten claims).

@EstJoel

Ah sorry, that needs an update. Use -1 instead of NULL.

@Apple_columb

Can you copy the content of your old table over to the new table? The code for creating tables and reading/writing them has not changed since I introduced it months ago. If there's suddenly a problem for you, I think it must be because something (possibly minor and nuanced) changed for you. I'm very sorry that I can't help, as I'm not a database expert - these are the perils of choosing database storage over file storage. :(

@ManBeastPigDev

Yep, see above - I already promised to deliver this feature in the next version. :) Probably this week.

@zSwayz

They can't do it, you'll need another plugin like grief prevention real estate, for example, to make this available to players. As a workaround, if you have a server economy, you could enable buying/selling. Then players could give each other claim blocks by passing server currency.

I can't figure out how to enable players permission to transfer claims. :l Is there a permission node for this somewhere?

@bigscary

Sorry to leave you hanging on this, I was using the broken bukkit beta when I encountered this issue. Upgraded and the problem was gone.

I'll also switch to pastebin instead of hastebin for posting crash reports, I didn't realize hastebin kept its links for such a short amount of time!

Hi,

Is there a lower limit to what the blocks per hour can be set to? I tried setting it pretty low as 100/hour seemed too much, but no one seems to be gaining any blocks.

Any suggestions are appreciated. Thanks!