[SEC/MECH/FUN] PreciousStones - Block Area Proteciton System [BukkitDev]

Discussion in 'Archived: Plugin Releases' started by phaed, Jan 18, 2011.

Thread Status:
Not open for further replies.
  1. Offline

    phaed

  2. Offline

    Axrael999

    phaed, I love you.
    loading 2.7.1 now
     
  3. Offline

    M1sT3rM4n

    That was the one key thing that I realized after breaking a few of them with the super pick axe:p
     
  4. Offline

    Axrael999

    Keep getting that error on 493. I may have to edit my config file tho because I had different blocks set for different things.
     
  5. Offline

    piousminion

    I've been getting that too. Even when I use stock config without changes.
     
  6. Offline

    Axrael999

    i have default config and im getting "cannont protect air"
     
  7. Offline

    Josch

    Since 2.7.1 I always get "Unprotectable block [whatever I am placing it on] bypass-protected"
    Here is my config:
    Code:
    {
      "unbreakable-blocks": [
        41
      ],
      "saving": {
        "purge-backups-after-days": 7,
        "frequency-minutes": 5
      },
      "log": {
        "pvp": false,
        "bypass-destroy": true,
        "bypass-unprotectable": true,
        "fire": true,
        "entry": false,
        "destroy-area": false,
        "bypass-delete": true,
        "conflict-place": true,
        "bypass-pvp": true,
        "place": false,
        "unprotectable": true,
        "destroy": false
      },
      "bypass-blocks": [],
      "settings": {
        "drop-on-delete": true,
        "sneaking-bypasses-damage": true,
        "public-block-details": true,
        "off-by-default": true,
        "disable-alerts-for-admins": true,
        "allowed-can-break-pstones": true,
        "disable-bypass-alerts-for-admins": false
      },
      "unprotectable-blocks": [],
      "force-field-blocks": [
        {
          "breakable": true,
          "slow-damage": true,
          "radius": 5,
          "block": 91,
          "title": "Jack-o-Death"
        },
        {
          "breakable": true,
          "title": "Glow-of-Life",
          "radius": 5,
          "block": 89,
          "slow-heal": true
        },
        {
          "prevent-place": true,
          "farewell-message": true,
          "prevent-fire": true,
          "prevent-explosions": true,
          "title": "City Protection",
          "nameable": true,
          "prevent-unprotectable": true,
          "prevent-destroy": true,
          "radius": 20,
          "custom-height": 15,
          "welcome-message": true,
          "block": 56,
          "guard-dog": true
        },
        {
          "prevent-place": true,
          "farewell-message": false,
          "prevent-fire": true,
          "prevent-explosions": true,
          "title": "Grief Protection",
          "nameable": false,
          "prevent-unprotectable": true,
          "prevent-destroy": true,
          "radius": 3,
          "custom-height": 10,
          "welcome-message": false,
          "block": 57,
          "guard-dog": false
        },
        {
          "prevent-place": true,
          "prevent-fire": true,
          "prevent-explosions": true,
          "title": "Entry Bouncer",
          "prevent-unprotectable": true,
          "prevent-destroy": true,
          "prevent-entry": true,
          "radius": 5,
          "block": 22,
          "guard-dog": true
        },
        {
          "prevent-place": true,
          "farewell-message": true,
          "prevent-fire": true,
          "prevent-pvp": true,
          "prevent-explosions": true,
          "title": "Peace Keeper",
          "nameable": true,
          "prevent-destroy": true,
          "radius": 10,
          "welcome-message": true,
          "block": 19
        }
      ],
      "warn": {
        "pvp": true,
        "entry": true,
        "fire": true,
        "instant-heal": true,
        "slow-heal": true,
        "destroy-area": true,
        "place": true,
        "unprotectable": true,
        "slow-damage": true,
        "destroy": true
      },
      "notify": {
        "bypass-destroy": true,
        "place": true,
        "bypass-unprotectable": true,
        "destroy": true,
        "bypass-place": true,
        "guard-dog": true
      }
    }
    Normal non Admins just get "Cannot protect [block placing on]"

    Console says e.g.
    Code:
    20:55:22 [INFO] [ps] M1n3M4st3r attempted to protect an unprotectable block [GRASS|22923 70 22943]
    
    Disabling off-by-default or adding some block as unprotectable changes nothing!

    edit:
    Also with /ps off I can't place any of the ps stones in a forcefield...
    I want to be able to bypass-place them as regular stones (I have * permission)
     
  8. Offline

    phaed

    Change log
    Version 2.7.2
    • Fixed bug with unprotectable blocks
    Gonna check this out.
     
  9. Offline

    MacVaultDweller

    Have you set up PS so that it doesn't need permissions to run yet ?
     
  10. Offline

    phaed

    Not yet
     
  11. Offline

    Axrael999

    any news on the "2011-03-07 14:14:29 [WARNING] Plugin 'PreciousStones' (ver 2.7.1) is registering events before it is enabled. It may be misbehaving and the author needs to fix this." text on server startup?
     
  12. Offline

    phaed

    GroupManager or Permissions? Are you using the Help plugin?
    [MERGETIME="1299557761"][/MERGETIME]
    GroupManager or Permissions? Are you using the Help plugin?
     
  13. Offline

    piousminion

    Using latest "Permissions" and latest Help.
     
  14. Offline

    Seldron

    Hi phaed,

    I just updated to the latest version and PS deleted 2 of my fields I set up as admin saying they where orphaned.
    These fields where ment to protect the starting point of our world and if I'm not mistaken where overlapping with other fields of the same type still present in this area.

    I just want to know how PS determines if a field is orphan. I would rather not have this feature at all since we are only around 10 players and it's not that difficult to maintain these fields there. Is there an option to switch off deletion of orphaned PS fields?
     
  15. Offline

    tommytony

    Hi, just a heads up.

    I'm running CB 511 and I've run into this issue:
    • ps is on, I place down a glowstone
    • oops, I just wanted a regular glowstone
    • /ps off
    • break the glowstone (maybe with superpickaxe form WorldEdit, which could be the problem)
    • From then on, the glowstone keeps working (I get a "*healing*" message) even though it's not in the forcefields.txt files.
    • Also, even after a reconnect, I can't put down new glowstones ("Can't put down force field here!") even though /ps off.
    Thanks.
     
  16. Offline

    phaed

    I'll make this an option on the next version. Basically what PS does goes through all the cordinates in the save files where there are supposed to be pstones, and looks in the world and compares the type of block it finds in that coordinate with the type of blocks defined in the config file as fields and ubreakables, if it finds that the block is not one of the configured pstones types, it removes the field associated with it. This is a basic cleanup check to make sure there arent any orphan fields around without a source pstone generating them. These ophaned fields happen in for instance when you use WorldEdit's superpickaxe to remove a pstone and the field stays in place. That is an orphaned field. Or when you remove the pstone plugin, then remove some pstones that had fields, and then add the plugin back later and the save files still think theres supposed to be some pstone blocks there so it has fields for them. Now with the check for orphans in place, these orphaned fields get deleted from the world on every server start.

    There must have been somethign wrong with those fields you had there, either you changed the config, or you made them manually using the save file without them being configured in the config file.
    [MERGETIME="1299607699"][/MERGETIME]
    Yea shouldnt be deleting pstones with superpickaxe. Either way once you restart your server, that orphaned field will be deleted automatically. I will add code to check for and clean up orphaned fields in the area before placing a new pstone.
     
  17. Offline

    Josch

    Two things I'd like to have.
    First and more important to me would be a ingame command to check for orphaned fields. Sometimes it happens that someone removes a PS with the Superpickaxe or VoxelSniper. It is possible to remove the field by placing the same stone with VoxelSniper and removing it with the normal pickaxe, but it is a lot of work.

    The other thing that is not so important but maybe something to consider for the future is upgrading of fields.
    There should be a way to keep old fields with their settings, but change the settings of new placed blocks of the same type.
    e.g. maybe I don't want users to be able to protect very big areas anymore, but I don't want old protected areas to be without protection.
     
  18. Offline

    phaed

    The first one im implementing for next version. The second can already be done, once you place a pstone its dimensions are stored on the seave files individually. You can change the dimentions in the config and those will be used for any new fields placed, but old ones will retain their dimentions.
     
  19. Offline

    Collinm

    Hey Phaed it's collinm from SL.

    What people are doing now with gold blocks are finding holes in the adminium and just covering the gap with gold, creating a vault with 1-2 blocks.
     
  20. Offline

    phaed

    Nothing much could be done about that.
     
  21. Offline

    Bill Warner

    don't know how hard it would be, but I always have a hard time visualizing what is protected. A way to temporarily turn all blocks in a protected zone to glass (or other block) and back would be very interesting. I'm finding it sometimes difficult to not overlap in tighter areas.
     
  22. Offline

    phaed

    You must not have read the Scoping section of the Original Post. Scoping was put in place for the very reason of overlapping tighter areas. And by the way, overlapping is a good thing if you own the overlapped fields.
     
  23. Offline

    LordJason

    I'm guessing you are already aware of this. But just in case...
    Code:
    [WARNING] Plugin 'PreciousStones' (ver 2.7.2) is registering events before it is enabled. It may be misbehaving and the author needs to fix this.
    
    On server startup, bukkit 493
     
  24. Offline

    Bill Warner

    You were right on the scoping part, I did miss that section, I was doing similar but naming an area and then seeing if placing the new stone took the default name or the renamed area's name. Scoping will make it much easier. It still doesn't help in visualizing the area though. Often times I bury the pstones and don't remember exactly where they were placed. If I could stand in a protected area and turn on non-air blocks to glass I could see how deep, how big, the actual shape, etc the area is. If the feature is unwanted by most I would understand, just wanted to chime in as one who would like something similar.

    I realize overlap is usually a good thing, but I'm also using the fields to name areas so people get messages like "entered spawn castle" "entered general store" "entered firehouse" etc... so I don't always want them to overlap even if I own them all.
     
  25. Offline

    phaed

    I'll look into this
    [MERGETIME="1299688756"][/MERGETIME]
    Change log
    Version 2.8
    • New pstone Pocket Snitch! /ps snitch, preciousstones.benefit.snitch
    • Admin command /ps clean - which cleans up orphaned fields on command
    • Fixed up Air of Atlantis code so that air doesnt run out in laggy servers
     
  26. Offline

    enkryptor

    I've downloaded PreciousStones2.8.zip, but it still says "[PreciousStones] version [2.7.3] loaded"

    Code:
    01:17:37 [INFO] [PreciousStones] version [2.7.3] loaded
    01:17:37 [INFO] [PreciousStones] version [2.7.3] 'Help' isn't detected. No /help support
    01:17:37 [INFO] [PreciousStones] loaded 0 unbreakable blocks
    01:17:37 [INFO] [PreciousStones] loaded 0 forcefield blocks
    01:17:37 [WARNING] Plugin 'PreciousStones' (ver 2.7.3) is registering events before it is enabled. I
    t may be misbehaving and the author needs to fix this.
    01:17:37 [WARNING] Plugin 'PreciousStones' (ver 2.7.3) is registering events before it is enabled. I
    t may be misbehaving and the author needs to fix this.
    01:17:37 [WARNING] Plugin 'PreciousStones' (ver 2.7.3) is registering events before it is enabled. I
    t may be misbehaving and the author needs to fix this.
    01:17:37 [WARNING] Plugin 'PreciousStones' (ver 2.7.3) is registering events before it is enabled. I
    t may be misbehaving and the author needs to fix this.
    01:17:37 [WARNING] Plugin 'PreciousStones' (ver 2.7.3) is registering events before it is enabled. I
    t may be misbehaving and the author needs to fix this.
    01:17:37 [WARNING] Plugin 'PreciousStones' (ver 2.7.3) is registering events before it is enabled. I
    t may be misbehaving and the author needs to fix this.
    01:17:37 [WARNING] Plugin 'PreciousStones' (ver 2.7.3) is registering events before it is enabled. I
    t may be misbehaving and the author needs to fix this.
    01:17:37 [WARNING] Plugin 'PreciousStones' (ver 2.7.3) is registering events before it is enabled. I
    t may be misbehaving and the author needs to fix this.
    01:17:37 [WARNING] Plugin 'PreciousStones' (ver 2.7.3) is registering events before it is enabled. I
    t may be misbehaving and the author needs to fix this.
    01:17:37 [WARNING] Plugin 'PreciousStones' (ver 2.7.3) is registering events before it is enabled. I
    t may be misbehaving and the author needs to fix this.
    
     
  27. Offline

    HotelErotica

    Getting that exact same error.
     
  28. Offline

    phaed

    Reuploaded, thanks. Wow that registered event warning is driving me insane, noone knows what it is. Is PS working even though you see those msgs?
     
  29. Offline

    HotelErotica

    @phaed
    Everything seems to work but commands. Also i have another error that completely locks up the server. I think it is caused when someone dies in range of the glow stone healing effect. Also this happened to a user in the nether if that matters or not


    Code:
    14:53:59 [INFO] tehdelta took a leap of faith
    14:53:59 [SEVERE] java.lang.IllegalArgumentException: Health must be between 0 and 200
    14:53:59 [SEVERE]       at org.bukkit.craftbukkit.entity.CraftLivingEntity.setHealth(CraftLivingEntity.java:38)
    14:53:59 [SEVERE]       at net.sacredlabyrinth.Phaed.PreciousStones.managers.EntryManager$1.run(EntryManager.java:77)
    14:53:59 [SEVERE]       at org.bukkit.craftbukkit.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:122)
    14:53:59 [SEVERE]       at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:345)
    14:53:59 [SEVERE]       at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:272)
    14:53:59 [SEVERE]       at net.minecraft.server.ThreadServerApplication.run(SourceFile:366)
    14:53:59 [SEVERE] Unexpected exception
    java.lang.IllegalArgumentException: Health must be between 0 and 200
            at org.bukkit.craftbukkit.entity.CraftLivingEntity.setHealth(CraftLivingEntity.java:38)
            at net.sacredlabyrinth.Phaed.PreciousStones.managers.EntryManager$1.run(EntryManager.java:77)
            at org.bukkit.craftbukkit.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:122)
            at net.minecraft.server.MinecraftServer.h(MinecraftServer.java:345)
            at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:272)
            at net.minecraft.server.ThreadServerApplication.run(SourceFile:366)
    
     
  30. Offline

    phaed

    Just added a fix, redownload 2.8, shouldn't happen any more.
     
  31. Offline

    HotelErotica

    @phaed
    Not sure if you had fixed this or not but still getting this error :( It only seems to stop commands from working.

    Code:
    2011-03-09 15:14:07 [WARNING] Plugin 'PreciousStones' (ver 2.8) is registering events before it is enabled. It may be misbehaving and the author needs to fix this.
    2011-03-09 15:14:07 [WARNING] Plugin 'PreciousStones' (ver 2.8) is registering events before it is enabled. It may be misbehaving and the author needs to fix this.
    2011-03-09 15:14:07 [WARNING] Plugin 'PreciousStones' (ver 2.8) is registering events before it is enabled. It may be misbehaving and the author needs to fix this.
    2011-03-09 15:14:07 [WARNING] Plugin 'PreciousStones' (ver 2.8) is registering events before it is enabled. It may be misbehaving and the author needs to fix this.
    2011-03-09 15:14:07 [WARNING] Plugin 'PreciousStones' (ver 2.8) is registering events before it is enabled. It may be misbehaving and the author needs to fix this.
    2011-03-09 15:14:07 [WARNING] Plugin 'PreciousStones' (ver 2.8) is registering events before it is enabled. It may be misbehaving and the author needs to fix this.
    2011-03-09 15:14:07 [WARNING] Plugin 'PreciousStones' (ver 2.8) is registering events before it is enabled. It may be misbehaving and the author needs to fix this.
    2011-03-09 15:14:07 [WARNING] Plugin 'PreciousStones' (ver 2.8) is registering events before it is enabled. It may be misbehaving and the author needs to fix this.
    2011-03-09 15:14:07 [WARNING] Plugin 'PreciousStones' (ver 2.8) is registering events before it is enabled. It may be misbehaving and the author needs to fix this.
    2011-03-09 15:14:07 [WARNING] Plugin 'PreciousStones' (ver 2.8) is registering events before it is enabled. It may be misbehaving and the author needs to fix this.
    
     
Thread Status:
Not open for further replies.

Share This Page