A good resource for providing a breakdown of feudal lands, and if you're unused to the feudal system, it provides great background. I think its math could be better organized so that the income and expenses are put next to one another, however. The Stronghold Builder's Guidebook from 3.5 ed, for example, just presumes income and expenses match unless there's a special feature of the stronghold itself, and you get a clearer sense of what you're paying for with the expenses as functions of your stronghold require set numbers of workers. Used together, however, if DM and players aren't afraid to break out an accounting book, this could be a really interesting means of producing a stronghold.

The examples are a little confusing, however. There are way too few sheep producing income for how many acres they were placed upon, for example, and I don't know why the priest is getting 46 acres of land for his service. How much annual salary is an acre of land worth?

I'd suggest expanding this to other cultures, such as Dark Ages pagans or other "barbarian" tribes, or Iqtas or other Asian systems, for players who aren't always stuck in Fantasy Europe.

While this will probably only help you as a player or DM in a VERY limited sub-set of playstyles, this sort of pure world-building fluff (if sadly unofficial) is the sort of thing that makes a nice read for any player who just likes taking a deep dive into the worlds presented in D&D itself. Free and fairly short and straightforward, this is a fun way to get you to consider some of the practical "real-world" implications of certain aspects of game mechanics (like Common being multiversal) that can possibly let you blow the mind of the guy who thinks he's the jaded metagamer who likes pointing out how gamey everything is. The one complaint I have is that the in-universe author is a lillend, a strongly-chaos-aligned outsider, yet speaks as though outsiders are strange and mortals are normal, or that (LE) devils aren't the absolute antithesis to everything that constintutes her being while having at least some commonality with a (CE) demon.

Well, you get what you (are minimally required to) pay for. It's literally a list of the names of 100 herb-type plants, with no means of segregating out which ones grow in which environments, any suggestion of what they could be used for, or even what they ARE. If you want that, do your own research... at which point, you're doing all the work this random chart was supposed to help you avoid.

While obviously different players have different tolerances for this sort of thing, I found any capacity to imagine myself in the place they were describing irreparably shattered by the fact that all the characters are not even thinly disguised characters from Back to the Future with their personalities and roles intact. (The innkeep is BiffTON Tannen, the womanizing bully, who presumably winds up in a pile of manure at some point.) This means I can't use the characters as they are presented, and would have to create whole new ones from scratch to fill this town... which makes it useless as an aid, becuase other than the NPCs, there is only the vaguest and most generic details familiar to anyone who's seen a castle town portrayed in any other setting. Even the map is essentially an oval wall with the same house copy-pasted and even facing the same direction.

I rather like this mini-delve because it can kind of serve as a better "random encounter" I can have any overland-travelling party stumble across rather than the formal quest it's presented as. I'd suggest the writers focus on making more "accidental side-quests", rather than having plot hooks, because two-page dungeons are too short to really hang a session on, but are perfect to have a random potentially interesting thing happen when an overland trek needs to be spiced up, or to make the players bust down a wall in their fortress's basement, and discover there's a crypt with undead down there.

That said for this particular dungeon, there's sort of a problem in that you've basically resolved the only non-player-created problem as soon as you defeat the first monster, and everything else is friendly. It's an open invitation for the players to screw something up and then suffer consequences for it... but there's no help with the consequences or stats or other mechanics for the sealed evil in the can if they let it into the world, so it's the set-up for a interesting finger-wagging punishment for bad player behavior lacking the actual punishment. If the consequences had at least suggestions for how it can be implemented, I'd give a more whole-hearted endorsement.