Bukkit

Version 8 - Subplots are now possible

• 
  
• Removed old style field overlapping. Now fields are independent. (you can still create several fields of the same type and have them touch each other and name them the same and you wont have repeting enter and leaving messages)
  
• Removed field scpoing, that was where you could click on the ground to see the fields that were touching, no longer needed now that overlapping is a thing of the past. Also it was annoying.
  
• Now when you trigger an event (break, place, fire ignite, etc) in an area with several overlapping fields, the smallest one always takes precedence, with the ideas that if there is one huge town cuboid field, and several subplot fields within it, with even smaller subsubplot fields, the smallest field is the one that is gonna be obeyed.
  
• Fields with the 'allowed-only-inside' flag no longer require no-conflict flag, as normal fields can now be sub-plotted.
  
• The parent field can not be removed if it has sub-plotted fields inside of it.
  
• When you create a new field, for example in a city, and your field overlaps a friends field (only possible if you're allowed on your friends field), then your friend will now automatically be allowed into your field as well. This prevents you from your friend all of a sudden not being in control of his own land.
  
• Conflict of interest system will not let you disallow a player from a field if your field is also overlapping one of their fields. (preventing a player from taking control of a friend's land by creating a field that overlaps theirs and then removing them from the allowed list)
  
• Added "Town Protection" and "Town SubPlot" default fields as an example of how to set them up.
  
• Removed word field from certain messages i.e. "City Protection field placed" to "City Proteciton placed"
  
• Added allowed list to right click info
  
• Added ability to use wool colors for pstones. Must use 4 digit numbers. (i.e. 3501 = orange wool) Note: This only works for the 'block' field flag.
  

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.