Klossus Part 5: Where the Brainstorming Ends and the Work Begins

Gather around, wanderers of wondrous worlds, scribes of the supernatural, and acolytes of adventure. Pull your stools closer to the fire and fill your cups, because tonight we celebrate. This is the final chapter of our Klossus series.

Now that I have indulged in a flowery opening, as any concluding article deserves, I will speak as plainly as I can.

Welcome to Part 5 of 5 in our journey through world design. Here the brainstorming ends and the real work begins. Until now, Klossus has been a collection of notions: an occupied island, a resistance of knights, a ticking clock, a few whispered legends. Notions are wonderful things, but you cannot play a notion at the table. Tonight those ideas begin to take on real shape.

I will not rehash the work we have already done. If you need a refresher on the ground, the masters, the threats, the magic, the factions, the coin, or the legends, you will find every installment in the Geek Opera Index at Scaldcrow Games. Instead, I will move through the forms and tools this setting needs to become a playable Pocket World, and I will lay out my next areas of focus.

First, though, I must answer the last of our ten worldbuilding questions. That answer will serve as my compass for every decision that follows.

What Truly Sets This World Apart?

In Klossus, nothing is inherited.

No crown, title, rank, or blessing passes by blood. Everything is earned, deed by deed. Stop earning, and it slips away.

This single truth runs through every corner of the setting. The Overlord’s claim expires the moment the Regent arrives. The Marks of the Broken Horn are only worth what a knight does next. The oldest legends blessed the worthy, never the well-born.

Here is the sharpest edge of the idea: a knight who frees a Hamlet earns its gratitude. A knight who keeps that Hamlet has become a Hill Lord.

GM note: Never explain this rule to your players. Let them collide with it. Show them a fallen noble begging at a Hamlet gate. Make titles decay when knights sit idle. Reward the goatherd who held the bridge over the knight who arrived late. When your table starts asking “What have I done lately?” instead of “What am I owed?”, the idea has taken root.

Every tool below must serve this truth. If a sheet, a table, or a rule does not reinforce the idea that standing is earned, it does not belong in Klossus.

The Knightly Values Definition Sheet

We have established that this is a story about honor, and about building something greater than what fell. A story about honor needs heroes who know what honor means to them.

At Session 0, I suggest the party begins by filling out a Knightly Values Definition Sheet. This form will be included in the Pocket World. It asks the players to answer two simple questions together:

• What do we value? Mercy to the defeated? Protection of the common folk? Truth, even when it costs us?
• What will we not tolerate? Hostage-taking? Breaking an oath? Leaving the wounded behind?

The knights of Klossus already carry an honor code. This sheet gives that code real definition. More importantly, it hands ownership of the story to the people sitting at your table. A code the players wrote is a code the players will fight for.

The code is not carved in stone. Allow your players to tweak and refine it as the game moves forward. The world will test them, and those tests may sharpen their vision. A party that once swore to “never spare an Iron Tithe officer” may rethink that vow after an officer saves a village from famine. That change is not a failure. It is growth, and it is a story worth telling.

The Campaign Tracking Sheet

Next comes a sheet the party receives at the very beginning: the Campaign Tracking Sheet. This is the knights’ shared record of the war, and it should hold:

• Honors earned: deeds recognized by Hamlets, factions, or fellow knights
• Allies: who stands with the party and why
• Diplomatic allegiances: the status of relations with non-human peoples and powers
• Enemies: who wants the knights dead, ruined, or disgraced
• Hamlet status: which Hamlets are free and which remain Helot Hamlets, the true scoreboard of the war
• Current concerns: enemy locations, troop movements, and rumors worth chasing
• The Ledger: honors and debts owed to the knights, and favors they can give, trade, or bargain with

That last section matters more than it may seem. In Klossus, coin has limited use. The Overlord’s money is backed by fear, and the old coins are a hanging offense. The real currency of this war is the promise, the favor, and the oath. A knight who knows who owes him, and whom he owes, holds a weapon sharper than steel.

I prefer to keep all of this on a single sheet. If it spills over, the second page must earn its place by being useful at the table, perhaps a miniature version of the island map.

The Knight’s Honor Score

Knights can endanger their standing and their honor, and that risk needs teeth. So each knight will carry an Honor Score, a number that represents how the world perceives his honor.

This score works as a bonus or penalty on ability checks where honor matters. Picture a knight negotiating with a wary Hill Lord, or asking the Green Ring Clans for sanctuary. A knight whose honor is untarnished walks in with weight behind his words. A knight known for broken promises walks in with a shadow at his back.

Honor rises through deeds witnessed and remembered. It falls through oaths broken, Marks left unpaid, and Hamlets kept “for protection.” Because nothing is inherited in Klossus, even a high score is never safe. It must be maintained.

A word of caution to fellow designers: Every sheet you add to the back of a book reduces the space you have for game content. Pocket Worlds are lean by design. Before adding a form, ask whether it earns its page. In this case, the Values Sheet, the Tracking Sheet, and the Honor Score all drive play directly. That is why they stay, and why I will fight to keep them compact.

The Map

I will need a map of the island. A map sets the parameters of the game and marks the edges of this particular world: the sea coves, the Meadow Ring, the northern river, the jungle ring, and the capital at the heart of it all.

Because I want Klossus to have long-term potential, I will suggest that GMs place this island into the space of another Pocket World, or into an original fantasy world of their own design. This is one of the great strengths of modular design. Klossus does not have to stand alone. It can be the troubled island off the coast of a world your group already loves.

How I produce the map will depend on need and cost. Some maps are hand-drawn. Some are commissioned. Some are built with digital tools. How you do it is up to you. What matters is that the map exists. A map grounds the adventure in a communally shared vision and creates a culture of belief at the table. When a player points at a cove and says, “We strike there,” the world becomes real. Even if its uses are otherwise limited, just having one is important.

Troop Encounter Statistics and SLICs

Klossus is a land at war, and war means soldiers. I will create statistics and SLICs for troop encounters: Iron Tithe patrols, garrison squads, Hill Lord spearmen, Saltking raiders, and the desperate bands of the Ash Road.

This work does double duty. Building enemy troops is also a crucible for designing the archetypes available to players. When I know what a garrison captain can do, I understand what a knight must be able to answer. When I see how raiders fight in the coves, I learn what a sea-raid knight should look like.

I generally aim for around six archetypes. Six offers enough variety for a full table without burying anyone in choices. If more are needed later, I can expand them elsewhere, such as here on the Scaldcrow Games website, without stealing pages from the core book.

Three Magical Schools

Next, I will build three magical schools. Their purpose is to supplement the actions and choices of the heroes, never to rob them of the honor and rewards of being heroes. In Klossus, magic is slow, costly, and socially dangerous. A spell may open a door, but a knight must still walk through it.

1. A school for players: available to those who choose it, with real costs and real limits, so that it supports a knight’s courage rather than replacing it.
2. A school for inhuman allies: the strange powers of non-human peoples, offered as aid, bargain, or warning.
3. A school for opponents and villains: the machinations of those who would rule Klossus through fear, forbidden names, or the restless dead.

Three schools are enough to give magic a presence in every corner of the war without letting it drown out the clash of swords.

The Faction Tracking Sheet

The GM needs a tool of his own. The Faction Tracking Sheet lets the GM keep track of every faction added to the game: what each one wants, what it fears, how it feels about the knights, and where its internal disagreements stand.

Thirteen factions is a lot to juggle. Remember my advice from Part 4: start with three and let the others enter through rumor and consequence. This sheet grows with your campaign. When a faction joins the story, it gets a line. When the knights help one side of a faction’s split, the sheet remembers, even if the players forget.

Story Hooks, Rewards, and Adversaries

Finally, I want tools that let a GM sit down and play with minimal preparation. A world that requires hours of prep before the first die is rolled is a world that stays on the shelf.

The Story Hook Generator

The generator will combine a few random tables into a ready adventure seed. Here is a taste of its shape:

d6	Who Needs Help	What Threatens Them	The Complication
1	A Helot Hamlet headman	A grain tithe due at dawn	A faction ally wants the same prize
2	A Pithos Guild mistress	An informant in her household	Helping her breaks the party’s code
3	A band of Ash Road Folk	An Iron Tithe sweep	They may be the raiders after all
4	A Sister of the Drowned Spring	A prophecy spoken too soon	The Regent’s clock advances
5	A Ferryman of Souls	A haunting spreading beyond control	An old debt comes due
6	A young Saltking captain	His own king’s retribution	Success could spark a civil war

Alongside the generator, the book will include a list of premade story hooks for GMs who want to hit the ground running.

The Rewards Table

Since coinage has limited use, treasure will take other forms. A sample:

d6	Reward
1	A Hamlet swears its loyalty and joins the free settlements
2	A favor owed by a faction leader, recorded in the Ledger
3	A secret: the name of a skimming officer or a hidden patrol route
4	Safe passage through Saltking waters or the Green Ring
5	Arms, a horse, or armor forged in secret
6	A relic or omen granted by those who judge the knight worthy

Notice that every reward ties back to the war, the scoreboard, or the Ledger. Treasure in Klossus should change what the knights can do, not just what they own.

The Adversary Design Table

Last, I will build an Adversary Design Table. The GM rolls to randomly match an enemy’s goal with a personality and a set of resources:

d6	Goal	Personality	Resources
1	Crush a free Hamlet	Cold and patient	A garrison of trained soldiers
2	Win the Regent’s favor	Charming and false	A network of paid informants
3	Claim the lost heir	Zealous and certain	Ancient lore or forbidden magic
4	Seize the grain stores	Greedy and cautious	Control of a trade route
5	Destroy a rival faction	Wounded and vengeful	Hostages taken from a Hamlet
6	Earn a title by any means	Ambitious and reckless	A band of hungry mercenaries

Roll once on each column, and you have a villain with a reason, a temperament, and the means to cause trouble. A cold, patient adversary hunting the lost heir with hostages in hand is a very different evening than a reckless upstart chasing a title with sellswords. Mix, match, and let the results surprise you.

Stepping Out Into the World

When all this is done, I will gather art, build a marketing plan, and step out with a new game that, I hope, excites and inspires. That final stretch is its own adventure, and perhaps a story for another night around the fire.

For now, look back at the road we have walked together. We started with a single image: knights resisting an occupied island before a foreign ruler’s sails appeared. We gave it ground and masters, threats and magic, factions and coin, legends and one defining truth. Now we have a plan to turn it into something you can hold in your hands and bring to your table.

Your turn, worldbuilders. Take what you have learned in these five parts and build something of your own. Then come tell us about it. Which tool would you build first? What would you add, and what would you cut? Share your thoughts with us at Scaldcrow Games. We would love to hear what grows from your fire.

Watch the shadows, my friends. And always check your ale for poison.

If you would like to revisit past articles, look no further than the Geek Opera Index!