Change Log 1.7.6

Purge Command
[USE WITH CAUTION]

Currently, if you have expire_blocks: true in your config file and a valid number in the block config for number of days, after the owner has been offline for that number of days, the field is deactivated, leaving a plain block. If the player rejoins, on the next reload, the field should mark as active again. However, with many players never coming back, there is the potential on busy servers for a large number of expired fields being read on startup.

As a player (with domain.admin permission) or console, you can now use:

/domain purge_list

This will output a list of fields that are not currently active into the console, like so:



You can then manually remove them if you feel you want to.

From the console however, you can use

/domain purge

This will automatically delete the files without further confirmation. This can ONLY be run from console, and CAN NOT BE UNDONE! It'll look something like this, so you'll have a log of what was removed.



I would very much recommend backing up your Domain folder before running either command. (Actually, I'd recommend pushing it out to a zip file or similar about once a week anyway)

Once the files are deleted, there is no going back, so if a player comes back 2 minutes after you purge.. their field will be gone.

Bug Fixes

While using a helpful servers Domain folder for my purge testing, I came across several errors during the load process where the world the field was created in doesn't exist. In this case, they have a world called spawn, and my test server did not, which resulted in numerous null errors. These have all been tightened up, if you delete a world and you had a field there, you'll now receive an error that looks like this, instead of a random null error



Locked_to was sometimes throwing an error as well, this was due to an invalid type cast, that has been corrected.

Finally, with debug mode on, rent_until was throwing an error if the field was not rentable, if it isn't rentable, it just won't add the fields now and the debug message is gone.

Upgrade Instructions:

Backup your Domain jar and your Domain folder (seriously, do it)

Replace your jar with the new copy, and add the following to the lang.yml file