This might not be the best place to ask questions. But I never got answer to a PM send to your team's manager according to dev.bukkit .
Also, there isn't any other way to communicate with your team other than PM, or this Issue tracker. At least, that I know off.

I looked through your code and I only want confirmation. If it isn't true what I am saying, please explain further.
Here it goes:
When I use the addSourceField and the deleteSourceField methods from ForceFieldManager. Will it disable the field/cuboid without permanently deleting it from the database?

Further background:
I am working on a plugin that adds upkeep-costs to preciousStones. But as far as I can see, the ForceFieldManager doesn't have an option to just disable a Field/Cuboid. Neither does Fields/Cuboids have a "disabled" tag available.
When the plugin detects a placement of stone that needs upkeep it has to disable the original Field. When a chest and a sign is placed (with the usual distinct txt-line) it will activate the stone until the chest runs out of the required resource.
I want to do this as less 'invasive' as possible, for now an extra table is added to save the status of the field on shutdown (disabled/enabled/igonred (no upkeep) ). I hope this is the only one table I need.

Hope to hear from you soon.
And thanks in advance,
Sciblon

Added field.setDisabled(boolean) on 7.0.5

Thanks for adding such a feature if it was because of my question. I had been developing this before 7.0.5 and just missed the update I guess.

My plan is to make this a serperate plugin as an exercise. When it has all functionality I want it to have I will try merging it with preciousStones itself and send it up as a pull request.

Thanks again.

Yea just added it cause of your comment so that you can disable fields easier.

Awesome, cant wait to try out the functionality :)