Hey all, I have several fixes and improvements but because one of them feels a little risky, I'm going to hold the release until tomorrow while I run it on my test server to make sure nothing falls apart. Stay tuned. :)

@Ganzor

Hey Ganzor, I actually have this fixed now, thanks for the info. The fix will be in the next version. Until then, the workaround I mentioned will work for you. I won't release today because I also made a big change to something that's difficult to test, so I want to run the updated version on my test server for a day before giving it to anyone else, just in case there are some problems.

@LiteWarfare

Okay, it sounds like your world is in creative rules mode. If your players there are not in creative mode, then go to your config.yml and remove any of your survival worlds from the "creative rules worlds" list. The reason it defaulted to this for you is because in your server.properties, you have your server's game mode set to creative.

@ljrobison

I don't think I understand 100%. There's a config option to set how many claim blocks players start with. If you want your current players to have some bonus blocks but not the new players, the easiest way would be to run the plugin a few days with a larger default blocks setting, then set it back to a lower amount before you open the server to new players. The current playres would get the higher default, and the later new players would get the lower default.

You could also do this with permissions, if you don't mind the headache that always comes with permissions management. See the administrative details page on how you can give bonus claim blocks to players based on their permissions.

@jbanto

This is in the newest version (or maybe it's only my local version... in that case, you will get the update in the next version). :)

I recently changed it to not tell players about land claims before they at least had their first claim. In your case, imagine your players' annoyance when every 15th block gives them a warning message, until they get around to mining for some gold. The better fix may be to give them their default chest claims. You could reduce the size, if you want.

@Swainooo

I THINK almost all of the features can be disabled with some creative config.yml editing. Check the administrative details page. It's not often somebody wants to download all the awesome and then take only a taste, so I'm not sure it will work out 100% for you.

@waybaker

No sorry, you're the first to ask for a permission node specific to buy/sell in more than a year of development. :) I may reconsider if more folks ask for it.

@tonymchugh97

The next version will have a fix to give you an explanation in this situation. For now, you need to check your config.yml to make sure you set prices for claim blocks, and check your boot logs to make sure your economy plugin and vault are working together like they should.

@higigabob

What plugin are you using to load the worlds? Multiverse? MyWorlds? Something else? Make sure your multi-world plugin has these worlds "registered". The steps vary with multi-world plugin, so you might have to check the documentation over there.

@Jeanzl2000

Yes, you need to put the quarry block on the edge of your claim, facing outward, so that the blocks it's changing are outside your claim. Have it pipe the collected blocks to a chest which is safely inside your claim area, where nobody can hook a pipe up to it from the outside.

You have to work around anti grief with machines like this because the Tekkit mods don't play nice with Bukkit - they don't tell Bukkit who owns the machines, so none of the machines can be safely trusted in any land claims.

@Ganzor

Okay, I'll look into it. For now, do this:

1. /ignoreclaims

2. /trust yourself

3. /permissiontrust yourself

Which GriefPrevention version are you using, and are you on a Tekkit server or a basic Minecraft server?

@thloh

Uhh, I think you want /ignoreclaims. There's a permission for that slash command, check administrative details. I don't plan to make any new releases for 1.2.5. I totally understand the position you're in running a Tekkit server myself, but it's too much to ask for me to try developing for two different versions of Minecraft at the same time. It's the pain you opt-into when you decide to run Tekkit. :)

@ha11oga11o

I'm sorry you're having so much trouble. It must be that whatever plugin you're using to manage bans is messing things up by not using the Mojang-provided ban lists properly. Try giving yourself a /pardon, then immediately doing a /reload.

@Praqoon

Okay if you mean that you'll actually be deleting the old map and starting a totally new large biomes map with the same seed, I suspect the result will be a completely different map, with everything freshly generated. I don't believe that using the same seed for two different map types will result in similar maps at all. If you decide to do that, I recommend deleting all claims in that world (dont delete player data, so players can keep their claim blocks) so that players can start fresh.

If you mean that you're just changing the map type and seed without deleting the map (is that even possible?), then all the areas already generated would remain the same, but NEW areas which were not explored until after your changes would be using the large biomes. Existing claims would still be valid, and would still protect the builds they were created to protect. Coordinates would not change. Also in this case, /restorenature is very safe to use even though you've changed the map seed, because it does not rely on regenerating the terrain.

@DrFusion

Yes but it's not fair. It's a totally valid use-case for two people in the same house to play Minecraft together on a server (siblings? friends having a sleepover? a LAN party? lots of players at a school library?). Treating them as the same person for anti spam purposes would lead to them being harassed by warning messages and possibly kicked/banned, just for having an ordinary conversation. Same IP address often, but doesn't always, mean same person.

@Jeanzl2000

I do plan to update the default configuration to cover all Tekkit blocks. But I'm waiting for Tekkit to catch up with Minecraft 1.3.1.

@waybaker

The only slash commands and other operations which require permissions are the administrative operations. The only exception is if you decide to require permission to create land claims, which you can do in your config file.

@MoonPie2000

Sorry, I can't confirm that 100%, but it's extremely likely that you will NOT have a problem as long as you're on a 1.3.1 recommended build. Good luck!

@edean82

Sorry no, that's in the to-don't list. It will hurt performance, create a lot of risk (bugs!), and will take a lot of time, when very, very few players and admins would use it. Also using it would lead to griefability in many situations (like somebody building a giant penis floating over your house).

@Ganzor

Anyone who has permission to create an admin claim (griefprevention.adminsclaims) can do whatever else he wants inside that claim. You can also use the usual /trust commands to add specific players permission, or commands like /trust public to give everyone permission there. You can even do /trust [permission.node] to grant permission based on Bukkit permissions.

So you have options. :) For this specific case you mentioned, it sounds like you want /accesstrust public.

I'm aware the admin video needs updating, since I changed the permissions defaults for admin claims a few versions back.