Openning Bestiary for new worlds not working.

[Mermut]

I've got a couple of campaigns ongoing. Since the last update, my worlds that I'd already started populating the bestiary can still open the bestiary. In worlds that did NOT have anything in the bestiary, I cannot open the bestiary via the button from the journal notes. Also the Open Bestiary macro is not showing up in the compendium. In configure settings, I can open the vague description settings in worlds with a populated bestiary but NOT in worlds with an empty bestiary.

[WBHarry]

I just released v0.8.8 which should fix these problems. If you can update and verify I'd appreciate it 😄

[Mermut]

The macro is back, but none of the rest of the functionality for new worlds has changed. Neither using the macro nor clicking on the button in the journal note section of the foundry interface opens the bestiary for worlds with empty bestiaries. Similiarly, the vauge description settings in the configure settings for the module doesn't open for new worlds.

All of the old functions and the new ones DO work for worlds where I've got populated bestiaries.

[WBHarry]

Could you open up the console and run: game.settings.get('pf2e-bestiary-tracking', 'version') and post the version number here? I'm curious if the migration is stuck on an old number because of some error. EDIT: It's curious since I created a new world, enabled the mod and had no issues 🤔

[Mermut]

I'll check with a new world, the others are existing worlds (one is my testing world and the other is one where the party doesn't do many recall knowledge checks so I hadn't populated the bestiary when I activated the module originally)

Added Note: Interesting. It works on brand new worlds for me too. I'll see if I take out the mod and exit the world completely rather than merely reloading and adding it again will fix the two where it's not working.

Unsurprisingly, that didn't work.. I'm wondering if there's a settings file somewhere that is funky since settings tend to be remembered even when you deactivate and reactivate a module.. Completely deactivating all mods except bestiary didn't change anything. Going to see if I can find the 'settings file' in the world folder.

--- Yup, it was something in the settings file. I cleared the settings directory in the testing world and then reactivated the module. Once I did that the Bestiary came up as it should.

[WBHarry]

Settings are definately remembered, but they shouldn't have to be cleaned out. Rather, it's a good thing they're there incase the module is enabled again.

The reason I was curious about game.settings.get('pf2e-bestiary-tracking', 'version') on failing worlds is because that will show how far the migration scripts managed to run - and that could be different than the module version if there are errors. IE, maybe it failed to migrated from 0.8.7.2 to 0.8.8

[WBHarry]

I've been trying to create old worlds and then migrating them up to current, but I can't seem to replicate these errors.

If you'd be able and willing to zip up one of your failing worlds, then I could have a look at these errors and see what's going wrong 🧐

[Mermut]

Whatever it was, the most recent update (0.8.8.2) is now working in the one remaining world that it wasn't working in. I just loaded the module back into it and was going to see if I could get any error generation and it loaded up correctly.

I'm not sure what changed... but at least the bug seems to have been smooshed.

I am loving all of the new additions and features. Thanks for your work and creativity :)

[WBHarry]

I just released v0.8.8.3 that should remove any further migration issues aswell. Glad you're enjoying the module 🫶