Tome of Beasts 2 bug?

[TheGreenHag]

Hi folks,

The tome of beasts 2 loads as a reference module...this causes your DM story notes to be full of spam from the book.

Should this book not load as a supplement - the same way the other kobolt books work, i.e tome of beasts 1, creature codex.

thanks!

[Zacchaeus]

Welcome to FGU.

It doesn't matter whether something loads as a supplement, reference, or adventure all story entries (if there are story entries in the module) in any book will populate the story list. I can't say why the Tome of Beasts 2 is listed as a reference, but even if it were listed as something else then the story entries will be added to your story list. I'll ask the developer whether the designation should be changed for this one; but ultimately it won't change anything in your campaign.

The only thing I'd say is do you need that module open when you are actually playing your campaign? If not then closing it before play starts would be the solution.

[TheGreenHag]

Would be great if the book worked like their other ones i.e not spam the dm notes. Guess your right and can just unload the module.

[drempel]

Would be great if the book worked like their other ones i.e not spam the dm notes. Guess your right and can just unload the module.

If there's records from particularly noisy modules with records you want to keep, you can usually just drag and drop them (making a copy) for your prep or what not. Then unload the noisy module.

Like, for an NPC I want to use, I'll make a copy of it, and its associated image record, set the copies reference to the image to the new copy, and then close the module. It'll still find the raw image and token assets in the module even if it's not opened.

Downside is that the copy won't receive updates if there's updates to those modules. But if it's working as is, the updates probably aren't required, but just nice to have (this works well with stuff that's been released for a long time that obviously isn't going to get any more work done on it).

For stuff I want to use a lot that from a noisy module, or just weirdly setup module, I do the above in a "personal home brew campaign" and then export it as a module to load in the main games. Still finds the assets if you own the original module and haven't loaded it.