[INACTIVE][SEC] AntiGrief v1.2.1 - Anti-Build+Anti-Grief Measures with Polygon Zone Protection [818]

Discussion in 'Inactive/Unsupported Plugins' started by crowebird, Feb 9, 2011.

  1. Offline

    crowebird

    AntiGrief v1.2.1 [Download]
    AntiGrief is a Prevention plugin with multiple aims:
    • Prevent potential griefers.
    • Control who can do what.
    • Give the server owner complete customization.
    • Define limitations based on in game created zones.
    What this means is you have complete control over who can do what on your server.
    • You can allow guests to visit your server without being able to do anything.
    • You can prevent certain actions from being used by anyone or certain groups.
      • This can be done by action, or even by item.
    • It is up to you as the server owner, you can customize every element.
    Features:
    • Prevent/allow any action.
      • Prevent/allow any action with specific item customization.
    • Prevent the use of TNT/Explosions/Fire/Lava/Water.
    • Prevent Mob Targeting (I.e. Prevent griefing via lured creepers).
    • Prevent players from damaging other players.
    • Prevent players from receiving damage in multiple ways.
    • Prevention of the usage of vehicles.
    • Prevent on a per-world basis.
    • Prevent via user defined polygon zones.
    Version 1.2.1:
    • Compiled with 818

    Version 1.3 [coming soon]:
    • Zones now have enter and exit messages
    • New zone commands to add enter and exit message and command to delete zones
    • Ability to prevent explosions in a zone
    • Ability to prevent creature (by type) from spawning in a zone
    • Fixes to zone creation and visualization (unable to break visualizing blocks)
    • Users can only modify the zones they created
    • Ability to modify the area of a zone
    • Can modify points while creating a zone
    • Ability to set default actions allowed inside a zone
    • Slight modification to the main configuration file (prevent_nodes is nodes.prevent again and allow_nodes is nodes.allow again) - this way nodes.prevent/allow follows the same logic as prevent/allow when preventing/allowing an item based on a certain action
    • The ability to disable an item completely outright or by group/user
    • Other fixes/enhancements
    Version 1.0.3:
    • Fixed a logic error dealing with preventing items (<node>.prevent)
    Version 1.0.2:
    • Many bug fixes.
    • Fixed zones - they now work properly and match main configuration format.
    • Changed some nodes around
    • Some changes to config format.
    • Prevent item use added back
    • Fix for door interactions
    If upgrading to 1.0.2+ it is recommended that you let AG re-create your configuration files. I know it is a pain, but the new changes/increase customization required some shuffling/creation of settings that need a new format (mostly re-naming).

    AG requires GroupManager or Permissions although GroupManager is recommended for use with AG!

    Links:
    Wiki
    Download
    Report Issues
    Changelog

    [​IMG]
     
    Hrdkr, xcession and brosef like this.
  2. Offline

    crowebird

    Happy to help Rich :)

    Note -> if you are using the zone protection I realized I broke it somewhere along the way... I am working on a fix, and some new features. I also added new markup for entity targeting to include everything that can attack a player.
    I will also work on more detailed instructions as I know the wiki is ages out of date now.
     
  3. Offline

    crazydog

    So I think I'm not understanding the new config:
    Code:
    buildtrue:
      nodes:
        prevent: []
    buildfalse:
      nodes:
        prevent: ['damage',
          'ignite',
          'creeper',
          'hit',
          'place',
          'use',
          'pickup',
          'vehicle_use',
          'vehicle_move']
      use:
        allow: []
      interact:
        allow: [64, 70, 72]
      place:
        allow: []
    groups:
      User:
        nodes:
          prevent: ['ignite']
      Moderator:
        nodes:
          allow: ['ignite']
      Guest:
        nodes:
          prevent: ['ignite',
            'creeper']
    I'm sure quite a bit of this is wrong, but all I've noticed is that guests are still targeted by creeperes.
     
  4. Offline

    Rich Boos

    Hello again,
    I wanted untrusted users to be able to make a makeshift home from a kit before I let them have buildtrue. In my config I have allow: 04, 05, 324, 323 for the items that are in the kit (stone, wood, a door, and a sign) but no one has been able to place them. So i'm halfway functional because they way I h ave it configured at least they can't break anything, but they can't place the 4 items I want. Could you explain what I am doing wrong again lol?
    Code:
    buildtrue:
      nodes:
        prevent: []
    buildfalse:
      nodes:
        prevent: ['damage',
          'ignite',
          'creeper',
          'hit',
          'use',
          'pickup',
          'vehicle_use',
          'vehicle_move']
      use:
        allow: []
      interact:
        allow: [64]
      place:
        allow: [04, 05, 324, 323]
    
     
  5. Offline

    bLazem

    excellent tool, keep up the great work
     
  6. Offline

    Th4natos

    Okay what must i do, can you give me an example?:
    I use:
    * Permission 2.5.5 (Phoenix)
    * Worldguard
    Groups: Hofnarr, Edler, Baron, Graf, Herzog, Kaiser
    Hofnarr = not build
    Edler+= can build

    my permissions:
    Code:
    groups:
        Hofnarr:
            default: true
            info:
                prefix: '&7[Hofnarr]&3'
                suffix: '&f'
                build: false
            inheritance: null
            permissions:
        Edler:
            default: false
            info:
                prefix: '&7[Edler]&3'
                suffix: '&f'
                build: true
            inheritance: null
            permissions:
    ==the rest, and finally===
        Kaiser:
            default: false
            info:
                prefix: '&6[Kaiser]&2'
                suffix: '&f'
                build: true
            inheritance:
            - Herzog
            permissions:
            - '*'
    Antigrief config = no change, all defaul

    sry 4 me english
     
  7. Offline

    crowebird

    @Rich - so I just tried it out... the code works, but for some reason bukkit is no longer firing the onBlockPlace event, which I am in the process of trying to figure out... never caught it as that code was untouched and worked in the past... so at any rate, I am working on a fix there.

    @crazydog - I'll run some tests and see if it is anything on my end, if I can't find any issues, i'll let you know.

    @Th4natos - so with the default AG config, since Hofnarr has build: false, then all the settings in the default.yml config created by AntiGrief will take place on that user (under the buildfalse nodes):
    Code:
    buildtrue:
      nodes:
        prevent: []
    buildfalse:
      nodes:
        prevent: ['damage',
          'ignite',
          'creeper',
          'hit',
          'use',
          'pickup',
          'vehicle_use',
          'vehicle_move']
      use:
        allow: []
      interact:
        allow: [64]
      place:
        allow: []
    So what this means is, any user/group with build: false won't be able to damage any blocks, ignite them, be targeted by a creeper, attack anyone, use an item (although this is currently broken), pickup an item, or use or move a vehicle.
    They also won't be able to interact with any item (except doors: item 64), and won't be able to place any blocks.
     
  8. Offline

    Th4natos

    Okay, and now.. how i allow to build all other groups?
    all other groups have "build:true" in the permissions. yml
     
  9. Offline

    crowebird

    Then all the other groups can build, AG won't do anything to them...
    If there are certain things you want to prevent on users with build: true you add them to the buildtrue: part of the .yml, but as it stands it does no look like you are trying to prevent builds from doing anything so you should be all set.
     
  10. Offline

    theDuck

    so if the build part of the permissions.yml the part that controls antigrief, what are all the permission nodes for?
     
  11. Offline

    crowebird

    I need to update the wiki. I got rid of the permission nodes as they were a stand in to add customization, but I decided to do everything in the config to keep it all together. Ultimately the new method gives the user more control.
     
  12. Offline

    theDuck

    thanks for the speedy reply

    I have another question... nobody with build rights is able to do anything, except for the admins who i gave '*' permissions. In my frustration i backed up my server files, downloaded the newest craftbukkit build, and worked on debugging the problem. Im not sure if this has anything to do with it, but I am using the pheonix version of permissions (v2.2.5)
    Code:
    plugin:
        permissions:
            system: default
            copies:
    groups:
        Default:
            default: true
            info:
                prefix: ''
                suffix: ''
                build: false
            permissions:
                - '-*'
        Builder:
            default: false
            info:
                prefix: ''
                suffix: ''
                build: true
            permissions:
                - 'general.*'
        Admins:
            default: false
            info:
                prefix: '&c'
                suffix: ''
                build: true
            inheritance:
            permissions:
                - '*'
    users:
        billy:
            group: Builder
     
  13. Offline

    crowebird

    Is this using the default config created by AG? I am able to allow users to build and stop building based on only build: true/false successfully.

    Note that I am working out quite a few bugs that I never caught with the config that is not allowing the customization to work the way I intended.
     
  14. Offline

    theDuck

    It seems to have been the permissions plugin. When I switched to groupmanager, everything started working fine, except for the fact that some people are still receiving messages that they "cannot perform that action" even though it lets them perform it.
     
  15. Offline

    Th4natos

    [qoute]
    Okay, and now.. how i allow to build all other groups?
    all other groups have "build:true" in the permissions. yml​
    Then all the other groups can build, AG won't do anything to them...
    If there are certain things you want to prevent on users with build: true you add them to the buildtrue: part of the .yml, but as it stands it does no look like you are trying to prevent builds from doing anything so you should be all set.[/quote]
    no ->

    Thats its my problem.. all have build:true, but nobody can build.. only headadmins
     
  16. Offline

    Steef

    Zone protection is still not working.

    You have commented out the part in AntiGriefPlayerListener.java, where new Zone-Points can be set, so there is no way to create one without editing config files.
     
  17. Offline

    crowebird

    - Yea, I am aware, and it is probably for the best at this point, I some how broke the re-initialization of zones so once the server was re-loaded or AG was reloaded, your zones would not be re-loaded. Has been fixed, but I am still working on a few other bug fixes, should be a new release later today.

    @Th4natos - not sure why it won't work for you, as I said, will have a new release later today, so hopefully that will fix your issue. I made quite a few changes to the config again to work some of the kinks out.

    Version 1.0.2 Released
    Update to 670 and many other big fixes!

    Note I am working on updating the wiki too.

    --

    Edit: @Th4natos - are you using permissions or groupmanager? If you are using permissions, I wonder if there is a conflict with their built in anti build.

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 8, 2016
  18. Offline

    crazydog

    Alright, trying to block anyone from placing obsidian, but it's not working. What's wrong here?
    Code:
    buildtrue:
      nodes:
        prevent: []
      place:
        prevent: [49]
    
     
  19. Offline

    Th4natos

    Permissions 2.55
     
  20. Offline

    crowebird

    @crazydog - thanks you helped me catch a logic error, is fixed in the new version.

    @Th4natos - got to be it, I am doing all my testing against GroupManager - i'll install permissions when I get the chance and see where (and if) it is conflicting. Got to be their built in permissions, as I only set prevention states, I don't override anything... but with all build: true, not entirely sure, might be a typo in one of your the configs.
     
  21. Offline

    crazydog

    Heh. Glad I could help, thinking I made a mistake. :p

    Ok, here's a question:

    Let's say I want to protect my roads. I've set up zones, and nobody but two groups can place/break blocks. Is there a way to protect the roads from creeper explosions as well?
     
  22. Offline

    crowebird

    So I am only preventing targeting, have not coded anything to prevent the explosion, although it is easy to do. I will include it in the next update!
     
  23. Offline

    crazydog

    Sweet. It's frustrating having to rollback my roads constantly. :p
     
  24. Offline

    jor956

    I set "build" to false in GroupManager, the group can not place blocks, but can still delete them; please help me with this! D:

    This is my default.yml

    Code:
    buildtrue:
      nodes:
        prevent: []
    buildfalse:
      nodes:
        prevent: ['break',
          'place',
          'interact',
          'ignite',
          'target_creeper',
          'target_giant',
          'target_zombie',
          'target_skeleton',
          'target_ghast',
          'target_slime',
          'use',
          'pickup',
          'attack',
          'take_block_explosion',
          'take_contact',
          'take_drowning',
          'take_entity_attack',
          'take_entity_explosion',
          'take_fire',
          'take_fire_tick',
          'take_lava',
          'take_suffocation',
          'take_custom',
          'vehicle_use',
          'vehicle_move']
      use:
        allow: []
      interact:
        allow: [64]
      place:
        allow: []
    What's wrong?

    EDIT by Moderator: merged posts, please use the edit button instead of double posting.
     
    Last edited by a moderator: May 8, 2016
  25. Offline

    crowebird

    Changes buildfalse.nodes.prevent to buildfalse.prevent_nodes (i.e.):

    Code:
    buildfalse:
      prevent_nodes: ['...']
    That should fix your problem!

    [I changed the naming scheme, but I realized earlier today, that I might need to go back to the way it is in your config, but for now make the change I said and you should be all set]
     
  26. Offline

    crowebird

    Hey guys, heads up - I just noticed for zone creation, if you had an item in the first slot before hand (which is where the tool gets placed) - the item does not get replaced on zone completion. Just a warning! It will be fixed in the next update!
     
  27. Offline

    crazydog

    Mine was getting replaced just fine. :p
     
  28. Offline

    crowebird

    Oh, lol well then... I must have had another stick and didn't notice... Out there was nothing in the first slot anyway. Well then, ignore my message everyone :) (I didn't test to verify, went off that assumption)

    Thanks crazydog
     
  29. Offline

    crowebird

    Maybe sometime tomorrow or in the next few days:
    • Zones now have enter and exit messages
    • New zone commands to add enter and exit message and command to delete zones
    • Ability to prevent explosions in a zone
    • Ability to prevent creature (by type) from spawning in a zone
    • Fixes to zone creation and visualization (unable to break visualizing blocks)
    • Users can only modify the zones they created
    • Ability to modify the area of a zone
    • Can modify points while creating a zone
    • Ability to set default actions allowed inside a zone
    • Slight modification to the main configuration file (prevent_nodes is nodes.prevent again and allow_nodes is nodes.allow again) - this way nodes.prevent/allow follows the same logic as prevent/allow when preventing/allowing an item based on a certain action
    • The ability to disable an item completely outright or by group/user
    • Other fixes/enhancements
     
  30. Offline

    Jessicadawn

    Will this work with the new bukkit build? and 1.5
     
  31. Offline

    Bipen

    Help... Please?
    Me and my friends have a private little server we use to play MC with ea. other, and when downloaded CraftBukkit, it came with several built in plugins, which we enjoy and like, but we're having a problem with this Anti-Grief one..
    We didn't choose to turn off TNT, Water, or Lava, it came turned off itself, and we have no clue how to turn it back on... so help please? :)
    When we use a bucket of water or lava, is just dissappears, and when you drop the bucket, you see its full once more.
    And for TNT, when you place it, it just comes back to your inventory...
    Help... Plox.
     

Share This Page