PreciousStones - Back under the development of phaed

phaed has decided to take back the reigns of this plugin, so please refrain from posting in this thread any further. Instead, go here: http://forums.bukkit.org/threads/in...-v4-3-self-service-grief-protection-935.1034/

 

@aPunch

Hmm, I will try unziping again. Thank you for your time and good luck as the new mantainer.

 

Any way to disable mob spawn? I'm looking for a good plugin that could do that, preferably self-serve.

 

I'm thinking about adding a stone that prevents mobs from spawning. Any suggestions on which block?

 

Netherrack may be a good choice

 

No offence aPunch but could you kick out the no-mob flag THEN worry about assigning it to a block by default
And I agree with MacVaultDweller, Netherrack

 

I know that this plugin does not recommend using build 709 and that 709 is not a recommended build, but should this work on it? If I place a gold block and do /ps info I'm told that I'm not in a forcefield.

 

I personally want to have no-mob-spawn in my city... so, if anything, you could add that flag to the diamond block.

I do like the idea of netherrack as well, I just think its a tad to common for a PStone and may throw things out of balance.

 

Any way to turn off the *healing* spam from Glowstone? I like the function, just not the chat spam.

Great plugin, keep it up!

 

Ok i want to use this plugin, but i have a little question.
When a User has no Precious Stones Permissions at all, will he be able to place the Blocks used for the Fields and use them like always just without the Field?

Edit:
Never mind im a Noob. Found the answer myself.

 

is this 714 compatable? just ditched residence plugin (the config file made my eyes go crosseyed lol) in favour of this but need one thats 1.5 compatable ...is this the one lol

 

Turn off the alert message in the config and it won't spam

 

@aPunch request for a anti-teleport zone block/option

 

It does work with 714, but I'm not officially supporting it until a new RB is released.

 

I take it you want to allow entry from people just walking in as the no-entry flag blocks TP as well

 

for some reason I cant get this to work with permissions. here is my yml file.

Code:

groups:
    Guest:
        default: true
        info:
            prefix: ''
            suffix: ', the Guest'
            build: false
        inheritance:
        permissions:
            - 'foo.bar'
    Builder:
        default: false
        info:
            prefix: ''
            suffix: ', the Builder'
            build: true
        inheritance:
            - Guest
        permissions:
            - 'bar.foo'
            - 'preciousstones.benefit.*'
            - 'preciousstones.whitelist.*'
            - 'SelfClosingDoors.*'
            - 'SimpleHome.*'
            - 'SpawnX.spawn'
            - 'Stargate.*'
    Trusted:
        default: false
        info:
            prefix: ''
            suffix: ', the Trusted'
            build: true
        inheritance:
        permissions:
            - 'bar.foo'
            - 'preciousstones.benefit.*'
            - 'preciousstones.whitelist.*'
            - 'preciousstones.special.*'
            - 'preciousstones.bypass.*'
            - 'preciousstones.alert.*'
            - 'MotherNature.*'
            - 'SelfClosingDoors.*'
            - 'SimpleHome.*'
            - 'SpawnX.*'
            - 'Stargate.*'
    Admins:
        default: false
        info:
            prefix: ''
            suffix: ''
            build: true
        inheritance:
        permissions:
            - '*'
            - 'preciousstones.benefit.*'
            - 'preciousstones.whitelist.*'
            - 'preciousstones.special.*'
            - 'preciousstones.bypass.*'
            - 'preciousstones.alert.*'
            - 'preciousstones.admin.*'
            - 'preciousstones.override.*'

anyone care to help me out?

 

I'm confused. How exactly do you allow people to the cannon/launchers when, in order to be close enough to do so, YOU are launched?

 

From outside of the field, type /ps allow [player] while you are aiming at it.

 

I'm getting some nasty console errors and nothing works.

Currently running CentOS 5.5 with MCMA, Bukkit 720, Minecraft 1.5_02

Errors-
http://pastebin.com/GRZHpAdy

Any ideas?

 

That's what I tried first. It was silently failing.

The plugin cannot create its dependent files. Does it have write access to the folder?

 

can we have it so doors,levers and buttons cannot be used?

 

There's nothing in place that would prevent it from doing so. All other plugins are able to create directories without issue. Is the .jar file download corrupted perhaps?

 

Every time I use a PS command the chat reterns /ps help displays pstones commands, even when using /ps help. Also I can't use any pstones, what am I doing wrong? I have found this in builds 684, 714 and 726.
Here are my Permissions

Code:

groups:
    Guest:
        default: true
        info:
            prefix: ''
            suffix: ''
            build: true
        inheritance:
        permissions:
            - 'foo.bar'
    Member:
        defalt: false
        info:
            prefix: '&2'
            suffix: '&f'
            build: true
        inheritance: 'Guest'
        permissions:
            - 'foo.bar'
            - 'preciousstones.benefit.*'
            - 'preciousstones.whitelist.*'
    Mods:
        default: false
        info:
            prefix: '&d'
            suffix: '&f'
            build: true
        inheritance: 'Member'
        permissions:
            - 'bar.foo'
            - 'preciousstones.bypass.*'
            - 'preciousstones.alert.*'
            - 'preciousstones.special.*'
    Admins:
        default: false
        info:
            prefix: '&c' [&c]
            suffix: '&f' [&c]
            build: true
        inheritance: 'Mods'
        permissions:
            - '*'

And also when I edit a block I get this in the console
"[SEVERE] Could not pass event BLOCK_PLACE to Permissions"

 

Hey, great plugin, will test it as soon as I can get to my test-server.

I /sign the mob-spawn stuff. I would add it to a city-block.
Maybe you want to take a look at the NoCivilSpawns plugin as the author has some experience with this technique and the load it puts on a server.

 

One feature I've been seeking out for a while now is the ability to make the protection size customizable by the user. Phaed said he liked the idea, but I guess he never got around to adding it.

I envision a "Home Protection" block that has limits on how large or small it can be and the player can set the size to his specific needs. This way a user doesn't have to claim too much or too little space.

Thoughts?

EDIT: the zip appears to be corrupt.

Code:

[~]# unzip ../PreciousStones.zip
Archive:  ../PreciousStones.zip
  End-of-central-directory signature not found.  Either this file is not
  a zipfile, or it constitutes one disk of a multi-part archive.  In the
  latter case the central directory and zipfile comment will be found on
  the last disk(s) of this archive.
unzip:  cannot find zipfile directory in one of ../PreciousStones.zip or
        ../PreciousStones.zip.zip, and cannot find ../PreciousStones.zip.ZIP, period.

 

Well... tried to unzip it and your file is corrupt, downloaded on different pc and different os and it still corrupt. Please fix

 

I will be helping out with bugfixes and feature requests to the project whenever I can. Here are my latest commits:​

• removed guarddog mode for pvp free fields (makes no sense)
• cloaked fields are breakable so they are explodable as well
• fixed the wrong removal of cloaked fields that were uncloaked when the the save files were read back in
• fixed bug where explosions were being nullified wrongly
• added lava place in pvp protected field warning
• prevent projectile attack in pvp protected field
• prevent entity attack in pvp protected field
• prevent lava and lava bucket place in pvp protected field
• prevent projectile damage inside pvp prevention fields
• fixed the menu/snitch list cutoff bug (hopefully)

​

 

Whenever I place a gold block it informs me that an unbreakable block has been placed, but it doesn't protect blocks around it like it's supposed to. "/ps info" tells me that there are not forcefields around me. This is my console information about Precious Stones:

Code:

2011-04-26 16:16:14 [INFO] [PreciousStones] version [3.2.1] loaded
2011-04-26 16:16:14 [WARNING] orphan unbreakable - skipping [339 113 -29]
2011-04-26 16:16:14 [INFO] [PreciousStones] loaded 0 unbreakable blocks
2011-04-26 16:16:14 [INFO] [PreciousStones] loaded 0 forcefield blocks

This is my Precious Stones configuration file:

Code:

bypass-blocks: [39,40,51,59]             # mushrooms, fire, crops
unbreakable-blocks: [41]                 # gold
unprotectable-blocks: [54,58,61,62]      # chest, workbench, furnaces
tool-items: [269,270,271,273,274,275,277,278,279,284,285,286,290,291,292,293,294]   #tools
cloak:
    cloakable-blocks: [54,58,61]         # chest, workbench, furnace
    cloak-blocks: [1,2,3,4,5,7,17,20,43,45,49,60,78,80,82,87,88] # everyday solid materials
    viewing-radius:
        min: 5
        max: 20
        default: 7
force-field-blocks:
    -
      title: "Protection"
      block: 41
      radius: 7
      custom-height: 8
      prevent-fire: true
      prevent-place: true
      prevent-destroy: true
      prevent-explosions: true
      prevent-unprotectable: false
      guard-dog: false
      nameable: true
      welcome-message: false
      farewell-message: false
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: true
    slow-heal: true
    slow-damage: true
    give-air: true
    launch: true
    cannon: true
    mine: true
settings:
    public-block-details: true
    allowed-can-break-pstones: true
    sneaking-bypasses-damage: true
    drop-on-delete: true
    disable-alerts-for-admins: true
    disable-bypass-alerts-for-admins: false
    off-by-default: false
    lines-per-page: 12
saving:
    frequency-minutes: 5
    purge-backups-after-days: 7

 

I'll be getting a release out with these changes soon.

 

You cannot have the same block type be an unbreakable block and a field block. They are mutually exclusive. Your blocks can be either unbreakable (which cant be broken but project no fields), or field type (which by default cant be broken but project a field out).

Remove 41 from the unbreakable list.

 

Version 3.4

-tons of bugfixes by Phaed (thanks!)
-correct version number in plugin.yml