7.2

Details

  • Filename
    PreciousStones.jar
  • Uploaded by
  • Uploaded
    Jan 17, 2012
  • Size
    294.71 KB
  • Downloads
    1,084
  • MD5
    58a0cd4ed245739cf960da722b2a1b72

Supported Bukkit Versions

  • CB 1.1-R1

Changelog

Version 7.2 - Works with CB 1.1 only

  • Added CB 1.1 support
  • Migrated to new bukkit event system for faster events
  • Fixed bug where PS would break if vault was not installed
  • Fixed autodownload url of vault, last one was 404
  • Disabled fields no longer heal you or damage you or accelerate you
  • Hopefully speed up /clean by nor explicitly loading and unload chunks
  • Fixed a block deletion error bug
  • Added dump of the actual SQL query whnever an error happens to easily find future SQL errors
  • Fixed default permissions issue (reported by bPermissions users)
  • /ps setname [name] now only sets the name of one field, use with -o flag to set all overlapped fields /ps setname -o [name]
  • Streamlined /ps menu a bit
  • Feeding, Airl, Healing, and Repair now only work on allowed players of the field. (before they used to work on anyone, now if you want that you must allow *)
  • Fixed bug where one would die in a field and come back and still be affected by it
  • Added 'prevent-teleport' field flag prevents non-allowed players from teleporting into the field
  • Added 'preciousstones.bypass.teleport' permission, to bypass the restriction
  • Added 'allowed-only-inside' field flag. Which holds a list of fields (titles) that this field can be placed inside of, the field will not be palceable outside of the fields in the list. (i.e. Adding "allowed-only-inside: [City Protection, Peace Keeper]" to the GodStone would make it so it could only be placed inside these two types of fields.) Note: The no-conflict flag must be used in conjunction with this flag. Note2: This is not a parent-child relationship for subplots.
  • Added 'preciousstones.bypass.allowed-only-inside' permission, to bypass the restriction
  • Added 'required-permission' field flag. With this you can make it so the field can only be placed by those with this permission. (i.e. required-permission: preciousstones.vip, would make it so only those with this permission can place the field). If one does not have the permission it will just place an ordinary block without any error messages.
  • Added 'allowed-worlds' field flag. It is a list of allowed worlds the field can be placed in (i.e. allowed-worlds: [world, nether]). If one does not have the permission it will just place an ordinary block without any error messages.
  • Added 'preciousstones.bypass.world' permission, to bypass the restriction
  • Thats right motherfuckers.

Compiled and tested for initialization and hooking into Vault, performance beyond this is untested currently.