Why are the Manuals Tables read only now?

[JohnFintch]

Hi, i notice today that the tables of the dnd 5e manuals are read only now. Witch is very annoying to use now because I cant change the output right away and if they are for encounters the encounter created still only read make it impossible to use unless you copy. I hope for a fix.

[Zacchaeus]

What tables are we talking about and are we talking about the 2024 rulebooks or the legacy rulebooks?

[JohnFintch]

Legacy in my case. For forest encounter 1-4 cr table of xanatar

[Zacchaeus]

Ok, yes. Since the module creation method changed a couple of years ago the way exporting works has changed and as a consequence the tables are now locked along with the rest of the reference material. If you need to change a table then make a copy and use the copy. Or roll the locked table (you can click the eye icon if you want to keep the result and roll secret from players); and then just either generate the encounter that is produced if it's a random encounter or drag the NPC link from chat and drop it into the Combat Tracker.

[JohnFintch]

I get that. What I find very uncomfortable is that when you generate the encounter the encounter it's also read only, which means that you can't decide where prelocate the npc in that. I must copy the encounter as well, which made the all thing a nightmare for beginners to find out. My was a suggestion about userfriendlyness. Thank anyway for the hardworking you all do.

[Zacchaeus]

Ok, I've re-exported the module as not read only. However I may have to revert that depending on what feedback I get since doing this may well break links in some or many campaigns. I've put the amendment through as a hot fix so it should go live later today.

[JohnFintch]

Thank you very much that gonna make the use of it very intuitive. Hope that it'll not brake anything so it could stay like that. As always big compliments for listen your community and to make my gdr tables so easy to run, since I began my adventure with FG.

[Zacchaeus]

I've updated it again :)

On the advice of Trenloe I've changed the way that the module is made not read only - so that should not result in broken links.