Massive Griefer Attack - Need Help

[Abysinian]

After having an insane amount of lag to the point where the server was nearly crashing, I've found caverns like these all over one of our worlds:

All of the items that are possible to do anywhere near this much damage are all banned and some of the areas there were even protected with WG and other things.

Other than a whitelist (which I plan to implement after this) what can I do to stop this? And how did it happen in the first place?

[Nentify]

Can you give a complete list of banned items and mods? Have you made sure you've disabled them correctly? I think that'd be the easiest method to find what caused these explosions. My guesses would be nukes, nova catalysts or nuclear reactors.

[Abysinian]

Can you give a complete list of banned items and mods? Have you made sure you've disabled them correctly? I think that'd be the easiest method to find what caused these explosions. My guesses would be nukes, nova catalysts or nuclear reactors.

Within that world my PEX reads:

- -modifyworld.items.(craft|drop|have|pickup).(x126:10|x126:11|x179|x214|x237|x4095|x7303|x237|x26524|x27527:?*|x27530:?*|x27531:?*|x27535:?*|x27538:?*|x27556:?*|x27579:?*|x27580:?*|x30208:?*)

- -modifyworld.blocks.(place|interact|destroy).(x126:10|x126:11|x179|x214|x237|x4095|x7303|x26524)

So nukes, novas, catalysts, lenses, infernal armour and abyss helm are all banned. Plus anchors and a couple of other bits and pieces like cannons and lasers.

[mikekrason]

Within that world my PEX reads:

- -modifyworld.items.(craft|drop|have|pickup).(x126:10|x126:11|x179|x214|x237|x4095|x7303|x237|x26524|x27527:?*|x27530:?*|x27531:?*|x27535:?*|x27538:?*|x27556:?*|x27579:?*|x27580:?*|x30208:?*)

- -modifyworld.blocks.(place|interact|destroy).(x126:10|x126:11|x179|x214|x237|x4095|x7303|x26524)

So nukes, novas, catalysts, lenses, infernal armour and abyss helm are all banned. Plus anchors and a couple of other bits and pieces like cannons and lasers.

I have heard that modifyworld does not like metadata, aka for example

- -modifyworld.items.craft.(x126) <-- Works, but:

- -modifyworld.items.craft.(x126:6) <-- Doesn't.

I personally recommend a plugin called NoItem. Search it on bukkit.org. It is much better at blocking then modifyworld.

[Abysinian]

I have heard that modifyworld does not like metadata, aka for example

- -modifyworld.items.craft.(x126) <-- Works, but:

- -modifyworld.items.craft.(x126:6) <-- Doesn't.

I personally recommend a plugin called NoItem. Search it on bukkit.org. It is much better at blocking then modifyworld.

Thanks I'll have a look into that :]

[mikekrason]

Thanks I'll have a look into that :]

http://dev.bukkit.org/server-mods/noitem/ Here's a link. Had to dig it out of my favorites menu. If you need any help with the permission's setup, PM me and I'll be glad to help!

[pherce]

I have heard that modifyworld does not like metadata, aka for example

- -modifyworld.items.craft.(x126) <-- Works, but:

- -modifyworld.items.craft.(x126:6) <-- Doesn't.

I personally recommend a plugin called NoItem. Search it on bukkit.org. It is much better at blocking then modifyworld.

Works for me.

Also, if you want to do multiple damage definers on one ID, try something like this: x30172:.?*

NoItem will help you a lot. There are items like deployers and turtles that can place banned items and NoItem will prevent you from 'fisting' it. You can drag something from a project/automatic tables into your fist and modifyworld does not prevent this until you interact with something. This could result in someone ruining your map with a Mercurial Eye because they don't need to interact with a block to use it (like flint).

[matejdro]

1. Modifyworld supports metadata fine.

2. Deployers and turtles behave as players. Unless you /op them and give them all permissions, they are bound to the same restrictions as any players.

3. Modifyworld have "have" permission, which will delete item as soon as player moves it into hotbar, if player is not allowed to use it.

For example here are our permissions for the watch of flowing time:

    - -modifyworld.items.craft.x27538

    - -modifyworld.items.have.x27538

    - "-modifyworld.items.craft.x27538:*"

    - "-modifyworld.items.have.x27538:*"

Craft permission will prevent players to craft it and if they can somehow get it, it will instantly delete it. And it works.

[AdrenalineON]

>not disabling reactors

There's the cause.

[pherce]

1. Modifyworld supports metadata fine.

2. Deployers and turtles behave as players. Unless you /op them and give them all permissions, they are bound to the same restrictions as any players.

3. Modifyworld have "have" permission, which will delete item as soon as player moves it into hotbar, if player is not allowed to use it.

For example here are our permissions for the watch of flowing time:

    - -modifyworld.items.craft.x27538

    - -modifyworld.items.have.x27538

    - "-modifyworld.items.craft.x27538:*"

    - "-modifyworld.items.have.x27538:*"

Craft permission will prevent players to craft it and if they can somehow get it, it will instantly delete it. And it works.

Again, if you use a project table it's easy to still craft the item. Modifyworld will not remove it from your hand until you interact. Mercurial eyes and lenses don't require an interact (like flint) to work. If you don't have NoItem, you will be exploited through ModifyWorld.

[matejdro]

Again, to quote myself:

Modifyworld have "have" permission, which will delete item as soon as player moves it into hotbar, if player is not allowed to use it.

[pherce]

Try it man. Deop yourself, have your mouse on spot 1, have spot 1 clear, visit a PROJECT table (not crafting) and you CAN craft the item and drag it into spot one. It will not remove the item until you interact.

[matejdro]

I have already tried it many times. And as soon as I move mouse wheel to change selected slot, it will disappear. Maybe you have it turned off in config?

[pherce]

That's your problem, don't move the mouse wheel. Have your mouse already selecting an empty spot, like spot one. Drop the item into spot one and voila. No interacting/scrolling is done so the item will remain.

[matejdro]

Yes, that way it will not remove it. But when you do ANYTHING (interact with anything, move mouse wheel, reconnect etc.) it will disappear.

I have also tested NoItem quickly and it have same behavior (or I am not able to configure it properly). It's just very costly for plugins to keep checking hotbar when nothing is happening.

[pherce]

That is true, but some items could ruin your map before the item is purged. I like NoItem because it can prevent people from doing things like wearing banned armor. I'm not sure if its the mod that auto-equips gear (InvTweaks), but players used to be able to equip it until we got NoItem.

[matejdro]

I have also tested NoItem quickly and it have same behavior

It was not deleted/moved until I moved mouse.

[pherce]

I did find another plugin that prevents it from going into your hand. It did not support damage definers though... Let me look it up for anyone who is interested.

http://dev.bukkit.org/server-mods/itemcontrol/

This will instantly push the item over one slot. As soon as you scroll over ModifyWorld will do its job.

[Abysinian]

I got NoItem as suggested and removed ModifyWorld and it seems to be working a treat, definitely better than MW. Cheers.