Open dev-nolant opened 3 hours ago
It is interesting that the migration failed. Was there an error in the console after the first time running the newest version? I see the issue with changing the file now. I am going to publish a hotfix in a moment.
Describe the bug When you uploaded the updated today, it noticed my config file was outdated, and suggested I updated. I updated, and it didn't update any of my yml configs, so I just deleted the CustomNPCs folder and allowed it to create fresh. After doing so, it worked for one launch, where I was able to create NPCs. After a restart, the config file was fine, but the npcs.yml was reverted to 1.6 which caused the plugin to disable itself.
I fixed this by manually going into npcs.yml and setting the version to 1.7 at the top. Upon restart it changed this version to 1.8, and worked.
To Reproduce Steps to reproduce the behavior:
Expected behavior I expected the npcs.yml to update accordingly after introducing the new plugin jar.
Screenshots N/A
Server(please complete the following information):
Additional context N/A