Archfiends of the Nine Infernal Kingdoms

The Nine Infernal Kingdoms are regions of the plane of Maledicium where powerful archdevils have established their domains, pockets of stability and order surrounded by demon-infested chaos. Brief descriptions of these "kings of Hell" and their dominions are listed below (in order of relative power, weakest to strongest).

Note: Each archdevil is listed with aliases as it is ill-advised to say their names aloud, outside the context of a ritual or invocation. To do so is said to invite misfortune upon oneself.

⁜ ⁜ ⁜ ⁜ ⁜

Ilsidris, King of Avernus

The Hawk, the Whisperer

Ilsidris is the ruler of Avernus, and is the third ruler of this kingdom in recent history. He has the form of a human male with a hawk's head, bird wings, and taloned feet. Ilsidris speaks in a sinister whisper, causing feelings of dread and uneasiness to those who hear his voice. The avian archdevil is the weakest of the infernal kings, but he is able to ally and manipulate the others in such a way as to keep his kingdom safe from their depredations.


Avernus looks like a typical temperate region suffering under terrible disasters. River banks are void of water, fields are filled with cracked soil and stunted vegetation, and trees are dying due to a lack of water. Dust devils and tornadoes are common.

Settlements in Mythosa

The Mythosan world map and PDF show and document a number of towns, many cities, three metropolises, and one hamlet. Hopefully it is obvious that this is not the entirety of settlements in the known world; to show every village and town on the map would be major overkill and a lot of unnecessary work (and to be honest, I have no idea where every village or hamlet is; I add them as I need them). That said, there's nothing that documents the specifics of settlements in the context of Mythosa other than the general terms listed in the world guide. This post is intended to clarify that.

There are five types of settlement in Mythosa: hamlet, village, town, city, and metropolis*. On the world map, settlements are shown based on their size (relative to the scale of the map) or their significance. Given that, all the cities and metropolises of the known world are on the map. Regarding towns, the ones that appear on the world map have some particular importance (like Irongate due to its role in trade in the Ruinlands and Avellyn River Valley), but there are many more that do not appear on the map (some can be found in the world guide, such as Aldenshire and Fairhaven in the Ruinlands, but there are still more beyond that). Villages, as one would expect, are numerous, but don't show up on the map or in the PDF; they can be placed anywhere on an as-needed basis. The same applies for hamlets, though they aren't quite as numerous as villages (it's more difficult for smaller settlements to survive the myriad dangers of the world).

Basic settlement population and economic information is shown in the table below**:

TypePopulation (estimated)GP Limit / Available Wealth (GP)
HamletUp to 1005 / 50
Village100 to 50025 / 250
Town500 to 5,000250 / 2,500
City5,000 to 15,0001,500 / 15,000
MetropolisOver 15,00010,000 / 100,000

Specific population numbers aren't usually provided but the table above is useful for getting a general idea of how many people live in a settlement. "GP Limit" and "Available Wealth" are holdovers from 3rd Edition. Nothing more expensive than the "GP Limit" will be found in a particular settlement, and it is also the maximum amount anyone will pay for what the PCs may be selling. "Available Wealth" is the amount of resources available in the settlement - i.e; the PCs can't sell more than that much worth of goods at a single time. Assume it takes about a week for "Available Wealth" to be rebuilt.

I'll have a couple more posts in the future dealing with some additional economic and demographic aspects for settlements, specifically for certain scenarios that may emerge during gameplay.

*: It would be simpler to just use the standard "village/town/city" threesome, but I felt that the huge, sprawling, exceptional cities should have their own category (akin to places like Waterdeep, Greyhawk, Lankhmar, etc.). I added "hamlet" to cover those settlements that are little more than a handful of families and individuals living in a cluster of buildings. I could have encompassed those in "village", but I wanted to balance the low end against the high end (and odd numbers are more interesting than even ones; I may post something about my "groups of three and five" philosophy in the future).

**: I've refrained from applying too many specific details to the settlements since I don't find them significant to actual gameplay. It's more important, for instance, to convey the impression and feeling of a village or city and what might make it unique than it is to know things like exact population numbers (the PCs don't care if a town has 4,500 or 4,700 people in it) or mundane resources (these can generally be inferred from the surrounding geography).

TableSmith 5.2 released

Yes, you read that right - a new version of TableSmith has been released! I realize it's long overdue, and it's not a huge release, but it is something (and finally addresses the folder access problem that's plagued 5.1 since Windows Vista was released).

There are some new features, but this is primarily a technical update to address two things. First, the standard installation puts the program and other "read-only" files into the "Program Files" folder of Windows, while the tables, config file, and other mutable files go into a TableSmith folder in the user's Documents folder. This is the expected installation that Microsoft encourages, and fixes the issue where everything was installed into "Program Files", which then created issues when TableSmith tried to save it's configuration information. "Back in the day" (i.e.; Windows XP and earlier), you could do that, but Vista and later didn't allow for that.

Ironically, while this was the primary reason to update TableSmith, I almost immediately received some resistance to dividing up the installation. Which is why there's a "portable" version that installs everything in the same folder as it did before. This is fine if you know what you're doing; I just hope I'm clear that if you're just using TableSmith "normally", you use the standard install.

The second technical issue was that TableSmith was using the .NET Framework 2.0. Not really that big of a deal, but 2.0 was old even when TS was first released, so I decided to update the required framework version. 4.5.2 isn't cutting edge but it's much more recent than 2.0.

The help file lists the other changes; mainly bug fixes, but a couple enhancements and a handful of net functions.

What's the future of TableSmith? I don't have a roadmap figured out yet, but I'm expecting further updates as time goes on. I'm probably going to be focusing on a port of some kind to iOS (FantasyGen is basically a precursor to that) sooner than later, but the Windows version should continue for the foreseeable future.

Irongate PDF Uploaded

I've uploaded a small (one-page) PDF for the town of Irongate (found in the Ruinlands region) that I put together for one of my current Mythosa campaigns. It can be found on the Downloads page.

Mythosa PDF Updated

I finally updated the Mythosa PDF (available on the Downloads page). When I switched from a static HTML site to Blogger, I obviously wanted to preserve the Mythosa pages. Originally, I just printed the pages to PDF and stitched them together into a single file. This was good enough for a start, but not for the long term.

I took the contents of the PDF, cleaned it up, reformatted it, and reposted it. It still could use some more artwork, but that will come later.

Campaign Setting Formats

While reviewing my backlog of PDFs, I was looking through a small campaign settings book (what and by who is irrelevant). As I'm looking through the Table of Contents, I see the same standard chapter - Races, History, Organizations, Religion, etc. On the one hand, this is a good, boilerplate approach to a setting and organized in such a way as to be easily digested by the reader. But on the other hand, I was thinking, is this the only way? We've been following the same basic template for presenting setting information since the late 70's. It's not bad (I certainly have done and am doing the same thing), but is there a better way?

State of the Site

While there is an "About" page on this blog (link over to the right), I figured I'd post some explanations of what is going on with this blog as well as the old Mythosa site.

Currently, the old website is gone (even after I spent a bunch of time revising it…sigh), and this blog is the Internet home for Mythosa, TableSmith, my iOS apps, and whatever other projects I may be working on. I got rid of the old site for a couple reasons. First, I realized that "fantasy campaign setting" sites really aren't a thing any longer. Most of them are gone, and the handful that remain haven't been updated in years (some have been sitting idle for over a decade). Farland is still going, but it's an exception (and has always been at a higher level of quality than most every other world site, mine included). Other than that, most people have moved their content to blogs rather than static HTML sites.

Now, just conforming to the current fashion isn't a reason to move. But I looked at what I was doing with my website, and moreso what I was paying each year to maintain it, and it didn't really make much sense. Blogger (which I'm currently using) meets my needs well enough, and it's free. I'm continuing to pay for the "" domain, but that's very little compared to maintaining a web host. File storage is handled by Dropbox, so it made little sense to keep the old site going.

The second reason for moving was that a blog supports a "train of thought" development style. I don't have to fill in an entire "chapter" of information if I want to present a portion of the subject; I can just post it to the blog. Granted, I could do that on a static site, but partial entries portray an unfinished, unprofessional appearance. With blogs, it's expected. Plus, the level of detail I've maintained in the past has been, in my opinion, not worth the effort (for me or for visitors). I have some more extensive thoughts on that which I'll be putting into a future post.

An obvious question is why the Mythosa information is in a PDF and the "Gamer's Almanac" has been converted to blog posts. I'd started converting the Mythosa pages to blog posts, but it seemed too disparate. Instead, I compiled the old content into one big PDF (which needs to be reformatted at some point), and only new material will be posted to the blog (and eventually will become supplemental PDFs). The Almanac, on the other hand, is made up of articles that someone would be more likely to be searching for on-line. I figured it would be easier for people to find (and use) that information if it was accessible directly on the blog rather than tucked away inside a PDF.