I rose on Tuesday to my alarm at 6:30, made coffee, and was soon in the office writing the blog. I had a game at Richard’s at 9:30, but I wanted to finish the blog before heading there. I pushed through writing the story of Monday and the colonoscopy (a word I have now learned to spell), the prep, and the recovery. Again, thanks to Joan S for taking me and bringing me back. I also edited the transactions in Quicken to keep my view of my assets clear and available every day. This is for my information and to ensure nothing disappears due to an unexpected transfer.
I read my email (mostly deleting the ones I should unsubscribe from) and read the New York Times. Again, it is not that I am politically liberal; I just find the writing and the way the paper assembles a story educational. Their stories, cooking information, and editorials are excellent.
I find my focus and complete the story in a few minutes, take a shower with some care, as I am only a day away from my procedure, and then do the usual shave and so on. I am running ten minutes late. Beaverton traffic is returning to the pile-on of back-to-school, and I add another five minutes to my tardiness.
The rest of the trip was unmemorable and the usual end-of-rush-hour slowdown. I arrived fifteen minutes late, and James and Richard had the game ready. We talked and knew something was wrong. We missed something in the play. We do not have the proper setting to play on. We discovered that others had made the same error, and we found that we had missed a log on some of the planets we sent way missions to. Oops. We replay the log and discover a story arc that allows us to reach a sector we could not reach in our current state. We make updates and corrections.
The app that runs the game, ISS Vanguard, informs us that we need to set aside extra time, that the mission will be casualty-laden, and that failure will be devastating. Rather dramatic. I have to leave at 2, and we start at 11:20, only to discover that we have a battle to fight and that we are playing under alternative rules to allow it. In this game, we have to make decisions and then apply the results. We make mostly good ones and lose two crew members. I cannot describe the material here, but it was a very immersive experience, and we did not know if we would win.
I managed to leave at 2, then enjoyed the early-afternoon traffic, made it to Office Depot to get some supplies and make copies of the character sheets for my Call of Cthulhu tabletop role-playing game (CoC), and picked up some double-sided tape to build some 3D props. With that, I headed home and tried to build some of the props. I managed to get the sword built. The buildings I was hopeless on (I missed the instructions in the box).
I finished the food I had delivered from The Cheesecake Factory last night for a late lunch. I started another episode of Star City and tried to relax. It is always hard for me before performing as Game Master or Keeper; I can usually find my way once we get started. I pick up Emma, and we make it to Rune & Board by 5:15, since Beaverton traffic isn’t on the back roads Apple navigation uses to get us there. Emma assembles the room for me and then even most of the buildings. We skip the island one as it is complex and a video is recommended. Yikes!
It is just M@ and Emma again. The store focuses on collectible card games and figure-based wargaming, such as Warhammer 20K. This is where the money is, and the staff are card folks. All good.
Eternity at Sea is the adventure from the H.P. Lovecraft Historical Society, featuring amazing props (assuming you buy the prop box and game from them), some 3D elements, and even audio to play. It is set in 1920s Astoria, Oregon, and is creepy and a slow burn. It is good for a slow two-session or a rushed one-session play. It creates a building horror or creepiness that you don’t find in the more grab-your-Tommy-gun of some 1920s CoC adventure or the run-and-hide. This is, and I have played with Sean Branney before, the author, a more indirect cosmic horror play. It is a stand-alone story and perfect for this one-time play I am doing.
Emma and M@ slowly unwound the story, explored it, and learned the terrible secret and fate of its characters. They enjoyed the experience, and I did manage to run it without too many mistakes. I think I would need some notes next time. CoC stories, props, and story arcs are complex, and it can be hard for me to keep all that straight, keep the game moving, answer questions, and play various characters. Still, it was fun.
With that done, we packed up, and M@ headed out. Emma and I went for drinks and a snack at The 649. Kyle was bartending, and the place had few customers. We each had a beer, shared some nachos, and talked about the game and about family. Emma is curious about the stories. We chatted about Ben and weddings, but I tried not to tell stories that were embarrassing to her Mother, Barb C, and Ben was a good neutral topic.
Emma let me know that Tuesdays are out for her games. I have not prepared any material yet for next Tuesday, and I think that with us not getting any other players, it would be good to stop anyway. More to come on that.
I returned home, finished the Star City episode, and then read and fell asleep. I dreamed brightly, but nothing I can recall now. I remember waking, unsure when the dream and reality started and ended, then returning to sleep and the busy dream.
I woke with the sunrise. I regret not taking any photos of the CoC game. Thanks for reading!
Alohawild (Michael Wild's) Website 