[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

    phaed

    Im gonna try to fix this and the broken commands tomorrow and release 2.2
     
  3. Offline

    mudzereli

    Am I missing some sort of option to allow overlapping fields with different field types? I use this for SMP and I have players protect their own houses with diamond blocks. I want them to be able to keep a slow-heal block inside of their house, or line their doorways with an entry prevention block. Right now the fields don't stack properly. Do I have something configured wrong? I loved this plugin back in 1.43 because it actually allows me to assign a real "value" to blocks like Iron and Lapis.
     
  4. Offline

    Mr_Mellow

    so im guessing this isnt working at the moment? because i ran it on my server and i got errors
     
  5. Offline

    PopeUrban

    Correct, as of 428 a lot of stuff isn't working/throwing errors. Might want to hold off on updating our live server until people can get some updates out.

    Oh, Phaed, quick request!

    How about a flag that *only* prevents placing blocks with PS values? I could use that to set up some hardline DMZs around the spawns on my server. The problem is that with the current setup, CERTAIN USERS (they know who they are) have taken to just walling in the spawn with no-move wards (that's what we call pstones) The official server answer to all PS blocks is explosives, and the answer to no-move blocks is building cannons and firing those explosives through the field. Thus, we have working siege warfare mechanics, which are the primary metagame of the server thanks largely to your plugin.

    However, when the users are walled in the super-carebear spawn ward they don't have any build permissions, and are thus unable to build cannons to attempt to break the blockade. They're also unable to place the special block arrangements I have set up to create portals and ship in building materials, or warp to an allied base or whatnot.

    So, basically, I'm looking for an anti-pstone pstone setting to create unclaimable zones of contention in specific spots, thus preventing users from walling in my safe zones and creating an unwinnable "fish in a barrel" situation.
     
  6. Offline

    Josch

  7. hello,

    I always similar, nobody backs up of my PreciousStones: ' (
     
  8. Offline

    SweetCraft Girl

    HOW - do you completely STOP the SPAM?
    I have turned every guard-dog notice to FALSE and added 'guard-dog: false' to every Pstone i have made. Yet, i am flooded non-stop by every single p-stone message across the world which makes MC completely unplayable for me as a GM/admin. In fact, EVERYONE gets spam reports from their P-stones. :( I have all the notify/warns set to FALSE; and yet, nothing but destroy/place flooding everywhere on everyones screen.

    The entire NOTIFY system is an RP immersion *destroyer*. No one should know that someone has hit their pstone, or tried to cross it or anything. I am working really hard to try to cobble together a fully immersive RP system and text spam telling people who is at their home or hitting their items or trying to enter is not only anti-RP, but *extremely disruptive to all socializing, conversing, interacting with items, etc.*

    Is there a way to shut off all p-stone reporting?

    Here are my config settings:

    log:

    entry: false
    fire: false
    pvp: false
    place: false
    destroy: false
    destroy-area: false
    unprotectable: false
    bypass-pvp: false
    bypass-delete: false
    bypass-destroy: false
    bypass-unprotectable: false
    conflict-place: false
    notify:
    place: false
    destroy: false
    bypass-place: false
    bypass-destroy: false
    bypass-unprotectable: false
    guard-dog: false
    warn:
    entry: false
    fire: false
    pvp: false
    place: false
    destroy: false
    destroy-area: false
    unprotectable: false
    instant-heal: true
    slow-heal: true
    slow-damage: true
    settings:
    public-block-details: true
    sneaking-bypasses-damage: true

    I would greatly appreciate a fix to this. We are running CraftBukkit: 361

    Every single p-stone interaction in the world is shot across my screen and its driving me berko :(
     
  9. Offline

    phaed

    Added this to new version
     
    SweetCraft Girl likes this.
  10. Offline

    mrgreaper

    working on build 421? (wondering what plugins 1.3 has broken lol)
     
  11. Offline

    phaed

  12. Offline

    mrgreaper

    to be honest chap i was joking, but it seems many plugins do infact work with the new 1.3 compatable craftbukkit so once i have finished copying files etc i will let you know if it works (if i can get a player to test it...only had a few hundred emails "server says outdated!!!1111!!"


    oh and i commend you for being one of the first plugin devs to support the recommanded builds once this 1.3 fiasco is all done and dusted it will make us server admins lifes so much easier
     
  13. Offline

    Verrier

    I am finding that on the latest craftbukkit version (423, compatible with 1.3) players can destory blocks in pstone areas, but not place them. (Using PStones 2.2)

    Is anyone else also having this issue? Just want to make sure it's not something on my end.
     
  14. Offline

    mrgreaper

    i stopped mid updating when i found out permissions 2.0 dont work right (grants permission to everyone)
     
  15. Offline

    kovk

    Thanks so much phaed for this awesome plugin :) I wanted to share the PreciousStones settings I carefully designed for my server in the hopes that other admins will find it useful. Also, i've included an in-game reference for players for use with MCDocs plugin.

    My goal was to allow players to construct protection in a balanced and logical way with regard to resources. All protection blocks may themselves be destroyed by players. If players do not wish to participate in pvp they must hide their protection blocks behind protected blocks. Blocks are separated into two categories, deeds and fortifications. Deeds are more expensive while fortifications may be created more easily.

    Deeds - Blocks that define area ownership
    • Iron Block - restrict build/destroy in 15x15 cube
    • Gold Block - restrict build/destroy in 29x29 cube
    • Diamond Block - restrict build/destroy in 51x51 cube
    • Redstone Ore - restrict build/destroy in 129x cube (not obtainable in game)

    Fortifications - Blocks that give extra protection
    • Obsidian - disable creeper/tnt explosions in 51x51 cube
    • Lapis Block - disable fire in 51x51 cube
    • Bookshelf - disable PVP in 51x51 cube
    • Mob Spawner - build/destroy/fire/explosion/pvp in 29x29
    Bricks can only be destroyed by the player who placed them.


    kovk's config.yml (open)

    bypass-blocks: [37,38,39,40,59]
    unbreakable-blocks: [45]
    unprotectable-blocks: []
    force-field-blocks:
    -
    title: "Iron Deed"
    block: 42
    radius: 7
    breakable: true
    custom-height: 15
    prevent-place: true
    prevent-destroy: true
    welcome-message: true
    farewell-message: true
    nameable: true
    -
    title: "Gold Deed"
    block: 41
    radius: 14
    breakable: true
    custom-height: 29
    prevent-place: true
    prevent-destroy: true
    welcome-message: true
    farewell-message: true
    nameable: true
    -
    title: "Diamond Deed"
    block: 57
    radius: 25
    breakable: true
    custom-height: 51
    prevent-place: true
    prevent-destroy: true
    welcome-message: true
    farewell-message: true
    nameable: true
    -
    title: "Platinum Deed"
    block: 73
    radius: 64
    breakable: true
    custom-height: 129
    prevent-fire: true
    prevent-place: true
    prevent-destroy: true
    prevent-explosions: true
    nameable: true
    -
    title: "Town Grant"
    block: 52
    radius: 14
    breakable: true
    custom-height: 29
    prevent-fire: true
    prevent-place: true
    prevent-destroy: true
    prevent-explosions: true
    prevent-pvp: true
    welcome-message: true
    farewell-message: true
    nameable: true
    -
    title: "Anti-Explosive Fortification"
    block: 49
    radius: 32
    breakable: true
    custom-height: 65
    prevent-explosions: true
    -
    title: "Anti-Fire Fortification"
    block: 22
    radius: 32
    breakable: true
    custom-height: 65
    prevent-fire: true
    -
    title: "Anti-War Fortification"
    block: 47
    radius: 32
    breakable: true
    custom-height: 65
    prevent-pvp: true
    log:
    entry: false
    fire: true
    pvp: false
    place: false
    destroy: false
    destroy-area: false
    unprotectable: true
    bypass-pvp: true
    bypass-delete: true
    bypass-destroy: true
    bypass-unprotectable: true
    conflict-place: true
    notify:
    place: true
    destroy: true
    bypass-place: true
    bypass-destroy: true
    bypass-unprotectable: true
    guard-dog: true
    warn:
    entry: true
    fire: true
    pvp: true
    place: true
    destroy: true
    destroy-area: true
    unprotectable: true
    instant-heal: false
    slow-heal: false
    slow-damage: true
    settings:
    public-block-details: true
    sneaking-bypasses-damage: false

    MCDocs protection.txt (open)

    &eCertain Blocks provide protection to player who placed them
    &eDeeds - Blocks that define area ownership
    &cIron Block - restrict build/destroy in 15x15 cube
    &cGold Block - restrict build/destroy in 29x29 cube
    &cDiamond Block - restrict build/destroy in 51x51 cube
    &eFortifications - Blocks that give extra protection
    &bObsidian - disable creeper/tnt explosions in 51x51 cube
    &bLapis Block - disable fire in 51x51 cube
    &bBookshelf - disable PVP in 51x51 cube
    &cMob Spawner - build/destroy/fire/explosion/pvp in 29x29
    &eAll protection blocks can be destroyed by other players
    &eunless they are hidden behind protected blocks
    &eBricks can only be destroyed by the player who placed them
    &e/ps allow [player] - Add player to the allowed list
    &e/ps remove [player] - Remove player from the allowed list
    &e/ps setname [name] - Set name of force-fields you're in

    Enjoy!
     
    SweetCraft Girl likes this.
  16. Offline

    phaed

    http://forums.bukkit.org/threads/ad...-9b-because-permissions-is-past-326-405.4723/

    GroupManager:
    405 compatible
    imports permissions/config.yml automatically
    --- merged: Feb 23, 2011 5:23 AM ---
    Thanks! Nice setup ;)
     
  17. Offline

    Verrier

    Just to let you know, it looks like the issue with being able to destroy blocks MIGHT be bukkit related, if infact it is not just me having the problem.

    [00:16] <@Tahg> so, isOp does seem to be broke for plugins

    Edit Update: isOp() fix does not fix being able to destory protected blocks
     
  18. Offline

    phaed

    Can anyone break the blocks? Or just ops?
    --- merged: Feb 23, 2011 8:10 AM ---
    Permissiosn 2.1 is out, I have it working on my dev server with cb 424 and pstones 2.2, working very well.
     
  19. Offline

    xXFreeekXx


    Anyone can destroy these blocks...

    Also, even though the console says it loads the protection blocks, none of them seem to work in game...


    I can right click a pre-1.3 diamond, and it does nothing, yet if i put a new diamond down, it will protect the area...

    But the protection only protects placing of blocks, not destroying.


    I've tried the following setups...

    permissions 2.0, pstone 2.2, cb 424
    permissions 2.1, pstone 2.2, cb 424


    Same effect with both.
     
  20. Offline

    Verrier

    Any user can break the blocks. I would assume it is because of this:
    http://leaky.bukkit.org/issues/476#change-1426

    Mostly because there isn't even a message that pops up saying "Blahblah broke a block in protection area". Are you sure that on your dev server blocks cannot be broken? Preventing placement works fine, as do all other pstone functions. I only noticed block breaking not working.
     
  21. Offline

    mwdennis

    I didn't see a post about this in the thread, but is there any way to import the unbreakable.bin file from 1.43 to be used in 2.2? I have users that have created large castles of pure obsidian (one of the unbreakable blocks I have set). And it would kill them to have to basically break it all down and recreate it just so PS can catalog the blocks in the new save file.
     
  22. Offline

    Verrier

    What I did to convert my old file:
    - Copy protection.bin and make a backup
    - Download / install older craftbukkit (I used build 326)
    - Launch older craftbukkit w/ PStones version 2.0
    - PStones will auto convert / update the protection.bin into forcefield.txt and unbreakable.txt.. removing protection.bin
    - Copy / backup forcefield.txt (and check to see if it's empty*)
    - Update pstones (v 2.2) and craftbukkit to latest
    - Launch server, make sure it loads your fields.

    *Note: I had issues converting protection.bin, for some reason it wouldn't convert on the machine my server normally runs on, so I had to copy the protection.bin file locally and do the conversion, then upload the forcefield.txt file to the server. Despite the two servers using the exact same configuration, craftbukkit, and pstones. My guess it was a permissions issue.

    If it failed to convert, copy the backup protection.bin file back and try again with less plugins.. different version.. or something. Absolutely worst and last case I can try to convert it for you if you PM me, but I'm not sure if it'll work without your world file, since I don't know how the conversion actually takes place.
    --- merged: Feb 23, 2011 9:20 PM ---
    Phaed:

    It looks like the mods that have fixed (didn't test?) the block breaking stuff are using the BlockBreak event now..
    https://github.com/Hidendra/LWC/commit/6c6a90530adee50a0e978c57113e11ed1657986c

    Perhaps something to consider if bukkit doesn't (want to?) fix it on their end.
     
  23. Offline

    IOn Vash

    why does the plugin still spam admins with messages?
     
  24. Offline

    phaed

    There are settings to turn this off now:
    disable-alerts-for-admins: true
    disable-bypass-alerts-for-admins: false

    Alternatively you can use Permissions 2.1's new permission exclusion feature to exclude admins from the alerts:

    http://permissions.nexua.org/
    (look in last code example)
    --- merged: Feb 23, 2011 10:41 PM ---
    Thank you!!! I was going nuts! New version shall be up shortly.
     
  25. Offline

    mrgreaper

    the author of permissions 2.1 quit didnt he?
    we just moved our server to groupmanager

    looking fwd to the new version of PS! :) love this plugin
     
  26. Offline

    phaed

    Redownload 2.2
    It contains the fix for the block breaking of pstones.
     
    Verrier likes this.
  27. Offline

    mrgreaper

    thank you
     
  28. Offline

    Verrier

    Thanks Phaed, works like a charm :)
     
  29. Offline

    mrgreaper

    both me and another admin cant place blocks down in other peoples forcefield which is wierd as we should be able to
     
  30. Offline

    IOn Vash

    Its also still spamming admins with messages even though I removed permission for preciousstones.alert.* and also my config is set up like this.

    log:
    entry: false
    fire: false
    pvp: false
    place: false
    destroy: false
    destroy-area: false
    unprotectable: false
    bypass-pvp: false
    bypass-delete: true
    bypass-destroy: true
    bypass-unprotectable: true
    conflict-place: false
    notify:
    place: false
    destroy: false
    bypass-place: false
    bypass-destroy: false
    bypass-unprotectable: false
    guard-dog: false
    warn:
    entry: false
    fire: false
    pvp: false
    place: false
    destroy: true
    destroy-area: false
    unprotectable: false
    instant-heal: false
    slow-heal: false
    slow-damage: false
    settings:
    public-block-details: true
    sneaking-bypasses-damage: false
    drop-on-delete: true
    disable-alerts-for-admins: true
    disable-bypass-alerts-for-admins: false

    I need a fix for this because the spam makes chat unusable.
     
  31. Offline

    Verrier

    If they're regular blocks, make sure you have bypass permissions.

    If they're pstones, you can't have overlapping pstones anymore so it should fail to place unless Phaed changes is so admins placing blocks inside someone elses field auto grants them that block to extend their field.. or something.
    --- merged: Feb 24, 2011 3:46 AM ---
    - I can't seem to get /ps setowner to work
    - Confirming that still spam even with disable-alerts-for-admins: true
    --- merged: Feb 24, 2011 3:50 AM ---
    - disable-pvp: true if this is set, the block can be placed but does NOT create a force field. Bug?
    --- merged: Feb 24, 2011 4:41 AM ---
    Phaed, is it possible that the:
    disable-alerts-for-admins: true flag only disables console alerts and not in game alerts?

    Could you push your source to github again so we can help track down some of these bugs quicker? :)
     
Thread Status:
Not open for further replies.

Share This Page