“…whenever anyone came to inspect it before purchase, the caretaker used to praise the house in the words that Nuth had suggested. “If it wasn’t for the drains,” she would say, “it’s the finest house in London,” and when they pounced on this remark and asked questions about the drains, she would answer them that the drains also were good, but not so good as the house.”

—Lord Dunsany, How Nuth Would Have Practiced His Art Upon the Noles

The upper part of the range of the d20 roll used to resolve #downtimes in the previous article determines whether the downtime was particularly successful or unsuccessful.

The lower part, indicating an average result, provides space for other complications, and consists of a seperate 1-8 table written for each available lodging, such as the default lodging of the campaign:

A Room at the Inn

An unpretentious room at a local inn, with a small fire in the grate. Recovery Rate: 1d6 CON/DT Ameneties: None. [Some kind of bonus to hiring retainers might be appropriate if we envision the inn as a clearing house for would-be adventurers.]

1-5: Pay Your Tab – 100cn upkeep (+50 per retainer) 6: Petty Theft – the cheapest gem, jewellery or other small treasure is taken. 7: Disturbed Sleep – Rowdy patrons reduce base recovery rate to 0 this DT. 8: Nemesis – If an enemy is looking to harm the PC, they gain access to the Inn.

So instead of having to remember to pay 25 coin every week for upkeep, the bill only comes due once a month on average. This might lead to unusually high or low living costs, but this can inspire fictional details – “we’ve had no trouble with the local youths since you started staying here – the room’s on the house” or “you’re traipsing through here every week with sacks of gold, you can afford to pay a little extra for our hospitality.”

For rangers, barbarians and skinflints, another options is:

A Camp in the Woods

Who needs the comforts of civilization when you can sleep beneath leafy boughs? Recovery Rate: 1d4 CON/DT Ameneties: None.

1-2: No event. 3: Good Foraging – Gain 1d6 surplus rations. 4: Weather – Roll on the weather table. If the weather is bad, the camp is negatively affected at the DM’s discretion. 5: Disturbed Sleep – The woods are not always a restful place. Reduce recovery rate to 0 this DT. 6: Random Encounter – Roll a forest encounter. 7: Rust & Rot – Next roll of 1 causes the item you’re using to break. 8: Ransacked – Roll a random encounter. The encounter finds the camp – wild animals may root around and eat provisions, humanoids may steal treasure etc.

And for those who like to keep things very simple:

A Guest at the Castle

Your patron has graciously made rooms available for your use, in recognition of services rendered – and services yet to be rendered. Recovery Rate: 2d6 CON/DT Ameneties: Depends on the patron, but may include library, training, chapel etc. Requisite: PCs must accept quests from the patron.

1-8: No event.

No upkeep or events outside of those dictated by the story (e.g. the villain lays seige to the castle), but the patron will require the PCs to go on regular quests for them.

Advanced Lodgings

So far so dull; these options don’t do much apart from establish that the PCs need somewhere to rest their heads and keep their stuff – but once the player starts asking “where do I want to live?” it can become a goal and another way to define their character.

An inspiration here is the lodgings from Fallen London. Depicted by evocative silhouettes and short descriptions, they imply a great deal about the nature of the setting, and suggest story possibilities.

Some examples (taken from the wiki, potential spoilers):

A Smoky Flophouse: Fleas, noise, smoke, Rubbery Men squealing as they're dragged out back and murdered. But you meet the most fascinating people.

Cottage by the Observatory: The blind men at the Observatory rent these out, to people who don't mind occasionally being assaulted by predatory fungus in the middle of the night.

Rooms above a Gambling Den: Noisy when it's open. Noisier when someone forgets to bribe the Constables and they stage a raid. But the conversation's good.

Rooms above a Bookshop: Rooms on three levels above a winding, dusty stair. The owner is melancholy and given to buttonholing you at the door and weeping into your hat. But he does have some interesting customers.

Decommissioned Steamer: Not a safe place, down by the Unterzee shore. Nor warm. But it's quiet, and offers good opportunities for beachcombing.

A Zee-Znail's Zhell: Whimsical echoes resound in the fluted vaults. Far out at zee, the lights of ships.

A Dripstone-Snared Third City Sub-Temple: A stalagmite: and at it's heart, a black space of silent sacred horror.

A guest room at the Brass Embassy: The luxury is sinful. The staff are always polite. Warm? I'll say it's warm. Good cigars, urbane conversation, and just the slightest possibility of accidental damnation.

A Room at the Royal Bethlehem Hotel: There's nowhere like the Royal Bethlehem Hotel. Its luxury is unparallelled: its guests, beyond baroque. Lock your door, or you don't know who you might wake up in bed with.

We have ambience, we have dangers, we have perks, we have NPCs! Suddenly home away from the dungeon isn’t just an off-camera void but a living place, with character and interest of its own. All in three sentences or fewer – easy enough to distill into a table.

There were plenty of enchanting or dangerous places to stay in my #RedHack / Ultan’s Door campaign, to list a few:

• An upstairs room at Bar Saturn.
• Cycladic apartments on Enraptured Isle.
• A modest Rastingdrung Tenement.
• An undersea bedroom at the Sunken Spire.
• A Studio in the Stables of the Guides.
• Guest at the Court of the Chatelaine.
• Mimsy’s Manse.

A simple lodgings table for each automates the ever present benefits and risks of living in such a place, such as the capricious requests the Chatelaine may make of her guests, or the comings and goings of Zyan Between.

#RedHack uses discrete descriptive experiences rather than points. To level up you must checkmark a number of Experiences equal to 2 plus the level you’re advancing to.

All four basic classes cap out at 12, at which point you can either just play the domain game or introduce Advanced classes for the next 12 levels, similar to the Paragon Paths of 4e or 3e Prestige classes.

In my original campaign the party chose:

Fighter –> Psionicist Bard –> (Advanced) Fighter Rogue –> Ranger Cleric –> Paladin Cleric –> Channeller Wizard –> Archwizard

Which I felt was a nice mix of doubling down on how they already defined themselves, taking radically new directions, and focusing in on one aspect of their existing role.

Each dungeon provided around 4-7 experiences using our list, which if we assume three weekly sessions per dungeon on average gives us 0.7-1.2 years to reach level 12 – which feels about right, and there’s a nice, almost fairytale quality to having to have exactly 99 daring experiences before you become a legend.

Training Systems

In the original campaign I ruled that levelling could be combined with any downtime action appropriate to your class, and would enhance the result of that action – so the level-up action became a resource players could choose where to spend. I liked this but it's not very diagetic – reminiscent of characters in MMOs fully healing and becoming buffed and healed when they hit a new level mid-combat.

Later I toyed with the idea of requiring training with a teacher, in order to encourage relationships with NPCs, but when I ran the Undying Sands – with the PCs as wanderers lost an otherworldly, shifting desert – the lack of a home base became a problem.

So instead of making training mandatory, I introduced a rule that once per level you could get a bonus Experience by training with a mentor – the Experience gained would have to be used to level up before you could benefit from training again.

There are a few options I’ve been looking at:-

1. Training happens in combination with any downtime action, and improves that action.

2. Training happens in combination with an appropriate downtime action – such as magical research for a wizard, or martial training for a fighter.

3. Require training with a master to level up. Once the PC reaches name level, the master has nothing left to teach them. But if an 8th level fighter is a superhero, should they still be in training? Possibly, if we’re talking Batman-style obsessive training where you seek out the greatest masters in the world to learn from.

4. Training as a bonus experience, once per level.

5. ‘Campfire’ training providing only some of the benefits (attribute points and HP, but not spells or new techniques) until supplemented with training back in town.

6. Prerequisite actions. You can level up overnight, or within the space of a downtime, as long as you have done one of the following things since you last gained a level:

Fighter

• Spar with a fighter of higher level; it would be gauche for him to charge you for the privilege, but he may ask a favour.
• Face a superior foe in single combat.

Cleric

• Visit a temple, regional locus of church power, or site of pilgrimage. You may be charged with some holy duty. Ignoring it won't stop you meeting the requirement to level, but may affect your standing with the faith.
• Form a new bond.

Thief

• Introduce yourself to the local thief guildmaster, underworld boss, crimelord etc. It will all be very polite but they may demand a service of you.
• Steal a unique treasure of at least local renown and keep/sell it. (Retreiving it for the king doesn't count.)
• Carry out a daring act of thievery and brag about it, gaining a local reputation.

Wizard

• Submit research on an obscure point of arcane or scholarly lore to a learned wizard or college of same. They may ask that you prove your worth before reviewing it.
• Research a new spell.
• Create a potion or scroll you have not made before.

I’m not precisely sure about the list, and I must be certain that it includes things that it’s fun or possible to do every level, but I like the idea of Fighters being on the lookout for worthy foes, Thieves being embroiled in the murky underworld, Wizards being catty academics if they aren’t entirely solitary, and Clerics wanting to detour to visit a pilgrimage site.

Each class has something to encourage interaction with NPCs, but also a less sociable option. I feel like the list could use a few more.

Once HP are depleted in #RedHack further damage spills over into CON. Upon taking CON damage a character must make a CON test to keep fighting.

Once incapacitated, a character’s fate is determined by the downed table:

* this save is made on your CON value before the damage was dealt.

Characters without a CON score roll a d6 on the table, subtracting one if they receive magical healing, adding one if they are left for dead.

Characters with CON base their result on their total CON lost. If they are magically healed, the healing restores CON before HP (this is the only time magical healing can directly restore CON). If they are left for dead they take a further 1d6 CON damage before consulting the table.

Exhaustion, Wounds and Injuries are all types of Burden, which affect encumbrance. Most PCs become encumbered when they have three Burdens, fewer if their CON is reduced, so these are a significant problem.

Infections follow the disease rules – I should write up a standard one.

A Doomed character may be dead instantly, they may expire after having time to say a few words to their tearful companions, or they may slip into a coma and linger for days – but in any case they are at least en route to the Hinterlands, and will die unless drastic measures are taken.

Healing from Wounds & Injuries

During downtime PCs heal 1d6 CON per week naturally, and this number can vary based on the quality of their lodgings – a stay at the Temple of Chardastes under the care of the healers there might yield as much as 4d6 CON/DT.

Full bed rest increases this number by a flat +6 in any case.

After rolling, the PC can spend any excess on overcoming Wounds & Injuries. They may also wish to sacrifice some of their CON to finish healing from an Injury – rising from their sickbed a little earlier than is prudent, and venturing back into the field shaky as a result.

Last month we tried out some new wilderness travel rules in #RedHack. The party were travelling from Castle Mystamere to the Iron fort, through hexes 502, 402, 302 and 202.

The system divides the day into six four-hour watches:

          Watch Table/Reference
1. Night          8PM-12AM  
2. Small Hours    12AM-4AM  
3. Morning        4AM-8AM   
4. Midday         8AM-12PM  
5. Afternoon      12PM-4PM  
6. Evening        4PM-8PM   

Each day, weather is rolled for, starting with the expected weather for the region and season and adjusting a step each day…

…and the daily travel table is consulted:

           Daily Travel Table
1.   Encounter in jungle, mountains or swamp.
2.   Encounter also in desert, forest or hills.
3.   Encounter in any terrain.
4-5. Apply weather effect. 
6.   No event.

If an encounter is indicated, roll d6 to determine which watch it occurs during; if while the party is resting, they’re surprised if they didn’t set a watch.

Extreme weather like a hurricane or blizzard always affects travel, and is worse on a roll of 4-5. Inclement weather has an effect on the table such as Arid weather consuming extra water rations and Mist causing the party to get lost.

Base speed in hexes per watch is based on mode of travel:

           Base Travel Speed, Hexes/Watch
Riding Horse                              3*
Forced March                              2*
Walking, Mule, Wagon, Warhorse, Donkey    1
Ox Cart or Encumbered Walk                ½
 *Must rest for a watch after 1 watch of movement or gain exhaustion

Every time the party leaves a hex the per-hex table is rolled on:

      Per-Hex Travel Table
1.   Spoor
2.   Exhaustion
3-4. Hazard
5-6. No event

A Spoor result means signs of a creature nearby; a second such result is an encounter with the creature. Exhaustion is a status in the system which puts an average PC halfway toward being encumbered, and can be cleared by resting for a watch. (In the dungeon, exhaustion takes two turns to clear – the PC only has to be rested enough to keep opening doors, not ready for four hours of marching.) Hazard means a roll on a terrain-specific table.

             Mountain Hazards
1. Precipice (Cliff, slope) - If approached without precautions, roll 1d20; anyone with a lower DEX must make a DEX save or fall for 1d3xd6 damage. 
2-5. Rough Terrain - The hex counts as two hexes.
6-8. Lost - Move randomly out of this hex.

My initial weather roll indicated a misty morning; the daily travel roll indicated weather effects. The PCs set out and immediately got lost, wandering north into hex 501.

Realising they should be in the valley already, they solved the problem by climbing to a vantage point in the mountains above the mist to orient themselves. By evening they had reached the river valley, and camped for the night.

Here I let them forage a little – 1-2 on a d6 to find a ration, modified by whether the terrain is fertile or barren and whether the PC is an outdoorsy type – and refill their waterskins at the river. I need to be clearer about who can forage and when, and what other camp/travel actions are available.

After a quiet night’s rest they encountered some blink dogs, and fed them in the hopes of inducing them to follow the party. They ventured back into the mountains. They got lost in 302, sending them to 303, where rough terrain ate up a third watch. They camped in the mountains and fed the blink dogs again.

In the morning they spent a watch foraging while two of them looked for high ground; they could see the Iron Fort in a small wooded valley below.

I’d lost track of watches by now so had them arrive earlier than they should have, during the evening watch, and then having rolled exhaustion on the way there, they spent some time resting, looking for water, and observing the fort from a distance, allowing them to get the drop on the troglodytes loitering around the entrance. The blink dogs also deigned to enter the camp this time, becoming more comfortable around the PCs.

Things that worked – the individual rolls were fairly simple to keep track of; the system allowed me to visualise and describe the weather and surroundings; the result was slightly unpredictable travel where terrain and weather matter, with both eating up supplies at a faster than anticipated rate.

What didn’t work – the PCs took novel actions to solve their problems during travel, which is to be encouraged, but they needed some more standard mechanical choices to feel in control of the process of travel. There needs to be more clarity in who is on watch, who is foraging, who is memorising spells etc. My notes were spread out in a large document on my laptop; I need a crib sheet and the players need to be able to see the rules being used so they know what their options are. There were complaints about becoming exhausted after the first watch of travel (4hrs seems long enough to need a rest) and about getting lost leading to random movement (fair – perhaps a 50/50 chance of going to the left or right of your intended direction? But how does one realise one is lost, and how does one become un-lost, barring climbing a high place to get one’s bearings?) and about not knowing how much food to bring (fair, can be addressed by writing out the rules for the players. We’ve also recently changed from rations being a usage die item to a one-use item.)

The map was open, but only on players’ phones, and they didn’t always know which hex they were in. I should have printed it out and given them hex paper to draw a map of their route so they could realise something was off when they compared the two.

For dungeon exploration I make an unkeyed copy of the map and cut it up with scissors as they explore, letting them re-assemble it with a glue stick – this is easier than explaining the exact shape of every room to the mapper. But verbal descriptions of hexes are much easier, “you move SE into a mountainous hex, a river passes through it from the NE to the S side.”

The system worked well enough but I still want to consider whether this is the best way to manage travel events, speed and weather. The blog Copper Pieces, for example, has an interesting series of articles from 2021-2022 discussing the use of Markov chains to generate weather.

I keep coming back to the question of encumbrance in #RedHack. It's a hard thing to streamline, because the input consists of numerous very different items, from loose coins to plate armour, and the output is some point at which the PC slows down to some degree, and another point at which the PC cannot move, ideally mediated by some combination of STR and CON. (I like CON as a measure of how much you can carry, as opposed to how much you can lift.)

But items move around a lot, so it all has to be recalculated anytime something is dropped, picked up or traded.

I started with “one item slot per STR point”, tried a container-based system, a push-your-luck version where you had to roll 1d6 per six items under your CON to move at normal speed , and one which simply counted multiples of six.

Sandra shared her very well thought-out approaches: A block method, which seeks to minimise recalculation by fencing off ‘settled’ areas of the inventory, her 5e sheet, which uses a size-based system, and the sheetless version, as well as pointing me back to page B20 of B/X, which de-emphasises equipment and provisions, tracking armour and treasure as the things that are most likely to slow PCs down.

This is good from a gameplay perspective because it's a meaningful decision – trading speed for either protection or rewards.

I also want to streamline, but I'm leaning toward the opposite direction. Weight of armour and weapons feels less important to me – wearing heavy armour might tire you out over time, but it isn't going to render you immobile. Objects held in hands are less urgent to track because there's already a limited supply of hands.

What matters most from a weight perspective is provisions and treasure.

So, this where I am now:

Each PC can carry a small number of burdens. A burden is-

• Up to 20 items of weight in a backpack.
• (Optional) More than 20 items of weight worn or held.
• A level of exhaustion.
• A long-term injury.
• Privation from lack of food, sleep, water etc.

Most PCs can carry 2 burdens before suffering penalties, and become immobile once they exceed 6. High CON or low CON adds or subtracts 1 from the amount that can be carried without penalty. High or low STR modifies the maximum burden limit by 2.

Held items don't normally count toward burdens. Some items can only be held (or carried on carts) such as halberds or 15' poles. If the item held is a table or something, it may be a burden in itself.

Worn items – armour, weapons in scabbards, magic jewelry, a shield across the back – don't count either. If you're wearing six swords and three cloaks the DM may rule you have an extra burden.

(Alternatively, worn/held items could be limited to 20 items weight total before a burden is incurred.)

Heavier armour makes you more likely to suffer exhaustion when exhaustion is rolled on the dungeon die. (DM Rolls d20 when the result occurs; any PC with lower CON than the roll gains exhaustion. Any PC with equal or more levels of armour than the roll (3 for leather, 7 for plate etc.) also gains exhaustion.)

A pack holds 20 items and usually counts as a burden. A sack holds 10, perhaps? And can be carried in a hand if you want to trade a free hand for more capacity.

The threshold for an item is about 2lbs. Half-items exist but I'll try to minimise them to make counting faster. Items under 1lb are counted as 0 unless you have a lot of them (a shipment of compasses obviously weighs something, but 2 compasses aren't going to add anything to your load.)

A stack of coins is an item. I'm not sure how big a stack. Black Hack uses 250/item. Since switching to the silver standard – and thus dividing most published hoards by 10 – I've been using 100/item. With the revised figures and AD&D weights it's looking more like 20/item. Amethyst disagrees and says this is far too heavy. Looking at the weights of two iconic 'treasure' coins, doubloons and pieces of 8, we'd get 134 and 33 per item respectively, which points to a figure of 100 or 50.

With the Gem Table we devised recently unappraised gems are homogenous and could also be stacked, at perhaps 50 or 20/item .

#RedHack combat rounds are 30 seconds long – long enough for multiple attacks and for a sprinting PC to cover 180' or more. Each character only has one action during this time, but the additional opportunities for action are provided by reactions. These might be the biggest divergence between the rules and B/X D&D.

Each character with class levels has a pool of reactions per round based on level:

Wizards have one reaction. They aren't good at fighting. I'm toying with letting them spend it to maintain certain spells or fire off magic-missiles, rewriting some spells to utilise the mechanic.

Thieves have one reaction, but it hits hard. If they use it to attack, they deal double damage plus half their level, and may roll DEX to attack instead of STR. They can also spend it immediately to attack an unaware or surprised foe, dealing triple damage plus their level.

Fighters gain a reaction every other level, and also have special Techniques which give them additional opportunities to spend them – for example Riposte allows the Fighter to make a reaction attack against anyone who misses him in melee.

Clerics also gain a reaction every other level, but can only use them in the standard ways.

Monsters do not track their reactions per round, but simply have a chance to react to each trigger, based on HD:

The standard ways to use a reaction, available to everybody, are:

Countermove – Maintain distance between you and an opponent trying to approach or get away from you by reacting to their move and moving with them. Intercept an opponent mid-move, keeping them from reaching a weaker ally or coveted item.

Counterattack – Attack a foe about to attack one of your allies in melee range.

Overwatch – Fire a ranged attack on a foe approaching you or moving out of cover or melee.

Opportunity – Attack a foe while they are changing weapons, drinking a potion, casting a spell, firing a bow in melee, or taking some other non-attack action when they should have their eyes on you.

Usually each reaction trigger can only be used by one character – one normal attack leads to reprisal by one reaction attack. (Reactions never trigger reactions.)

I'm thinking the best way to make this part of the flow of play would be to make reactions part of defending against an attack. The player being attacked, before rolling for defense, would call on another player to “defend me!” This would not necessarily be in-character, as the character may not have time. It's a non-diegetic mechanic, but it places the burden of remembering reactions on the beneficiary, and resolves the question of who gets to react: The first player invited by the PC to be willing and able to react.

Monsters simply roll on the table; multiple monsters roll with advantage. I'm thinking that the monster who reacts is the slowest monster who could act on the roll of the higher die – e.g. if you're fighting a dragon and a goblin and you roll snake eyes, the goblin reacts and not the dragon.

Shields

Currently a shield allows you to react to a successful hit either on yourself or an adjacent ally by rolling defense on STR and spending a reaction to avert the blow only if you succeed.

This is probably too powerful, and should spend a reaction for the attempt and not simply on success – it's already only targeting successful attacks, and it's worth a reaction to take a shot at not suffering what is otherwise guaranteed damage.

Claw Claw Bite

There's an issue with multiple attacks. Claw/claw/bite is already a wrinkle in the system because of the player-facing rolls. If six goblins attack one PC I can just say “make six defense rolls, difficulty 1.” If two gargoyles attack the same player, it's “make four defense rolls, then two more, then two more, difficulty 4.”

Add reactions to the mix, and we have the gargoyles potentially taking 8 opportunity attacks in one round. I think it needs to be one reaction per target – having multiple attacks shouldn't disadvantage a monster. So if the gargoyle claw/claw/bites a PC, that's one reaction attack; if they tail lash another, that's a second.

It's also tempting to figure out a way to make the bite the main attack and turning the weaker claw attacks into guaranteed reactions, but there'd need to be a very clear rule of thumb applicable to all classic monsters.

The Dopey Boss Monster

If monsters only have access to the normal reaction triggers, they rely on having allies around to use their reaction attacks. The dragon alone in its lair should be formidable, and reacts more often than it doesn't – if it has something to react to.

One solution might be to give monsters access to Fighter Techniques. This is more work so it would have to again rely on simple rules of thumb – one technique every 4 HD is a possibility, or simply one technique for every monster of 4HD or more. Indeed, multiple techniques would be a lot more powerful on monsters, which never run out of reactions during the round, and are probably best reserved for NPC fighters who have to track reactions.

NPC bowmen have the Archer technique by default, so a similar approach could be taken here – large and ferocious monsters like dragons might default to the Stand technique, making them dangerous to approach – they will react when you close into melee with them.

On the one hand, writing #downtimes has been one of the most rewarding parts of running games with #RedHack. On the other, it’s also the most time-consuming and demanding, equivalent to prep for the game itself.

So as well as providing for a range of downtime activities and results, I’m looking for ways to reduce bookkeeping.

In a addition to resolving downtime actions, I like the idea of Lodgings: Allowing PCs to trade upkeep costs for ameneties and the security of their possessions and persons, but there’s a risk of ending up with many steps of bookkeeping for each character – deducting upkeep, checking for illness, robbery, poor maintenance of equipment and so on, applying any perks, before even getting into downtimes and having to design progress clocks and roll for complications.

How much of this can we concentrate into one roll?

BenL's downtime system uses a 2d6 PBtA style roll, and recommends ability modifiers of +1 for 14-17 and +2 for 18. My system only has one tier of ability bonus or penalty (attributes are either High (16+), Low (6 or less), or Average.)

Converting these odds into odds out of 20 and massaging them a bit to offset my more stingy modifiers and to keep the odds of an 'Average' result consistent, we end up with:

Every downtime each PC rolls a d20 and reports the number rolled.

If the result is a 1-8, an average downtime result is recorded, and the number is passed to a Lodgings table.

9+ means a good or bad result on the downtime. 17+ is a good result. (15 or better with High ability, 19 or better with Low ability.)

This isn't very intuitive; it would be nice to have the bad results at the bottom of the range and the average ones in the middle, but putting the average results first lets us pass the number on unchanged to a 1-8 table, which handles all of the upkeep costs and random events arising from wherever the PC happens to be living.

So from one roll we get two salient pieces of information for each character: Their downtime result, and either a complication/benefit to the downtime or some complication arising from their domestic situation.

That is, assuming the ‘average’ result for most downtimes is also the simplest outcome, which is only sometimes the case in Ben’s system – for Revelry and Learning a Skill, but not for Cultivating a Relationship or Building an Institution. I need to consider whether to diverge from this in the name of streamlining.

Another question is how to include other sources of random events and DT modifiers, such as Institutions. Perhaps a PC who owns a cafe gets to count a range such as 9-11 as ‘Good’ results on Gather Information downtimes.