Skip to main content

Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines

I have tried a dozen times, resetting my computer in between attempts, but it won’t let me save additions to the bestiary. 
I make a monster, name it and add the picture. Close the bestiary, open it and the monsters still there. I save my campaign, close DMHelper and reopen it and my monster is not in the bestiary anymore. Again I’ve reset my computer between attempts and have saved multiple times both through the file menu and with Crtl S. 

In my current homebrew campaign I can’t really be making 4-5 homebrew monsters before every session only to have to do it again next week. 

(+1)

Happy New Year! 

You're absolutely right, you should not have to recreate your monsters in the Bestiary! I suspect this is a known issue and I can offer two potential solutions: 

1) work around: move your Bestiary (and any images) to a new location on your harddrive, then go to the options menu and select the new Bestiary location. I recommend to do this without having any campaign open to avoid damaging the campaign monster links.

2) message me on discord, I can share a link to the engineering build where the bug has hopefully been fixed. It would be great if you could try out that. we version and give feedback whether it does indeed fix the issue.

Your first fix works. Thanks a lot! Thanks for the really quick reply too!
This is a guy who makes quality software and cares about it!

Great!

I’m also having this issue - I’ve learned to export a copy of the bestiary every time I add a monster to it, which works but does mean that if I miss doing that, I’m out work. Even saving it in another location doesn’t seem to help.

That seems to be a very unsatisfying process! What version of the DM Helper are you using? Could you join our Discord server? Then we could chat through how to find a good solution for you.

I just went to check that it was still happening and the monster I created stuck around, so whatever was causing the issue seems to have fixed itself. I did run a bunch of updates on things recently so maybe something there caused an issue. All good now!

Great news! Do let me know if anything further pops up!