Kitchen-sink fantasy is one of the most popular genres. A shared list of monsters, spells, and magic items gives a table an instant common language, and that is no small thing. D&D-like games have proven for decades that a well-stocked menu can be exactly why people show up.
At the same time, those lists can start to define the genre so completely that other possibilities get crowded out. A game built primarily out of catalogs is very good at some jobs and less good at others. The difference is worth paying attention to.
Kitchen-sink fantasy, and several other genres, often function like glossy, laminated chain-restaurant menus. For many tables the familiar menu is the entire point. For others it is mostly background noise. Knowing which situation you are in changes how much conversion work is actually worth doing, and how heavily the lists should shape the world.
When the menu is load-bearing
There are tables where the familiar list is not background flavor. It is the reason people sat down.
High fantasy that lives in the long shadow of D&D is the clearest case. Players arrive already knowing what a displacer beast does, how a fireball is supposed to feel, and roughly what a +2 flaming sword is worth. The shared catalog is the common language. In that situation, a GURPS game that refuses to provide recognizable versions of those things can feel incomplete or oddly abstract, even if the underlying math is elegant. The same pressure appears in certain supers games and in any heavily fantasy fan-favorite-filled setting where the audience’s attachment is to specific named powers, creatures, or items.
When the menu is load-bearing, conversion work (or a solid library of ready examples) stops being optional polish and becomes part of the product. A-I has made the mechanical side of that work faster, but the cultural side remains: the results still need to feel like the thing the table expected, not merely a point-balanced approximation. In these games, GURPS is being asked to function as a better kitchen for a menu people already know by heart.
When GURPS should refuse the menu
Other genres and other tables do not need the laminated list, and forcing one on them usually costs more than it gains.
Historical games are the obvious example. A Late Republic Rome campaign, or any grounded low-fantasy setting, is not improved by a thick catalog of generic monsters and magic items imported from elsewhere. The same is true of original worlds, most horror, hard science fiction, and any campaign that wants the system’s strength as a physics-and-character engine rather than as a content library. In these cases the absence of a pre-printed bestiary is not a gap; it is a feature. You build exactly what the story requires instead of carrying assumptions that fight the tone.
Here the conversion impulse is often a distraction. The energy spent translating another game’s catalog could be spent making the few things that actually matter feel precise and inevitable. GURPS is unusually good at that kind of focused work. Trying to stock a full chain-restaurant menu in these games usually produces something that feels both over-built and under-specific.
How much menu do we actually need?
Most tables do not need the full laminated catalog on day one.
A short, familiar core is often enough to make a fantasy world feel complete. Orcs, goblins, dire wolves, zombies, and skeletons already cover a surprising amount of ground. They give players recognizable threats, establish the setting's basic tone, and let the game start without waiting for a comprehensive bestiary. GURPS already has solid treatments of most of these creatures in the existing books, so the work of getting them to the table is modest.
Does an adventure need more than a dozen monsters? I could do a great adventure using six to nine beast stat blocks. How many of these are conversions versus creatures that can be pulled from GURPS books? Are there some that are "close enough plus a power?" I could take a stock panther and quickly mod that with a few special powers and have 95% of a displacer beast in GURPS. Orc sorcerer? Tack a few spells on a normal Orc. Some monsters can be rough sketches using GURPS Ultra Lite, and nobody will notice.
GURPS has a lot of fantasy bestiaries that cover a lot of ground, and the tighter focus of GURPS means you are not fighting through dozens of different monsters in a dungeon adventure. The rest of the classic list can wait. You can add displacer beasts, beholders, or more exotic undead later if the campaign actually calls for them. Starting small keeps the conversion burden light and prevents the world from being defined by a catalog that no one has opened yet. In practice, a short menu is frequently all a table needs to feel like it is playing “fantasy” rather than an abstract exercise in system.
Final Thoughts
The practical question is not whether kitchen-sink lists are good or bad. It is whether, for this table and this genre, the familiar menu is the reason people showed up, or mostly noise that gets in the way.
When the menu is load-bearing, the work of conversion (or of building a solid set of recognizable examples) is part of delivering what the players actually came for. When the menu is noise, that same work often distracts from the tighter, more specific design GURPS does especially well. The system can serve both kinds of game. The skill is recognizing which one you are actually running, and then spending your effort accordingly.
No comments:
Post a Comment