Sea Dogs, Chapter I:VI, GM Debrief

Session Recap; Stream

GM confidence: 4.5/5. Other than a couple of mistakes, I felt like I was firing on all cylinders this week.

A Rough Week

For whatever reason, I had a really hard time coming up with content for this week. I had the beginning (Randel’s intro) and the end (which we didn’t reach), but not the middle—I had the “travel” bit, of course, but I didn’t feel like that would be enough on its own. It took me until Thursday to come up with a plan, a compromise against what I wanted, but it eased my worry—and we didn’t get to that part either. It turned out well anyway. It’s worth noting that they didn’t actually accomplish a lot, but it felt like they did.

Write It Down, Continued

I talked about my need to “write it down” last week. This week, I made an effort to script out as much as made sense. My “narrative” mindset led to an attempt to arrange the order of events in a more readable, followable manner. Afterward, I felt like the results of the session proved last week’s theory correct. I didn’t follow the scripted elements exactly, of course, but I expected that. I intend and expect to improve this technique in the future, as there were certainly places that I feel could have been further improved.

The Hunt

When it comes to the PCs’ “Treasure Maps,” I have been using “The Hunt” (from Monster Hunters 2) as a guideline. Basically, when they find a “clue,” they get a Deduction roll to answer “the question” (the nature of which varies). It’s only come up once, so far: Payne’s finding the Compass was a clue, for which I allowed him to use Research (against the journal he had) to answer the question of “what do I do with this thing?” He didn’t get the entire answer, but it did give him forward-progress—he’ll get other opportunities later.

In Hayden’s case, he had gained a clue: the report that the Cardinal Virtue had been captured by the Spanish. He was therefore due a Deduction roll. I figured the records in Santo Domingo, combined with his own, would be a good enough opportunity. I took the precedent from Action 2 regarding Research taking 1d6 hours, and decided it would take 1d6 days to arrange to view the records. I had him roll this in secret: Hayden wouldn’t know how long it would take, and it was an opportunity to highlight his Obsession, and make him choose to delay the Expedition or not.

However, I messed it up quite a bit, mechanically. First, I forgot, in the moment, to make the roll in secret. Second, for reasons I can’t fathom, I didn’t sort out what the actual results of his success or failure would mean beforehand. (I blame the aforementioned “rough week.”) Ultimately, he did make forward-progress, in that he eliminated one of the many possibilities—this is a legitimate and helpful piece of information. But I failed to present that clearly, and as discussed after the game, it felt to him like a waste of time. The confusion resulted in the operation taking a little longer than it needed to. Lesson learned: results of success of failure on Deduction need to be spelled out, and it needs to be clear why it matters.

I had not discussed the use of “The Hunt” openly up to this point, for no particular reason other than I wanted to keep it a little more “organic.” It might have helped them understand the situation if I had brought it up before. But now that cat’s out of the bag, so we’ll see.

Sea Travel

In spite of its potential for drudgery, I think the sea-travel bit turned out to be the most fun:

  • Knowing there was going to be a lot to get through, I pre-rolled the random encounters and traffic stuff, which also allowed me the week to figure out how to interpret the results in a narratively-efficient manner
  • I’ve been rolling for a random NPC crewman to be “in focus” for the session, and Moggridge’s turn came up, but the random at-sea events rolled him up anyway—that was not intentional, but it worked out nicely. I did have notes to bring up the superstition regarding weighing anchor on Friday, but I didn’t expect it would actually occur. Mr. Moggridge’s illness was actually the result of the random events; its apparent connection to “Friday” was entirely coincidental.
  • I got the bugs in the spreadsheet from last week sorted out, but Ronnke started tracking the progress on the map, which meant I needed to add a daily mileage total as well—already done
  • The group is starting to get the hang of the at-sea procedures, so the die-rolling and assignments went smoothly—including those rolled by our audience (thanks to Ronnke’s chat-bots)
  • The “bet” was a surprise, though a welcome one—shows the players were engaged
  • The “man from the sea” event garnered exactly the reaction I intended; it was also the first time in the campaign the PCs have had to make a Fright Check (it won’t be the last)
  • The Ship Malfunctions (from Pyramid 3/103 Setbacks) didn’t confuse anyone, but I realized in the moment (or re-realized) that I really need some defined examples to pull from, and some mechanic to determine when/how the symptoms become apparent

Other Stuff

  • This week was my intended halfway-point of the campaign
  • Randel’s intro was an echo of a long-ago D&D game, with a similar incident involving another character of his
  • Claude’s Secret (nevermind the absence of his/her player) came up for this week, but I couldn’t quite figure out what to do with it in time, so I’ve deferred it to next week
  • The arrival of the Rumjack at the end was a part of the previously-mentioned “compromise solution,” but it was a good cliffhanger.
  • The session ended short of the content I had, but as I said before, that’s fine—I have a good starting point for next week, now. I expect them to get under way for St. Kitts next week, plus it’s Davino’s turn to find a Treasure Map clue.

Sea Dogs, Chapter I:V, GM Debrief

Session Recap; Stream

GM confidence: 3.75/5. Honestly, I don’t have much to complain about for this one, but there were a few bits here and there that were nagging at me afterward. I accomplished what I meant to, overall, but it was a bit rough.

Side Mission

There’s a tendency to have some sort of “adventure” at every stop along a long voyage in campaign-situations like these. I have wanted to distance myself from that. Thus, I originally intended Santo Domingo to be a non-adventure stop, but this turned out to be a special case. We were (supposed to be) down two players for this session, and I had considered skipping it, but decided instead to do a side-mission with the three players that were available. By the latter part of the week, the event had morphed into Furlong’s “Loyalty Mission.” I kinda wanted to “take it easy” this time and just do some character-development.

Full disclosure: I may have been experiencing a mild depressive episode during the week, which may have influenced the tone of this session’s story 😛

Treasure Maps

Each PC has a “Treasure Map,” essentially a personal campaign objective they’re attempting to complete. For each such Treasure Map, I make a weekly 3d6 roll in secret against a target of 6, like a Secret. On a success, some event occurs relating to that plot-thread, often in the background. I took the opportunity of a couple of them having succeeded to bring in some events I had been planning for a while (Hayden’s actually fired last week, but I delayed it). “CptButton” is one of our regular Twitch viewers (and played a session of Shadowrun with us); I’d been looking forward to an opportunity to start working some of those viewers into the narrative where I could.

Write It Down

In recent years, I had mostly gotten out of the habit of writing extensive GM notes, in an attempt to reduce the overall pregame workload. Plus, one can always tell when the GM is reading off a script. This session, however, was a bit of an anomaly, in that there were a few instances of complicated dialog that I had to write down. I observed afterward that I was able to deliver the stuff I wrote down comparatively smoothly, while I tended to stumble over the stuff I didn’t write down. I guess it really wouldn’t hurt to write down more. I’m trying to work on my “storytelling” anyway, and I suspect that’s going to follow the same pattern—I need to start pre-scripting more of the narrative elements.

Dependencies & Assumptions

I’ve learned the hard way, over the years, the danger of planning events that depend on or assume specific PC actions, as the PCs will inevitably do the opposite. I’ve had to re-learn it many times 😛 . In this session, there were multiple instances where I realized, to my horror, I had assumed the PCs would turn left, while they were determined to turn right. I was fortunate that they self-corrected onto the Golden Path before I had to take emergency action. I should know better by now.

But that brings me to an issue I’ve been trying to figure out lately: what to do when you place an opportunity for exposition in front of the player(s), and they just won’t ask the question? Taking away player agency to say, “You ask the guy about X,” is bad GMing, in my opinion. Allowing them to not get the important info isn’t ideal either. I don’t have a good answer for this yet.

Minor Issues

  • Rogers’ player was supposed to be out this week, but he showed up for the game anyway, and I wasn’t prepared for it. Therefore, I didn’t have any specific content in mind for Rogers. Worked out okay, anyway.
  • I missed the “maintenance” roll last week (3/103 Setbacks, “Spaceship Malfunctions”), so I made it up here
  • I stumbled a bit over accents and language issues, despite my practice during the week. The more I do it, though, the more comfortable I’ll get with it. But this also goes back to the “write it down” thing, too. I’m trying to remember to introduce the character/situation, and not try to carry the accent/etc. through the rest of the conversation.
  • Regarding the above: I used some Spanish with the watch-captain, and when asked to, didn’t translate it—I don’t know why I did that; I didn’t mean to
  • Shifty’s introduction and the surrounding events got a bit more jumbled than I intended
  • I totally forgot about Dora when the PCs started sneaking Shifty out of town. I guess that’s fine, since I really didn’t have anything specific for her to do. I hate when that happens, though…
  • There were a handful of events that got used out of sequence due to “forward progress”; the scene where they drink to Shifty after his recapture was supposed to happen after the hanging, but it didn’t make sense to wait at the time
  • There were some bits that were completely missed, like the rather-important revelation that Shifty’s “escape” wasn’t entirely accidental (but a ploy to find his crew)
  • I didn’t remember Plot Points until the moment the Tactics roll happened before the shootout, otherwise I might have had some better suggestions for their use other than re-rolls (though it ended up working out, in that regard)

Sea Dogs, Chapter I:IV, GM Debrief

Session Recap; Stream

GM confidence: 4/5. I was prepared for this one to get messy, and was pleasantly surprised when it didn’t. It basically came in two parts:

Île-à-Vache

I was afraid I’d overpowered the PCs, but in the spirit of “sandboxing,” I didn’t want to pull my punches here. But with some subtle disadvantages (no boat, and the need to get information before killing everyone), and clever placement of distractions, the players had the space to deploy their typical shenaniganry to their advantage. I was actually prepared for “normal” combat here, but that didn’t end up being necessary. The players finally used some Bennies, to good (and expected) effect. “Dora” and her pursuers were not a random event—that thread is much more important than it might at first seem.

I’ve long tried to figure out the best way to make suggestions to the players without feeling like I’ve handed them the solution. Most GMs rely on die-rolls for this: they make it, and you tell them the answer. I never liked this solution, because it means there’s a chance you don’t get to tell them that thing they need to know, and if that’s not so, there’s really no point in the die-roll. As it happens, this campaign has an outlet for this: the NPC crewmen. That is, if I need to make a suggestion, I can have the NPC crewmen give it to them. It gets the information to the players, and it makes the NPCs feel a bit more alive. Win/win. In this case, I had Mr. Bold deliver the suggestion to circle around and walk in from behind. I need to look for more opportunities to use this.

Travel to Santo Domingo

Now to the truly sandboxy part. This was a bit of good and bad, and as usual, it’s far easier for me to focus on what went wrong, minor though it was:

  • I discovered, in the middle of it, that my spreadsheet voyage calculator had a bit of a bug, which prevented me from setting the proper departure time. By the time we got to the end, I had forgotten, and I screwed up the narrative a bit. I didn’t realize the error until after the game, though, so it didn’t cause me any real stress.
  • I “misplaced” my weather data for the trip. I didn’t want to subject everyone to 15 minutes of dead-air while I dug around for it, so I just went with what I had on hand, correct or not. The players wouldn’t likely know the difference.
  • There was a glitch at one point, where my random event generator system kept telling me there was a “traffic” event after it had been determined that there was no traffic. It threw me off my game, a bit, at the time, though I realized afterward that I could have just generated some traffic anyway—I’m sure nobody would complain, “But we rolled no traffic?”
  • I had some content for Mr. McNeill—the (randomly determined) NPC-focus for the session—but I forgot to sort out where that content should fit. It got a little jumbled, though again, the players would never know.
  • We wrapped up at a spot that didn’t make for a good cliffhanger.

But some stuff went well:

  • The incident with the guarda costa was completely random. I didn’t mind the back-and-forth about signals—good fodder for some research afterward—though I would obviously rather have known those answers beforehand. I established the PCs’ level of “vulnerability” long before the campaign started, so I don’t feel the need to worry about them getting inappropriately belligerent towards a strong enemy. Plus, the shakedown was a fact-of-life I wanted to establish, anyway.
  • The ship “stations” map seemed to be well-received, and did its job. I think this will keep things nicely organized for the future (and potentially, for other games).
  • I added a travel checklist the players could see, which should also help keep the travel processes better organized, and we established an SOP. This travel segment went pretty smoothly as a result, and I expect good results in the future.

Overall, I felt pretty good about this session. There were some lessons learned, that I’m in the process of addressing, and that’s always good news for the remainder of the campaign. We’ll be missing a couple of players for the next session, so I decided to run a “side-mission” with the ones that are available—I did want to get away from the “adventure at every stop” tendency, but it fits here, under the circumstances. The trick will be how I merge the other PCs into the narrative for the session that follows. We’ll see.

Sea Dogs, Chapter I:III, GM Debrief

Session Recap; Stream

GM Confidence: 4/5. I thought this one went pretty well. Seemed like the players did too.

It started off with the “recap.” I basically went back over the whole previous session and straightened out the timeline, adding in all the elements I forgot, like making the planning rolls, introducing the crew properly, fixing some mistakes, etc. Regarding the planning roll: this was the second time I’d used it, borrowing heavily from mechanics established in Dungeon Fantasy 16: Wilderness Adventures, but due to the changes I’ve made since the previous usage, the PCs ended up with a lot more Plot Points to spend. We’ll see how they get spent. I had to retract my former advice regarding “leaving with the tides” as well—I know quite a bit about nautical matters these days, but I’ve still got plenty to learn—and that significantly changed the PCs’ post-sabotage plans once the regular timeline was resumed. I wanted to keep the whole thing short, but it ended up taking half the session. Oh, well.

Claude’s player decided to drop out of the group, at the last minute. It is a little disappointing, but it will be easier to run with fewer players, so there’s some benefit. Ironically (and conveniently), her Secret fired this session; it ended up playing out without her, and I was able to work it into one of the random events.

This was the first session where (finally) the PCs took to the open sea. That meant it was the first time making in-game use of the sailing spreadsheet stuff, which worked pretty well, but I discovered it needed some improvements (some of which I’ve already made). It was also the first time using the departure/under-sail/arrival checklists, which meant a lot of die-rolling—I was afraid that would be a mess. Afterward, I think it felt about right. The “repetitive” feel of it is entirely intentional; it’s an aspect of the life I wanted to get across, though it’s possible I’ll start allowing them to Take Average on those rolls down the road.

I’m using the “Interesting Times” interpretation of my Universe Reaction rolls to handle daily random encounters, which I combined with tarot to determine the nature of generated events. I did find myself hesitating a bit at first, but I think I’ll get used to it. It might be a good idea to come up with a few crewman/ship-specific events ahead of time, rather than the more generalized list I currently have. After-the-fact, I’m pretty sure the calculations were a bit off, but I’m not going to go back and fix it. The players won’t notice (unless they read this 😛 )

The events at Île-à-Vache were a bit last-minute, and I think they could have benefited from a bit more processing—it wasn’t bad, I just felt it needed a little more…something. I need to keep in mind for the future that such events should probably always include a “twist” of some kind, beyond the initial confrontation. The session ended on a much better cliffhanger than last time, too—though I hope I haven’t painted myself into a bit of a corner as a result.

Sea Dogs, Chapter I:II, GM Debrief

Session Recap; Stream

GM Confidence: 3/5. I really buggered this one up. I’d rate it worse, but I think the mess was, thankfully, mostly invisible to the players.

Wibbly-Wobbly

I thought I had everything properly organized, but “no plan survives contact with the enemy.” I suppose it could be accurately said that my failure here was the result of players doing what I should have expected, but did not. In hindsight, the first domino appears to have been my intent to have the “voyage planning session” occur after the “dive.” I expected all the PCs to participate in the Skill Challenge, and not make any real plans until after it was resolved. When some split off, it made more sense for them to start making voyage arrangements on the side, which would require them to know where they would be going first. (Payne already knew about Île-à-Vache, so they could reasonably plan it out, even though the Coin wasn’t yet in hand.) That meant they had to have the conversation before the dive—which would sensibly occur when they returned to the ship that night. Since I didn’t know they were going to split up until afterward, that meant I had to backtrack. The second fail was my one-the-spot decision to roll-up the entire Skill Challenge at once and sort it out afterward, which caused me to miss a bunch of events I intended to occur during the process, and muddled up the timeline even more. Those two combined with other mistakes, to make a complete mess of things, behind-the-screen:

  • I realized days later that I had completely forgotten the second clue from Old Tom, which will greatly affect the voyage planning (requiring a bit of backtracking next week)
  • For whatever reason, it skipped my mind that the process of getting freight/passengers/etc. takes two days, which meant my timeline needed to be extended (and some events could have occurred later); also, even though I did review the rules in Pyramid 3/97 “Medieval Sea Trade” beforehand, I didn’t actually make note of the skill needed to roll against
  • In spite of my extensive notes on the matter, I completely forgot to actually do the skill-rolls for the voyage planning process—I’ll have to backtrack next time and cover that
  • I have no idea why it didn’t occur to me that one of the PCs might actually try to seek out the captain of the Nijmegen and, y’know, talk to him. At least it’s got their curiosity going. It’s a shame I didn’t have any real detail on the character. That would have been a good idea…
  • I had forgotten how absolutely passive Davino’s player has always been, and I wasn’t prepared for his complete lack of response to his info dump (though, in my defense, I’ve not GMed a full campaign with him in it before)
  • There were a few events in town, and a number involving the NPC crewmen’s introductions, that I completely skipped, in the general confusion
  • It never occurred to me that someone on watch aboard the ship might just “yell at” the saboteurs in the water—I completely froze for a minute, not quite knowing how to respond; I think my use of Serendipity wasn’t quite in the spirit of the Advantage as written, also

It Wasn’t All Bad

  • The Skill Challenge actually went through more-or-less without a hitch, which surprised me—maybe we’ve finally figured it out
  • Once again, my pacing was pretty accurate—it ended roughly where I expected
  • As GM or player, I’m not usually the “accents” guy; this was my first time attempting French—good or bad, I felt mostly comfortable doing it, which is a big step for me. (I’ll have to listen to the stream later and see if it makes me cringe 😛 )
  • Planning big operations always takes a lot of table-time; I tried to speed it along, and I don’t think it dragged on excessively, so that’s a win

Unsolicited Information

During the Skill Challenge, I ended up volunteering some background information regarding goggles and diving bells. It was related, and potentially useful, whether or not it was “interesting.” But it was unsolicited, and frankly, I doubt the players would ever have asked for it, because it probably never would have occurred to them. I find myself wondering what a GM should do here? You want them to have the info, but if you volunteer it, it can feel forced, and can be mistaken as “important” when it isn’t really. I don’t have an answer (yet).

Conclusion

I like to think I generally learn from my mistakes, and that means I should have learned a lot from this session. But we’re going to be moving out of the relative safety of the kiddie-pool next week, and into the deep end of the unknown (that is, stuff I haven’t prepared for as thoroughly, due to the sandbox nature of the campaign). That will be the real test of my GMing ability.

Sea Dogs, Chapter I:I, GM Debrief

Session Recap; Stream

GM Confidence: 4.5/5. Finally, after (literally) 20+ years in the making, the Sea Dogs campaign officially began. I had the usual first-session-jitters, but it went pretty much according to plan. I felt like everyone was engaged throughout. The session splits into three basic parts:

Part I: The Duel

I was pleased with how the “duel” segment turned out, overall. I made a point to find some way to highlight each of the PCs’ character; I had some difficulty figuring out how to do that for Hayden, but he ended up being the volunteer, which worked out perfectly. I did not think through the medical aftermath, though; I really should have read up on that beforehand.

Part II: The Priest

I had to make a lot of changes to the “priest” scene at the last minute to fill some plot holes, and it could have benefited from cooking a little longer, I think. But it had the effect I was looking for. I hadn’t actually expected Davino’s player to hesitate to the degree that he did, but at least it had occurred to me, and I planned for the servant offer to do it for him in that event. I did not consider he would bring another PC along, though, but that ended up working to my advantage, as Rogers’ reaction added a little more conflict/drama to the scene. There’s actually a lot more exposition to get through to set everything up, here, but I decided to have the servant catch up to Davino later, rather than slog through it all in one go. We’ll see if that was the right call.

Part III: Old Tom

I was a little disappointed that the “random encounters” on the road came up nil, but I want to stick to the plan—it’s supposed to be sandbox, after all. I discovered too late that, although it had occurred to me the PCs might want to talk to the assassins, I hadn’t actually considered their response. I should have paid more attention to their equipment, as well. But to be fair, I really procrastinated to that end. Next time, better, I hope. I did have an idea after the game that I might come up with some sort of “random mook personality trait” table, just to give them a little individual flavor. I had a short Action 2 Chase in mind for the runaway at the end of it, but the PCs didn’t try to run him down. That’s fine. It was probably unnecessary.

Other Stuff

My pacing was spot on; it ended roughly where I expected. And on a good cliffhanger. On the down-side: I didn’t give out any bennies—new mechanic—as my mind was occupied with too many other things at the time. Some of the interludes were a little stumbly. I missed getting a reference image for the jungle trail. I totally forgot the monkey until the fight at the end. But those were all pretty minor, and I’m confident I can improve, now that the first-session dread is past.

Going Semi-Mapless

Last Saturday, for the Olympus group, I ran another one-shot from our Supers campaign. I did a bit of an experiment I had been meaning to try for a while now.

Tactical combat—in pretty much any system, not just GURPS—tends to drag, for obvious reasons. We have experimented a few times with eliminating the tactical-map and going entirely theatre-of-the-mind. Sometimes it works. It does spare everyone some of the brain-cycles we use to process the tactical situation according to the grid, and reduces some weird meta-behaviors resulting from minding the rules. I’ve found that it helps—or maybe requires—some kind of graphic to establish the geography, to keep everyone on the same page about what’s where. But we’ve also done that, and in at least one instance, the confusion over who can see what, who can reach whom, etc., left a little to be desired. “Was he over there, or over there?” “How far is that?”

My experiment was to go “semi-mapless.” The players had no map, just an image reference of the combat area (in this case, first the alley, and second, the stairwell). But I, as GM, did have a tactical map, fully gridded and all that. I was tracking positions and moves based on the players’ descriptions, but I tracked facing, distance, etc., as usual, using my map grid. They had all the benefit of “mapless tactical combat” while I was able to keep everything (mostly) organized behind-the-scenes.

Afterward, I call it a success. There were a couple of places where I could have communicated the situation better—I think I need to remind the player-on-deck of the geography when their turn comes up. I felt free to fudge the details here and there, for simplicity, so it wasn’t too tedious, on my end. I definitely expect I’ll use it again in the future.

Table News, 7 Oct 2019

Well, it looks like the Sea Dogs is about to happen for the Olympus (Sat) group, finally. For real this time. I wrote up the introduction almost a year ago here. It should kick off at the end of October, or beginning of November. Unfortunately, that leaves me with very little time before the onset of the “Silly Season”—the end-of-year holiday season, where half the group tends to bail a lot for family reasons—which means either taking a break from the campaign (right after it starts) or dealing with constant delays and random player absences. At this point, my assumption is the former. Therefore, the current plan is to do the “Session Zero” planning session and campaign intro, and then break for the holidays, until the beginning of next year. Sad but unavoidable. But it does give me a little longer to prep, so there’s that. I’m feeling pretty good about it, though.

I have no idea what’s in store for the Core Group (Fri). I’m still leaning in a generally Car Wars direction, but any real effort there is still spinning its tires at the starting line.

Universe Reaction, Extended

grand_universe_by_antifan_real1

Some time ago, I introduced both of my player groups to my Universe Reaction idea. It has seen extensive re-use since then. We’ve found it quite useful. Along the way, I had planned to post some examples of how it might be used. I’m finally getting around to it now. (Since I don’t have much else to post about at the moment.)

Universe Reaction, Examples

Positive/Negative

Simple concept. Provides an answer to a yes/no question, like “Will it rain?” with a bit more granularity.

<=0 No, And+
1-3 No, And
4-6 No
7-9 No, But
10-12 Yes, But
13-15 Yes
16-18 Yes, And
19+ Yes, And+
Enough

This one is for questions like, “How much ammo do we find?” It depends on a rough idea, at least, how much is needed.

<=0 None at all
1-3 Hardly any
4-6 A little/half
7-9 Not enough
10-12 Almost enough
13-15 Enough
16-18 More than enough
19+ Plentiful
Timing

Actually, this is one of the earliest questions I was trying to answer that resulted in the idea of the Universe Reaction. It revolved around how early or late an “appointment” occurred, or what sort of delays a PC might experience in rush-hour traffic.

<=0 No-show
1-3 Really late
4-6 Late
7-9 A bit late
10-12 On time
13-15 A bit early
16-18 Early
19+ Really early
Match

This question originally revolved around “scrounging” and how useful a found item might be to whatever-it-is. But it could obviously have much wider applications as well.

<=0 Worst possible match
1-3 Very bad match
4-6 Bad match
7-9 Poor match
10-12 Not quite good enough
13-15 Good enough
16-18 Close match
19+ Exact match
“Interesting Times”

By “interesting,” I mean the Chinese curse sense—May you live in interesting times. This question evolved from an attempt to work out some “random events.”

<=0 Most interesting (negative)
1-3 Very interesting (negative)
4-6 Interesting (negative)
7-9 Not interesting (maybe a little negative)
10-12 Not interesting (maybe a little positive)
13-15 Interesting (positive)
16-18 Very interesting (positive)
19+ Most interesting (positive)

Table News, 3 Jun 2019

And the wheel keeps turning…

Due to one of the Olympus/Saturday players deciding to take a summer hiatus, I got a bit derailed. Now, instead of running Generica next, I’m going to be revisiting the After the End concept (previously a Core Group/Friday campaign) with a different “antagonist.” It won’t happen until the fall, most likely. As a proper Google Earth-powered “sandbox” like its predecessor, there won’t be a ton of pre-prep, so there’s nothing really standing in the way whenever the go-signal is given. I’m feeling pretty good about it right now. But there’s a fair amount of time between now and then, wherein anything can happen, so who knows? I expect the prep-work I did on Generica won’t go to waste, though; I had already discussed the idea of a concurrent campaign for Friday, and as I have nothing planned for Friday at the moment, that could become a thing.