@zathrus_writer

@zathrus_writer:

Sounds like it mimics process priority on *ix, where the lowest number (negative 20) is the highest priority. It can be confusing to talk about, though. :)

@bigscary

no, not highest... lowest, because Bukkit works from lowest up to highest and that's how plugins get the event passed - lowest first, highest last... I was surprised by this as well myself but one learns to live with it ;)

@zathrus_writer

Do you mean highest priority? Anyway you make a good point, I could add a configurable list of slash commands which send private messages for better eavesdropping where other plugins are involved.

@KrYojeNiX

I said that you don't need more plugins to solve your grief problem. The features I refuse to add are not necessary for preventing grief - they're optional fun features. If I allow those non-essential features to creep in, THEN I'm contradicting myself. If you think you can make a case for any of the features I've refused to add as being absolutely necessary for preventing grief, then go for it.

Due to your sarcastic, self-important, judgemental tone, your comment has been deleted. When you can frame your arguments in a constructive, civil fashion, you may post here.

@jmcgee611

You're still not telling me what your specs are. If you're not going to do the work to ensure you have minimal specs needed to run a Minecraft server and eliminate other plugins as the problem, then don't add noise to my comments. If I have a problem I want to fix it, but I need more information before I can take action.

There's no relationship between claim size and performance. The only factors are number of claims and number of online players. That's why I suspect you're not running with reasonable CPU and RAM.

@bigscary

I don't know how you coded the eavesdropping feature, but some plugins allow for local chat or even chat with /msg instead of /tell... what I'm doing in CommandsEX is checking PlayerCommandPreprocessEvent for all possible commands that an admin sets up in config as used for personal messaging

also, I'm intercepting all chat in PlayerChatEvent with lowest priority to get it to my plugin before any other one tampers with it (HeroChat, for instance, will nullify all recepients)

just an idea...

Hey guys! I was checking 3.8 updates and tough Um... Griefing... Avo... Oh! Let's go watch avolition! Lol

Just wanted to say to bigscary that if you need a test griefer, im in! (I'm a server owner and a griefer) Fail.

Thanks

3.8 Updates!

• Added a new "eavesdropping" feature which allows administrators to see /tell messages. It's off by default, but when enabled, will both log those messages and send them live to anyone online with the "griefprevention.eavesdrop" permission. Those with the permission are immune to eavesdropping (their private messages are still private). Note that this doesn't do anything for other slash commands you may add with other plugins, so keep that in mind. This feature can help you catch griefers and cheaters who assume their messages are private, and use them to collude. For example, "hey, is your x-ray working?", "ooh! this chest isn't claimed", or "i talked some guy into /trusting me so i can steal his stuff later".

• Tweaked anti spam to be a little more lenient with "fast chatters".

• We've now 100% eliminated copy/paste spam.

• When auto-ban for spam is disabled, the spammer will be kicked after ignoring a warning.

• Fixed a minor creative mode spawner egg problem.

@bigscary

i have been wondering about spawn egg issues, i wonder if its the same one that i was trying to pin ;)

@re4397

Not if you disable the land claim blocks in precious stones.

Thanks, link is fixed now.

@pur3pros

I understand about accidentally picking up a block. That's why playres can't pick up blocks for about 10 seconds after respawning, to prevent griefers from putting items on the spawn just to spawn camp.

There are two problems with a plain timer, which was my original plan. First, this would allow players to pick up stuff and run off with it without being at risk for pvp. You can see where in some cases, players would be outraged at the invincible "thieves" (he stole my monster loot!). Second, in many cases, the timer could run out before the player has a chance to get back to his house or wherever, where he can re-arm himself. That makes him vulnerable, even when he's unarmed.

I know that there's a small exploit for the current system, where a bad guy could camp outside your house, and drop a lot of items on the ground so that when you come near, he can kill you again before you can get inside to safety. But I think that the timer issue has the same problem, and overall, the current system is the best balance. When unarmed, regardless of timing, you are not vulnerable, but as soon as you start doing someting other than running away from the spawn point, you end up picking something up and becoming fair game.

@bootsmith

@re4397

I tried very hard, and couldn't make either of your issues reproduce on my server with the latest craft bukkit RB and the latest version of grief prevention. I'm not calling you liars, understand, but I just didn't have any luck pinning down your issues. Will you both please check your craftbukkit version? It's very important that you're using a recommended build, and not a dev build (those are known to be buggy). If you're on the latest GP version AND the latest recommended CB version, then please post more information about your problem if you can. In the worst case, I can come visit your server and we can look together to see if maye there's more information we're missing.

I did find a small bug with spawner eggs though, while looking for your bugs. :) So thanks for that.

@deseven

As it turns out, I was already checking for block is null. So I added a check for player is null, which seems ridiculous to me, but I added it anyway. :) I hope it will help.

@bigscary

agreed... would you at least thing of adding wooden planks as protection start block? there are not too many players that will use anything else to actually build their very first house than planks... except very few that carve it into stone, for which chest or even furnace will do ;)

Update your GitHub again please?

@khanjal

The permissions for claims aren't mutually exclusive. Anyone who has container access also has access. Anyone who has build permission also has both container access and button/lever access.

If you think about this a little, you'll see the logic. If someone can build, then they can break open any door or chest, so they might as well have access to those. Similarly, if you trust someone to open your chests, why wouldn't you trust them to open your iron doors (which may keep them away from the chests you gave them permission for)?

@deseven

Okay, diverging from the standard. Being weird. Anyway like I said, I will try to do something.

@Machinimatt

No, I won't add per-group claim blocks limits. Claiming a larger area becomes increasingly difficult already because blocks accrue at a flat rate rather than a percentile increase. So you'll find that players have to play a REALLY long time to get a large area, unless you reward them with /acb.

@Mako_Shark

Yep just use /ic. :)

@re4397

Thanks Mr. Vader, I'll investigate this error message you're seeing.

@mailtomomo

Localizability is on the to-do list. I just haven't to-done it yet.

@Munkyman587

First, try disabling all your plugins except for GP, then checking your TPS. That at least will eliminate any other plugins as a possible cause. You can also try this site:

http://www.canihostaminecraftserver.com/

If neither of those help, come post again. This is the very first time anyone has ever complained of a performance problem. I hope I can help. :)

@bootsmith

Thanks booth, I'll look into this as soon as I can. Lava should work after an hour, so I probably introduced a bug recently.

@zathrus_writer

I kind of like that idea, but also I kinda don't. I know many players like to create a crafting bench right next to the first tree they punch for sake of convenience, then later start a house somewhere else. The benefit of the chest is that it's troublesome to move a chest full of stuff, so it's a better indicator of "permanence" in a player's settlement. :) Also, there's no guarantee that the player will place his first chest near the very first block he placed, so many chests will go unprotected.

@re4397

Will not block sethome. I'm solving vanilla problems here, and problems I create with my solutions. There are a million ways another plugin could cause trouble, and I can't be expected to account for them all. If you add a plugin which allows players to grief others, that's your plugin selection problem, not my coding problem.

Adding any kind of flags for special behavior inside of claims (pvp) is on the to-don't list above. Players can make themselves safe from pvp using an iron door, because players without permission can't use the buttons/levers which open it.

@DJAmnesia

In the config, there's a "creative rules" list of worlds. Remove your survival worlds from that list. That rule about building in the wilderness is for creative worlds, not survival worlds.

EDIT: If your world is actually meant to be a creative world, I don't think you should remove it from the list. Because creative mode players have unlimited resources, a griefer can make an enormous mess if he's not restricted to building within his limited claim area, or with tnt, which will destroy terrain in survival mode.

@zathrus_writer

if your home plugin does not have private homes, then I'd consider switching for another solution... at least MyHome and CommandsEX have this functionality