Bugs found with Server.addArea / Server.removeArea

I'm currently working on my own LandClaim plugin and noticed some things:

- if you use `area.setPlayerPermission` before `Server.addArea`, the permissions are not persisted to the database.
- if you use `Server.removeArea` before removing all player permissions from the area, the permissions stay in the database with no valid area.

Might not be critical but it cost me much time to figure this out

Hey red51 i'm currently experiencing some more issues with the Area API.

I noticed that my rename-area code is only temporary setting the new area name.

area.setName(v);

Also if i do a Server.addArea(area, true); afterwards, it is not reflected in the db file and gone after restart.

The only way i currently experimenting with is to do

area.setName(v);
Server.removeArea(area);
Server.addArea(area, true);

But this comes with an even bigger downside (bug)
The area is removed and readded to the database with the correct name but ingame it is not found by Server.getAllAreas() until the server restarts.

I'm thinking of using my own SQL to update the area names as workaround to fix that but i dont know yet if thats causing any other side-effects.
Using SQL to update name works for now.

Another bug: when deleting an area where the player itself is standing in, the non-area area gets the name of the deleted area instead of "wildernes" for example. Everytime you leave an area the old area name pops up.