Table of Encounters Based on (all) CRs but...

[Tempered7]

Anyone knows a free and/or paid (except from forge/paypal) module that includes random encounter tables from MM and other books with NPCs based on CR?

I searched everywhere and the closest one is Rob Twohy's Random Monster Tables in dmsguild.
But it isn't updated for Mordenkainen Presents Monsters of the Multiverse, and I don't have Volo's Guide & Tome of Foes. (they are delisted)

Free version (if any) is for the guide I'm writing btw. Jimsocks' Content Creator has some but it doesn't link to monsters.
The Adventurer's Toolbox links to monsters and based on all Terrain/CR but it's not free.

Links to even SRD would do.

[LordEntrails]

You already listed all the ones I know

I wonder if someone could make an extension to do this dynamically based upon what content is loaded/what's available in the current NPC list.

[Tempered7]

You already listed all the ones I know

I wonder if someone could make an extension to do this dynamically based upon what content is loaded/what's available in the current NPC list.

That's also what I searched for. Thanks anyway.

There is one ext that I cant remember the name but it can produce encounters based on 1 to 6 PCs. I have no idea if it's from loaded content or from something else.
If there was a free one I was going to show how to use it in an article about Cheapest and Quickest Way to Play Solo.
It'll be a time-based (w/ Clock Adjuster ext) method that will roll encounter tables automatically as the PC travels.

I covered the free & paid non-combat encounter parts. If only Rob's modules would be updated
The Toolbox part 1 & 2 have also links to the delisted modules.

***

If I decided to do it for the guide, using only the SRD monsters, could I publish the module of the guide without infringing any copyrights? If so, how to do that?

[LordEntrails]

If you use Random Encounters, you can use the variable "$PC" to determine number of NPCs or each row. Such as "2*$PC" or "$PC+1" etc. I think it gets the counts PC that are added to the party sheet (marching order) rather than the Combat Tracker, but not certain. Brief info on it in the Wiki under random encounters.

[Tempered7]

If you use Random Encounters, you can use the variable "$PC" to determine number of NPCs or each row. Such as "2*$PC" or "$PC+1" etc. I think it gets the counts PC that are added to the party sheet (marching order) rather than the Combat Tracker, but not certain. Brief info on it in the Wiki under random encounters.

Ah yes. Good idea! I was thinking about adding it to the Solo Guide. So some soloists might play 2+ PCs.

And if I only use SRD content, would I break any copyright laws? Or what would I need to do to add these encounter tables in terms of copyright?

[LordEntrails]

If you only use SRD NPCs then you are not breaking any opyright.

[Tempered7]

Excellent news!

But I kinda stuck on the method I should use to make them.

I am doing it for the use with Clock Adjuster by pr6i6e6st (Travel Manager). It requires to create 1 table for each paces of travel: slow, normal, fast.
The problem is to make the tables CR appropriate for any level of solo PC. If I add all CRs in 1 table, it wouldn't be level appropriate for low and high solo PCs.

I read some articles on the wiki but nothing comes up as a solution.

How to make one table that is level appropriate for all levels?

Note: B = Battle, E = Non-Combat Encounter chances in the pic. You just press the slow/nmormal/fast travel button underlines with red and it rolls automaticlly.

[tjlee]

Perhaps these (free) resources might be of use:

OSRIC modules under OGL 1.0a

[Tempered7]

Perhaps these (free) resources might be of use:

OSRIC modules under OGL 1.0a

Thank you! I checked the tables in GM modules and finally found a solution.

I'll prepare 4 different random encounter tables for each level tier, and players will change the appropriate one's name so Clock Adjuster can use it.

These Osric tables are like a lesson in table creation in FGU. I didn't know we can output the result into Encounter window, it's super easy to use.
And they even use tables within tables. This cracks the code and enables me to use 1 table to rule them all