Change Log 1.2.0

This is the largest single update to Domain so far, there are a lot of changes (listed below) - If you are upgrading from an existing version, please be sure to backup your Domain folder before upgrading.

• A LOT of under-the-hood changes to improve stability
• Domain will no longer use a SQLite database for storing data, it will instead move to yml files in the Data folder
• Domain.db data will automatically convert to the yml files - however, any blocks saved where the world no longer exists or some other important issue (missing required fields) may cause a conversion failure. It is VITALLY important that the Domain folder is backed up prior to the update. If you run into issues with some fields not updating, then roll back the change and contact me via Discord for assistance.
• Once the server stops after first run after the update the Domain.db file will be renamed to prevent the plugin from attempting to re-convert the fields.
• The users data is now saved to users.yml
• The gui section of the config.yml has been moved to gui.yml in order to prevent the config.yml file from being cluttered
• The flags section of the config.yml has been moved to flags.yml for the same reason
• gui.yml and flags.yml will auto-generate on startup, if you have any translations in the existing config.yml file, you will need to manually copy these changes over
• debug_log and debug_to_file have been removed from the default config.yml file. /domain debug is the preferred method for entering debug mode.
• The blocks section has been removed from the config.yml file - instead all block configuration files in the Blocks folder will be loaded on startup
• The Domain menu > Edit > Open for commands has been removed and replaced with Administrator commands. These commands require domain.admin permission. These options include, setting Teleport location, making the Domain block into an admin block, and setting enter/leave run commands.
• /domain admin_block, /domain flag *, /domain enter_command, /domain leave_command, /domain tpto have all been disabled
• /domain flag add * has been removed, instead admins can add new flags to a field by using the Add Flag button in the flag menu. This is the preferred method for creating custom blocks for administrator usage (ie. portals)

• The following flags have been added:
  * PREVENT_SPAWN_HOSTILE - Prevents hostile mobs from spawning inside the field (zombies, skeletons etc.)
  * PREVENT_SPAWN_NONHOSTILE - Prevents non-hostile mobs from spawning inside the field (cows, pigs etc.)
  * PREVENT_SPAWN_PILLAGER - Prevents Pillagers from spawning inside the field
  * PREVENT_SPAWN_RAVAGER - Prevents Ravagers from spawning inside the field
  * PREVENT_SPAWN_EVOKER - Prevents Evokers from spawning inside the field
  * PREVENT_SPAWN_ILLUSIONER - Prevents Illusioners from spawning inside the field
  * PREVENT_SPAWN_VEX - Prevents Vexs from spawning inside the field
  * PREVENT_SPAWN_VINDICATOR - Prevents Vindicators from spanwing inside the field
  * PREVENT_SPAWN_WANDERING_TRADER - Prevents wandering traders & their llamas from spawning inside the field
  * PREVENT_BAZAAR_BUY_BY_NONALLOWED - Prevents non-allowed players buying from Bazaar chests inside the field
  * PREVENT_BAZAAR_CREATE_BY_NONALLOWED - Prevents non-allowed players creating new Bazaar chests inside the field
  * PREVENT_BAZAAR_REMOVE_BY_NONALLOWED - Prevents non-allowed players removing existing Bazaar chests inside the field
  * PREVENT_BAZAAR_SELL_BY_NONALLOWED - Prevents non-allowed players from selling to a Bazaar chest inside the field
  * HEAL_ALL_PLAYERS - Heals any player inside the field

• Changes to any Domain fields will be saved immediately instead of waiting for the hourly check for edited fields

• This is the final feature update that will include ShopChest integration, any future feature updates will support Bazaar for shop integration only

Update FAQ

I'm new to Domain, do I have to do anything with this change to .yml files?
- No, this is just for existing users. New users will just automatically use the flat file storage

What is this yml file thing?
- It is just a way to store files in a structured way, if you don't know what it is, don't worry about it

Why the change to .yml files?
- The Domain.db file could get stuck into a persistently locked state which could cause the server to crash as Domain was unable to write to the database. This became more urgent in 1.2.0 when immediate saves of the domain block changes was implemented (rather than startup + 1hr cycle).

Why not move to MySQL?
- Not everyone wants to use MySQL

But I do want to use MySQL!
- MySQL support IS coming, but not in this update. Future versions will support flat file and MySQL only.

What if the conversion from database file to flat-file doesn't convert all my blocks?
- It should, with a few notable exceptions. For example, any invalid block, such as those created in a world that doesn't exist will NOT copy over.

But I'll lose all those blocks that didn't convert if you stop using the Domain.db file, can't you just leave it?
- No, just so we don't keep trying to convert already converted data. This is why it is VERY important to backup your folder first. If you have issues with the conversion, roll the change back and let me know and I'll help with getting the files generated.

I can read and edit .yml files, right? So I can make changes directly in the file!
- You can, but I will not support manually edited files
- I'll answer that a second time in bold just so it really sinks in.. I will NOT support manually edited files. If you break a file by editing it, your best bet is to delete the file and recreate the block in-game.

This is too complicated!
- Feel free to join the Discord and I'll be happy to try and help you out with the update

I used ShopChest, what happens in the next feature update?
- The next feature update will remove the SHOPCHEST_* flags - the blocks that have them will continue to work but will not actually do anything with those flags. Your shops will continue to work, but without the Domain restrictions for buying/selling etc.

Why are you removing ShopChest in the next feature release?
- Supporting third-party plugins adds complexity and increases development time. As Bazaar is now released, there is no need to support multiple shops.

I don't have Bazaar and I don't want to pay for it!
- Bazaar is NOT required for Domain, it is an optional extra only. Not sure that Bazaar is for you, contact me on Discord and I'll be happy to let you try it out

I don't want to install Domain as I'm not sure it is right for me!
- You can contact me on Discord for a free copy to test with (this is at my discretion and I reserve the right to refuse to provide a copy - test copies do NOT mean you are added to the Buyers list)

I found a bug!
- Please contact me with a message on Spigot or on Discord and I'll do my best to help you out.

Want to try Domain?
You can test Domain on play.ibexmc.com - the official showcase for Domain, Bazaar and Myriad Clans - you might find some surprising uses for Domain that you've never really considered (portals, healing monuments, catching falling players, paying players for reaching an area etc.)