Migration guide
2.0 -> 3.0 Update
I'm sorry for this major update, as I know that every major update requires you to reconfigure the files. Especially for users who have just purchased plugins and completed configuration. I have concentrated all the major update suggestions from the past six months on this update. To reduce the difficulty of migration, I created this guide and provided commands to automatically convert old data and configurations into new configuration format. Please patiently follow the instructions to complete the migration. If you encounter any problems, we are willing to assist you on Discord.
Stop the server and back up the plugin data folder
delete the plugin data folder
Run the server and generate the new plugin data folder
[IMPORTANT] Put the crops_itemsadder.yml or crops_oraxen.yml in /plugins/CustomCrops/ folder
Run command /customcrops convert <tripwire/item_frame> [Note: choose the argument according to the crop mode you are using in 2.0 version]
Get the config in 3.0 format in /plugins/CustomCrops/converted folder and edit it according to your needs because the convert is not 100% accurate.
Put the crop config files in /plugins/CustomCrops/contents/crops/ folder
[Some default config changes] Pot: "pot" -> "dry_pot" "watered_pot" -> "wet_pot" If you want to use the old name, edit them in /plugins/CustomCrops/contents/pots/default.yml Fertilizer: "quantity" -> "yield_increase" "gigantic" -> "variation" "retaining" -> "soil_retain" "speed" -> "speed_grow" It's advised to edit the new generated files and type in your IA/Oraxen item id.
[IMPORTANT] Run command /customcrops migrate, and just wait for the migration done! You must run the command after you finished converting the configs. Otherwise some data would be ignored and can't be migrated.
Restart the server and enjoy.
Q&A
Q: If I was using 2.0 packs before. Do i need to do any changes to IA/Oraxen configs if I want to use 3.0 plugin? A: You can do that but it's not necessary if you converted 2.0 customcrops configs by following the migration guide. But if you want to use 3.0 default configs, it's advised to use the new 3.0 resource pack to prevent some duplicated actions (For example ItemsAdder drops the seeds and CustomCrops spawns another seed). The only difference is that the effect system which used to be configed in IA/Oraxen is configed in CustomCrops now
Last updated
