Change Log: 1.0.11

Orphaned fields (an orphan field is a field that has no block) will now be removed from the list of blocks.

Some examples of how this could happen:

• If the block was placed in a WorldGuard region, Domain may register the field before WorldGuard cancels the block place event. This causes a field to be created with no block.
• If a block was placed and then WorldEdit is used and it removes the block using //set (or similar)
• The block was created, then destroyed when Domain was not active (for whatever reason)

Removing the orphaned fields does not remove them from the database, so it is possible to fix an orphaned field by placing the block type back in the same location. When Domain starts, the console will report all the orphaned fields that have been removed.



If I was to place a diamond block (which is what is being used for a City field) back at location 224, 79, -505, then after the next restart, this would no longer be an orphaned field.

A future change will allow admins to purge an orphaned field from the database (not implemented yet).