Tomorrow (Wed 10/16) at 7pm!!! Very excited to be part of this panel at the fabulous Ripped Bodice in Brooklyn! Hope you can join us! (Tickets required.)

https://www.therippedbodicela.com/brooklyn-events

Had a wonderful time at The Ripped Bodice last night!!! Excited for NYCC today!

(Photo above, left to right: Sarah Beth Durst, Carissa Broadbent, Amal El-Mohtar, and Sara Raasch)

Eeeeeeee! Just saw that THE SPELLSHOP is a nominee for the Goodreads Choice Awards 2024!!! Thanks so much! This makes my day! I'm so thrilled and so grateful! Voting is open now! 

https://www.goodreads.com/choiceawards/readers-favorite-romantasy-books-2024

I was so excited when Jamey Stegmaier’s Plans and Ploys  expansion for Tapestry  (published by Stonemaier Games) showed up in the mail. I’d  played a lot of Tapestry games with my social isolation pod (see my review for Tapestry  here) over the summer and I was eager to explore the new Tapestry cards and civilizations promised in the expansion. Beyond these updates, the Plans and Ploys expansion also includes a new game element (Landmark cards), new space tiles, a handy bag for drawing exploration tiles, and landmark place marker tokens which offer an easy way to identify which landmarks have already been claimed just by looking at the central board.

As soon as we unboxed Plans and Ploys, we invited a few of our friends over to give it a go. Our previous social isolation pod had disbanded with the spike in new COVID cases in our state (Iowa: ground zero for the pandemic once the fall semester of school started) and none of the members of our newly formed pod had ever played the base game before. So we weren’t sure whether we should play the base game without the expansion first or if the expansion was straightforward enough to merge into the base game in a way that didn’t prove too complicated for new players to understand. We spent a bit of time going over the base game rules with our friends and then read the rules addendum for the expansion together and decided to jump straight into playing with the expansion. It was a good decision. Everyone got into the flow of the game without any difficulty.

I played the Advisors civilization. This is a new civ from the expansion and I wasn’t sure if I was in love with its special abilities as compared to the other new civs I’d peeked at before we shuffled all the civs and randomly drew for each player.  One point per Tapestry card didn’t seem to amount to much, and at first I didn’t see the power in forcing others to take my Tapestry cards instead of drawing from the deck. But as the game unfolded, I quickly realized that I could use the giveaway power to purge less helpful Tapestry cards from my hand and churn through the Tapestry deck much quicker in search of the really powerful cards. Plus, I could influence my opponents’ behavior by giving them Tapestry cards that would encourage them to favor certain actions over others and then use the knowledge of what they were likely going to do for my benefit. For example, I might give someone a Tapestry card that strongly encouraged military track advancement and then play a Tapestry card myself that allowed me to pick an opponent and a track and copy the opponents movement on that track. Knowing that a specific opponent would likely play heavy on the military track for their next several turns allowed me to be more confident in my bet on that player and that track in conjunction with the track+opponent copy power of my Tapestry card.  Overall, the Advisors are well balanced and constructed civilization, as are all the others from the expansion that I’ve studied closely.

At the beginning of the game, each player was given a Landmark card and building. These are personal goals that allow a player to place a building on their Capital city map once the goal is met. All of the goals are fairly straightforward, but as with other games that feature personal player goals, players have to be careful not to become overly focused on their goal at the expense of general game strategy.

 

All of the new components packaged with the Plans and Ploys  expansion feature the same artwork style and the same quality of construction as those of the base game. The additions integrate very well in terms of gameplay and strategy too. I wouldn’t be surprised at all if Stonemaier revealed Jamey had done a Peter Jackson: Lord of the Rings  move with this game, designing everything all at once and just releasing it in separate parts as the base game and an expansion. I especially appreciated the new landmark tokens that saved me from that grumpy feeling that wells up inside of me when I realize someone else has already taken a track landmark I was eyeing. Now as soon as they claim a landmark from one of the tracks, the landmark token is removed, signaling its unavailability. Nice. 

Our game was really close in score as far as everyone could tell for most of its duration. I wasn’t sure I was going to win, but I was having a hell of good time playing the six, count them, SIX, civilizations I’d managed to acquire in the game due to some crafty manipulation of my technology cards in conjunction with track actions. I felt powerful. Very powerful. 

In the end, my husband Christopher won (but not by much) and I came in second. Our newbie players did pretty well at final scoring, especially considering they’d never played before and were playing against veterans.

I loved everything about this expansion. If you haven’t picked up the base game yet, call/email your local game store to reserve a copy (or order online from Stonemaier) and add Tapestry Plans and Ploys  to your order at the same time. You’ll want them both. And if you already own Tapestry, this expansion is calling your name. There’s still time for you to add it to your Christmas wishlist and if no one gifts it to you, you can give yourself a copy (you deserve it after surviving 2020!) when the new year rolls around.

-------------------------------------------------

Publisher: Stonemaier Games
Players: 1-5 (We played with 4)
Actual Playing Time (vs the guideline on the box): About 3 hours per game
Game type: tile placement, hand management, dice rolling, area control
Retail Price: $27 direct from the publisher https://store.stonemaiergames.com/collections/tapestry/products/tapestry-plans-ploys

Rating:

Jenni’s rating scale:
OUI: I would play this game again; this game is ok. I probably would not buy this game myself but I would play it with those who own it and if someone gave it to me I would keep it.
OUI OUI: I would play this game again; this game is good. I would buy this game.
OUI OUI OUI: I LOVE THIS GAME. I MUST HAVE THIS GAME.
NON: I would not play this game again. I would return this game or give it away if it was given to me.

The good folks at Stonemaier Games sent us a review copy of the newest expansion for Tapestry recently. We have the base game and the previous expansion, Plans and Ploys, in our game library. Arts & Architecture is designed by Jamey Stegmaier and Mike Young, with artwork by Andrew Bosley and landmark sculptures by Rom Brown. The expansion adds more of the familiar components: five new civilizations, six new capital city mats, 5 new landmark cards with landmarks, twenty new tapestry cards, and eleven new tech cards. Arts & Architecture also adds completely new features to the game, including an arts track with accompanying landmarks, twenty masterpiece cards, twenty inspiration tiles, and an upgraded science die to include iconography referencing the arts track.

The new arts development track is quite useful and thematically blends well with the overall concept of the game.

It gives you the opportunity to place more of your income buildings, score victory points for tech cards and exploration tiles, acquire masterpiece cards which provide benefits during income turns, and place inspiration tiles on your income mat over existing income tracks to improve the rewards gained during income turns. In the first few games I played (2 player), I concentrated heavily on the arts track, progressing to the end of it easily before game end, all the while also making steady progress on two of the base development tracks.

In the most recent game (4 player), I didn’t use the arts track much at all, which was a huge mistake, landing me in third place while the frontrunners leaned on the arts track significantly. I’ve previously noted in my review of Tapestry (https://www.thatswhatjennisaid.com/2020/07/board-game-review-tapestry.html) and Tapestry Plans and Ploys (https://www.thatswhatjennisaid.com/2020/12/board-game-review-tapestry-plans-and.html) that to win the game, you must diversify and progress on at least two tracks simultaneously, but to be careful trying to do much more than that or you’ll spread yourself too thin. With this expansion, I’ll amend that to note you’re unlikely to win the game unless you focus on the arts track as well as two of the base development tracks, as the arts track is really an enhancer for all the other tracks. It will be interesting to see how development track focus will need to be adapted when Stonemaier releases additional expansions for the game (anticipating a religion track at minimum; every civilization has its religious scholars).

The additions to the tapestry deck include a new ability type - continuous. These abilities begin when played and continue for the duration of the game instead of just the current era. There are also new tapestry cards that allow you to place landmarks on them for scoring as an alternative to placing the landmarks on the capital city (or on the map as some civ powers allow you to do). I did not have a chance to play any of the continuous tapestry cards during my recent games (although they look useful), and I passed over playing any of the landmark tapestry cards I acquired as they did not seem as beneficial as the other tapestry cards I had in my hand.  I don’t think I’m a big fan of any of the cards that let you place landmarks on the for points (including the new tech cards with this feature); I prefer to prioritize my city map for landmark placement first. Maybe I’m just doing it wrong, but I haven’t made use of my landmark cards at all, even in the games where I won by a large margin. They seem to be an entirely optional aspect of the game and not necessary for a win.

 

One more change with the Arts & Architecture expansion is another refinement of the civilization adjustments first introduced in the Plans and Ploys expansion. This fine tuning of civilization powers comes as a result of extensive real-world player testing and aims to rebalance the game for greater fairness. I think it might need further refinements because my husband Chris played the Architects civilization in our last game and the adjustment afforded him 30 VPs at the start of the game as some sort of handicap to balance out perceived weakness, but his city mat was so perfectly attuned to his civilization (the mesa) that he won in a landslide (80 points above the second place player).

Overall, I think that the Arts & Architecture expansion is a great addition to the Tapestry portfolio. It adds more variety, layers in additional ways to strategize and score, and provides some new opportunities for player interaction on the map, without causing any additional complexity. While it’s not a must have for the base game, it’s certainly a nice-to-have addition that I’m happy to recommend.

Beyond the details of the new expansion, I did want to take this opportunity to mention that with repeated plays of the base game as well as across the expansions, I’ve noticed that 4 player games are much more competitive than two player games (at least in our household). There isn’t a single time Chris and I have played the game by ourselves that I haven’t walloped him by 100+ points, yet when we play at 4 players, he has won twice or been neck in neck with the winner, whereas my scores are significantly lower. That’s got to be tied to the dynamics of how this game plays at higher player counts because it doesn’t make any sense that all on my own I could go from being a genius at 2 player to just average at 4 player.

--------------------------------------------------------------------------------

Publisher: Stonemaier Games
Players: 1-5 (We played with 2 and 4)
Actual Playing Time (vs the guideline on the box): About 3 hours per game
Game type: tile placement, hand management, dice rolling, area control
Retail Price: $45 direct from the publisher https://store.stonemaiergames.com/products/tapestry-arts-architecture

Rating:

Jenni’s rating scale:
OUI: I would play this game again; this game is ok. I probably would not buy this game myself but I would play it with those who own it and if someone gave it to me I would keep it.
OUI OUI: I would play this game again; this game is good. I would buy this game.
OUI OUI OUI: I LOVE THIS GAME. I MUST HAVE THIS GAME.
NON: I would not play this game again. I would return this game or give it away if it was given to me.

Expeditions is my favorite game in the Stonemaier Games portfolio to date. The game is a sequel to Scythe, and continues the narrative years in the future. It has taken everything I loved in Scythe and expanded on it, while chucking out everything I didn’t care for (the combat).

Designed by Jamey Stegmaier, Expeditions brings us into an age when a meteorite has crash landed into Siberia and things begin to go sideways for all who encounter it. One team after another sets out to investigate the crash site and they are never heard from again. No one knows what happened to them. Now it’s our turn to find out what’s really going on, each of us leading a competing expedition team into Siberia to bring back desperately needed answers.

During a game of Expeditions, all players are seated around the game board, which is made up of individually placed hex tiles laid out as shown above. At the bottom of the game board is an insert affectionately known as the base camp. The base camp holds the glory scoring track, some reminders for end game scoring, and serves as the physical start point for player mechs. Each player also has a small board – their faction board – in front of them, featuring both a guile (turquoise) and power (orange) marker as well as a track for these markers to move up and down during the game. A player keeps their hand of cards face up to the left of their faction board and plays cards from their hand to their tableau on the right side of their faction board.

All players perform their expedition work using mechs and meeples. The mechs are used to venture out from the basecamp, traveling from hex to hex (the move action) to gain access to the benefits printed on the tiles (the gather action). Mechs also provide asymmetrical powers for each player.  The meeples are used in conjunction with laying down cards in your tableau (the play action); most cards have a special ability that can be activated by placing a meeple of the matching color on the card when it is played. As with Scythe, players must select a different group of actions (choosing from move, gather, play, and refresh) to complete each turn. For example, if you moved and gathered last turn you cannot do so again this turn, but you could move and play, or gather and play, or refresh (this is where you pull all your cards from your tableau back into your hand and all your meeples back onto your player mat). A nice bonus is that on the turn after each refresh turn, you may do three actions instead of two.

The play action is the most complex action in Expeditions as it involves so many different abilities. You play a card from your hand to your tableau, gain the card’s core value (bump up your power and/or guile by moving your token up the track), and then optionally activate the card’s ability using a corresponding meeple from your available pool. Both the core value and the ability of a card may be enhanced if you meet certain conditions as specified on the card. As detailed in the rulebook, the card abilities can be instant or ongoing and include:

Rescue: take a card from your tableau and put it back into your hand and return any meeple to your available pool.

Gain: take a card from the indicated location (either one of the faceup cards between the hexes or the draw pile) and place it in your tableau; do not gain the core value or activate its abilities.

Discard: discard a card from your hand to your tableau; do not gain the core value or activate its abilities.

Trash: return the indicated component (card or token) from your player area to the box; it is out of the game.

Activate: activate another card’s ability without placing a worker on it.

Solve: pay the indicated solve cost on the card, gain the benefit shown below the solve cost on the card, and tuck the card under the top of your mat in the solved quests area; you must be on the indicated numbered hex to do this action and you can only solve 4 quests during the game unless otherwise indicated. The number of quests you complete is a factor in your end game scoring.

Vanquish: spend your power or guile (moving your token down the track on your faction board) to take the topmost corruption tile on the hex your mech is on; spend power to vanquish power corruption tiles (orange) and guile to to vanquish guile corruption tiles (turquoise). These corruption tiles are drawn blind from a bag and placed when the hex tile is first flipped.

The move action is pretty straightforward and most of the spicy adventure here is moving onto unexplored hex tiles to flip them over and see what benefits they offer and how much corruption someone will need to vanquish in order for everyone to gain access to all the benefits on the hex tile.   Because most of the game tiles are shuffled randomly and placed facedown, there is always variability in the layout and you never know what is going to be on the other side of an unflipped tile you’ve moved onto. Maybe the hex tile has the benefits you’ve been searching for, or maybe it’s no help to you at all right now.

The gather action is also pretty straightforward. You simply collect the benefits visible on the hex tile where your mech is located. These benefits are varied and include options like gaining more cards into your hand, gaining new meeples, and playing cards from your hand.  There are three special benefits that can be gathered: upgrade, meld, and boast, but these benefits only become available once all corruption on the tile is vanquished. Upgrading a card lets you pull an item card from your hand or tableau and tuck it under your player mat so that only the ongoing ability is visible. Now the item’s ability is permanently activated for you and at the end of the game each upgraded card is also worth victory points (coins). Melding a card is almost the same as upgrading one except you meld meteorites instead of items and when you tuck them under your mat you get a meld bonus as specified on the card, plus you receive all your previous meld bonuses again. Boasting is the action of putting one of your scoring stars on the basecamp boasting track, selecting one of the glory categories for which you have met or exceeded the goal. Once a player puts down their 4th scoring star, the end game is triggered and each player gets just one more turn. If you’ve played Scythe, or other Stegmaier designed games, this end game triggering mechanism and scoring is very familiar to you.

It’s easy to outline and teach the basics of how to play Expeditions, as I’ve done above, but solving the puzzle aspect of the game more efficiently than your opponents is hard to master and the answer to winning the game. It’s also what makes the game so enjoyable. The artwork is pleasant, the components are well made (as with all Stonemaier games), but the reason to buy this game is for the logic puzzle at the heart of it. You’ve got to take into consideration your mech special ability and how to leverage that to improve the efficiency of your process flow. You’ve got to time your refreshes just right in order to extract maximum value from your play, move, and gather activities. You’ve got to balance your work toward solving quests, upgrading items, and melding meteorites so that you’re in a position to place glory tokens for meeting the goals in these areas. And the unique aspect of this game wherein your hand is always laid down in front of you on the left of your player board means your possible play action choices are laid out for all to see, so you’ve got to keep a close eye on what your opponents are doing and how close they are to meeting the glory token goals and ending the game before you can complete everything you want to. And unlike in Scythe, nobody is coming to steal your resources, so it’s all thinking and no fighting.

I’ve a half dozen or more games of Expeditions under my belt, and some very close to winning scores, but I’ve yet to win a game. Still, I keep coming back for more, and I know that someday I might finally crack the puzzle wide open and figure out how to make every step of the process work together for my win.

Please note, for all you solo players out there, Expeditions comes with a robust automa mode.

--------------------------------------------------

Publisher: Stonemaier
Designer: Jamey Stegmaier
Artist: Jakub Rozalski
Players: 1-5 (We played with 3, 4, and 5)
Actual Playing Time (vs the guideline on the box): About 90 minutes per game
Game type: worker placement, hand management
Retail Price: varies; direct from the publisher https://stonemaiergames.com/games/expeditions/

Rating:

Jenni’s rating scale:
OUI: I would play this game again; this game is ok. I probably would not buy this game myself but I would play it with those who own it and if someone gave it to me I would keep it.
OUI OUI: I would play this game again; this game is good. I would buy this game.
OUI OUI OUI: I LOVE THIS GAME. I MUST HAVE THIS GAME.
NON: I would not play this game again. I would return this game or give it away if it was given to me.

What follows is the true and unredacted account of my tour of duty as a command leader for the Yin Brotherhood.

Map: 5p POK Kazadoom’s Notch Map generated on https://ti4-map-generator.derekpeterson.ca/

Factions: Yin, Yssaril, Nekro, Vuil’raith, Hacan.

Round 1 objectives: Engineer a Marvel (R1-1); Push Boundaries (R1-2)

Five experienced leaders gathered this weekend to prove themselves worthy. As the Yin, I found myself wedged between the Hacan (around the corner of a notch in the galaxy) and the Yssaril. Word had come down to the Blessed on Darien through our ambassadors and spies that both nearby factions were set on amassing larger fleets and armies, but to what end we were unsure. The Blessed discussed the matter at great length and decided our best defense was to rebuild our flagship the Van Hauge and to take control of as many planets as we could (more, at least, then our neighbors). That would allow us to stand firm in the face of any aggression.

As a command leader, I had heard the rumors not only of these rising neighbor armies, but also of some truly terrifying events taking place on the other side of the galaxy. The horrific Vuil’raith were actively recruiting with empty promises; telling factions whatever they wanted to hear to forge alliances. Left unchecked, they would surely seize and destroy our entire galaxy planet by planet. The Nekro Virus was also gaining strength on a planet nearby the Vuil’raith and while it was unclear who would come out the victor in the inevitable head-to-head match between them, I shuddered at the idea of either of them heading our way. Because I viewed Nekro and the Vuil’raith both as bigger threats to our Yin than Yssaril or Hacan, I decided to put all my efforts into leading my crew to Mecatol Rex as fast as possible. I knew that if we could successfully land and build up a presence, we could stand as a line in the sand against the wave of Nekro or Vuil’raith forces that would inevitably come crashing down upon us.

As time went on, I congratulated myself on recruiting warfare strategy experts and prioritizing our expansion to Mecatol Rex over building the flagship. It was the right choice. It had allowed me to maneuver our fleet onto the doorstep of Mecatol Rex. I had to explain to my Blessed brothers why we hadn’t built our flagship yet as ordered, but I pointed out that settling the planets along the way between Darien and Mecatol was in line with the orders given to seize control of new planets. Granted, we did not have more planets than our neighbors yet, but we did have more than we started with. I was sternly reminded to prioritize the flagship, especially since our spies had spotted the Hacan flagship (R1-1), but otherwise the matter was dropped.

End of R1 scores: Yin(0), Yssaril(0), Nekro(0), Vuil’raith(0), Hacan(1)

Round 2 objective: Erect a Monument (R2-1)

To provide the assistance I needed, I hired some well respected leadership strategy consultants. Their job was to provide me guidance on getting more out of my command, using the influence I’ve cobbled together. I’d been given a new objective by the Blessed – I was to gather the resources needed to build a monument to the brotherhood on one of our newly settled planets. I thought it absolutely ridiculous at a time like this. Word was that Hacan was also heading to Mecatol with a settlement force and the Blessed wanted me to make time for fundraising? Forget it. In my meetings with my brothers, I nodded and agreed on the importance of the monument, but secretly planned to prioritize what I deemed most urgent instead. Back at command, I forged ahead and reached Mecatol (MR1) before Hacan could do so. Built a space dock on her right away once construction was authorized, and then began amassing troops on the surface. At the same time, I was diligently managing the build of our flagship (R1-1) by our production teams back home on Darien.

Yssaril also finished their flagship (R1-1) and through some swift imperial strategy, settled enough new planets to control more than their neighbors (R1-2). Hacan got word that Vuil’raith had taken over a legendary planet in a distance sector (VS1) and in response intensified their own settlement efforts. In doing so, Hacan also found themselves controlling more planets than their neighbors (R1-2). Our ambassadors’ reports were increasingly worrisome – war was brewing and they were unsure where it would break out. And while the Vuil’raith were clearly planning something, the Nekro had gone completely silent. Our scientists on Darien continued their research, our production teams added more ships to our fleet, and we all waited for whatever was coming next.

Having established a settlement on Mecatol Rex, I called for an inaugural council meeting with the other leading factions. At this first meeting, we took up a couple of interesting proposals and passed a new law implementing technology that allowed all Alpha and Beta wormholes to connect.

End of R2 scores: Yin(2), Yssaril(2), Nekro(0), Vuil’raith(1), Hacan(2)

R3 objective: Discover Lost Outposts (R3-1)

Pleased with the completion of the Van Hauge, the Blessed advised that our intel had intercepted some encrypted communications about an objective the other factions’ were working on – to conduct in-depth explorations of their new settlements and identify any undocumented resources, pockets of political influence, or technology specialties. Any gains discovered during exploration were to be documented and written up in attachments to the planetary profiles faction leaders kept on hand for reference. I was told to keep on the efforts to settle more planets than our neighbors and to emphasis exploration of any new settlements. I was to report back when I’d successfully identified at least two different planets with enhancements worthy of documentation attachments. There was no more mention of the monument, and I was glad to have that off my to-do list. I decided to hire some tech strategy consultants to help develop new tech that could aid our explorations.

Soon after I’d turned my attention to new settlements and exploration, the Nekro launched a direct attack on my fleet guarding Mecatol. I’m not the best negotiator and had been unable to secure the contractors needed to implement an imperial strategy, but holding onto Mecatol was still imperative for blocking the advancement of Nekro or the Vuil’raith toward Darien. Additionally, we had built a good rapport with everyone on Mecatol and their influence on the council was powerful. So I dug my heels in and fought. A couple of my destroyer pilots kamikazed their ships into the Nekro fleet, but it was not enough to stop them. They held the airspace above Mecatol while at the same time building their flagship in another production facility they controlled elsewhere (R1-1). Luckily for us, they underestimated the fortitude and persuasiveness of our infantry. We were able to turn at least one of their advancing infantry against them and through the strength of our troops, we held the planet. Still, they did not leave the system, so we had to make peace, at least temporarily, with their looming presence above us.

There was a skirmish between the Nekro and the Vuil’raith as well, and there also, the Nekro had come out ahead. After the battle, Vuil’raith regrouped and turned their efforts toward building their flagship (R1-1). Nekro had also been reported to be gathering relic fragments as they conquered and explored, only instead of holding onto them to reassemble a relic, our spies came back with word they were purging them (NS1). While all of this was going on, Yssaril was quietly continuing to settle and explore planets. Our spies kept a close watch on them and every step of progress they made was immediately relayed to the Blessed. Eventually, my superiors sent me a reprimand via encrypted message wanting to know why I still hadn’t made more progress with the attachments when Yssaril had already done so (R3-1). Worse, the Hacan commander had managed to submit 2 attachments for planetary profiles under their control (R3-1) AND build a monument to their leadership (R2-1). Now the Blessed were jealous and angry and every communication from them I received reflected that. I had faith in my strategy, but I was going to have to have something more to show for myself when I spoke with my brethren. When I got word from my construction team that we’d build a third space dock across our systems in record time (YiS1), I forwarded the progress report directly to the Blessed, hoping it would soothe them.

Another council meeting was called, and even though I wielded the most influence of any leader present, none of the proposed legislation before the council interested me much. Certainly nothing to really shake things up in favor of the Yin. I mostly abstained from voting and mentally prepared for my upcoming status report meetings with the Blessed.

End of R3 scores: Yin(3), Yssaril(3), Nekro(2), Vuil’raith(2), Hacan(4)

R4 objective: Raise a Fleet (R4-1)

I really wanted to implement the famous imperial strategy I’d heard so much about, as when a faction holds Mecatol, it’s especially rewarding for them. But you need the right experts who know how to do it and Hacan always managed to grab that team it each time their contract came up for renewal. One time, even after they’d agreed to go work for another faction, Hacan pulled out some fancy datahub tech and persuaded them to come back over to work with them. So I never got my turn with them. After my research consultants rolled off their contracts, I reached back out to our warfare experts who were on the market again. I wanted to bring them back under contract for guidance in troop redeployments. We had a problem with ship crews’ that fulfilled a deployment order and then wanted to rest on location for an extended amount of time before being redeployed. They’d gotten their union involved and it was a mess and I hoped the warfare strategy team could persuade at least one of our most essential crew teams to head back out sooner than they’d planned.

At my next status meeting, my brothers were frank with me. They were encouraged by my construction feat, but I was not back in their good graces yet. They told me I was to build my fleet up to 5 in at least one system (R4-1), but preferably in as many systems as possible. They were also interested in the spoils from the cultural planets my crews had been settling and asked me to have at least 4 under my control (YiS-2). I was easily able to do both of these things, and so our working relationship was going very well. With the Blessed giving me some breathing room, I took time for planning my own goals and priorities.

Hacan had been making a lot of noise about taking over Mecatol and the Vuil’raith leveraged the general atmosphere of distrust and anxiety to approach me directly about a potential alliance. It might be just what I reported before – that the faction knows how to say whatever you want to hear to get you on their side. But it also might be that the rumors of their all consuming evil were vastly overdramatized. All I know is they gave me some useful tech that allowed my production teams to go above and beyond their production limits. And I agreed to look the other way should they decide they wanted to stomp out Hacan or Nekro. And why shouldn’t I make such a deal? They never did anything to me or our people whereas Nekro had attacked us. There were also confirmed reports that the Nekro had built an impressive monument to themselves on one of the planets they had recently assimilated (R2-1). And Hacan needed to be stopped before they got any more powerful. Recently they had amassed 5 ships in one system (R4-1), won a battle with their flagship (HS1), and come to control enough planets to give them 12 influence votes on the council (HS2). No doubt the Blessed would have been thrilled with the Hacan commander, were he set up to answer to them.

At our third council meeting, Yssaril, Nekro, and Vuil’raith reported they now each had at least one 5 fleet system to serve as deterrents (R4-1) for aggression. Thank God I’d prioritized that myself or the Blessed would have really been up my ass. Nekro passed around pictures of the monument they recently built. It was absolutely hideous. I made no bones about saying so and they deflected with slander that I was just salty about their blockade of Mecatol. As we brought each agenda item up for consideration, Nekro pushed hard to get a seemingly dull law passed. I should have figured out their angle sooner, but I was distracted by the Vuil’raith who were on me to pay back that tech share by voting for them on an upcoming agenda item. At the end of things, the law Nekro was pushing was passed (NS2) and with my influence, the Vuil’raith was selected by the council as the elected beneficiary of a boost to their military operations (VS2).

End of R4 scores: Yin(5), Yssaril(4), Nekro(5), Vuil’raith(4), Hacan(7)

R5 objective: Command an Armada (R5-1)

In my next debrief with the Blessed, I told them all that had happened at the council meeting. I warned them especially of Hacan’s growing power, but they didn’t take me as seriously as I’d hoped. The Hacan had not attacked us in any memorable fashion (perhaps an accidental ship collision here or there) and wouldn’t it be better for them to come out on top versus Nekro or Vuil’raith, the destroyer of worlds? I didn’t have the heart to tell them I’d already made some preliminary deals with the the Vuil’raith. Their minds were made up on the more pressing threat. The Blessed presented me with my latest assignment – build up my fleet to 8 ships in a single system. A show of force to deter Vuil’raith and Nekro. I tried to remind them our great strength was in our infantry and holding the ground (especially with our Yin Spinner tech), not our pilots, but they didn’t care to listen. They sensed my reluctance and offered up double the cash incentive if I could get it done before the next council meeting. I told them I’d work on it, but as usual, I had other plans.

As always, Hacan lured away the Imperial strategy experts when they came off their contracts so I reached out to our on again off again leadership consultants. I also focused on settling more planets, including a few intrusions into Yssaril territory. They were in the midst of a monument building project (R2-1) and completely distracted so there was no retaliation even though I’d braced for it. The Nekro and Vuil’raith faced off against each other aggressively again. The tension between all of the factions was growing but despite our petty grievances with each other, all of us kept our eyes fixed on Hacan.

Just before the council met again, word came in that Hacan, Yssaril, and Nekro had each managed to build up a fleet of 8 powerful ships (R5-1) within a system they controlled. Dammit! The Blessed were going to be upset with me again. At least I’d settled enough additional planets to outnumber my neighbors as they’d asked me to do eons ago (R1-2). The Vuil’raith had done this also (R1-2), facing the increasing threat of the Nekro at every turn. While I didn’t have the fleet count the Blessed had asked of me, all my planet settling and incursions into Yssaril territory had given me control of planets in the same system as other factions (YiS3), which provided great accessibility for continuing covert operations. The Vuil’raith commander reported to me through back channels that Yssaril was creeping into systems neighboring their home planet in our galaxy (YsS-1). Yssaril had also formed a loose, informal alliance with the Nekro. Under friend of my enemy logic, that made the Yssaril a new enemy of the Yin.

The fourth council meeting was extremely stressful. Hacan was confronted regarding their massive fleet build up and asked of their plans. Instead of answering the question, they reminded us how they’ve always been generous in trading with us all, and how they had rarely shown any aggression. But we weren’t buying it. The continual build up of their fleet and infantry had to point to something big they were planning. Hacan was given a mandatory military reduction directive from the council. They would be sent back out from the council meeting with a limit of 3 command actions, 3 ships max in any fleet, and only permitted to conduct two strategic actions until we met again, unless they could gain more influence through better leadership. It passed by a wide margin, and I have to say Nekro looked especially pleased. As much as I fear and hate Nekro, I do not trust Hacan and the Vuil’raith commander had said that was wise on my part.

End of R5 scores: Yin(7), Yssaril(8), Nekro(7), Vuil’raith(5), Hacan(9)

R6 objective: Manipulate Galactic Law (R6-1)

Nekro announced a bold move – they had instigated a scheme their lawyers had crafted to force their consultants into an automatic follow-on contract. Each other faction was now doing the same, utilizing a fine print clause to make it so. I knew the Blessed would be disappointed if I released our teams, so I let our contractors know I was exercising the fine print as well and they belonged to us for a little while longer, whether they liked it or not. I needed to keep the Blessed content. My ears still stung from the berating comments my brothers had laid into me during our last status meeting following the fourth council. How had I let so many other factions get ahead of us on fleet size? Didn’t I see the danger? Did they need to replace me or could I get my head on straight and get us into a position of power? If Hacan or another faction were to take control of everything, there was a good chance they’d shut down our genetic cloning operations. They were prejudiced against our ways. They didn’t understand the threat of Greyfire.

It was true that Hacan was exceedingly close to seizing control of everything, but I couldn’t see an easy path for me or my fleet to stop them. Perhaps if I had built up the fleet as the brothers had ordered, but it was probably too late for that to make a difference now. What I did do, was send a message out across all channels – even to the Nekro – that I pledged my support in temporary alliance to all who would seek to destabilize Hacan.

Nekro moved first, easily taking control of multiple Hacan systems (although Hacan managed to hold the planets). Vuil’raith charged in next, infiltrating the Hacan home system and taking an entire planet hostage until Vuil'raith agreed to stand down.

Meanwhile, I’d gotten an urgent dispatch from the Blessed. If I couldn’t take Hacan out militarily, the Blessed counseled that I needed to gain enough influence to impose even greater consequences on them during the next council meeting. To do this, according to their calculations, I needed to amass at least 16 votes of influence. So while all of the military operations against Hacan were going on, I moved into more of Yssaril territory to capture more planets so that we’d have a greater voice on the council. I also made a far reaching jaunt into Nekro systems thanks to one of our command heroes. I was bound and determined to collect enough planets under Yin control so that I would have the strength to stop Hacan. I also prioritized building out our fleet to 8 ships (R5-1). Better late than never.

Just before the fifth council meeting, both Vuil’raith and Nekro publicly announced they’d raised enough influence among their settlements to be in a position to heavily influence the next wave of galactic laws (R6-1). Nekro had also beaten up Vuil’raith badly in an anomaly (NS3) equidistant between their areas of control. And Yssaril had brought in a report of some new strategic tech they’d adapted (YsS2). As for Hacan, they came into the council meeting with their head down and shoulders slumped. They hadn’t been able to accomplish much of anything lately with the constant onslaught of attacks from all sides and the Vuil’raith hovering over their home planets. Did I feel sorry for them though? While I considered it, the Vuil’raith commander gave me a wink across the table. No, I did not feel bad for them at all. Yssaril proposed we give an official support of power vote to the faction that most aided the Hacan disruption. We were all in favor of that and passed the measure, but when it came time to decide who should receive the award, there was contention. Nekro made a good case for themselves, but we felt the honor belonged to the Vuil’raith and gave it to them instead (A1).

End of R6 scores: Yin(9), Yssaril(9), Nekro(10), Vuil’raith(7), Hacan(9)

R7: Subdue the Galaxy (R7-1)

I took news of all these developments (leaving out the wink from the Vuil’raith commander) back to the Blessed. They were extremely happy to hear the Hacan had stalled, even if it was temporary. We discussed the new problem – Nekro was gaining power and now they were on the verge of becoming unstoppable. In fact, they had assimilated not only our faction tech but Hacan’s! They were now able to seize control of any strategic contract team when needed during strategy contract negotiation windows. We could be faced with Hacan peeling away imperial strategy experts away from us and then Nekro peeling them away from Hacan. I told the Blessed that we had one last hope. The latest round of contract negotiations was approaching, and I was slotted last to recruit. My plan was to grab some strategic contractors who weren’t of any value to Hacan, but whose priority rank meant that I’d be given audience in my bid for total control before the other council members. If we could prove ourselves worthy, we could take control of the new empire before any of the other factions even got up to speak. I explained this would be possible because Yssaril always preferred to hire research contractors, Nekro would hire imperial strategy experts as it was the only way for him to win ultimate control, Vuil’raith would hire whomever they chose (they weren’t a threat to us), and then Hacan would take something they didn’t care too much about that was a higher number and then force Nekro to switch. The Blessed approved of my plan and suggested I continue to settle new planets – at least 11 outside of Darien – to give me firm footing on seizing total control. They didn’t have any new secret objectives to hand down to increase my power, but they said intel reports advised some of the relics could increase my power if I happened upon the best ones.

When strategy consultant negotiations began, I found I was wrong about Yssaril – their commander hired warfare experts instead of tech. But I was right about Nekro. And Hacan chose to hire tech experts instead of stealing away the imperial experts from Nekro. This was probably because they realized Nekro would just lure them back. So I hired some trade experts, knowing Hacan would not want to steal them from me. It was hard to leave the leadership consultants on the table, but I couldn’t risk losing them to Hacan if I hired them.

Based on my hiring choices, I held a better initiative than anyone else in the council except Vuil’raith. If everyone could just keep Nekro held back until the council was ready to meet again, and if I managed to find a powerful relic, I could seize control for the Yin.

With limited command actions due to a lack of leadership strategy consultants, everyone was careful with their actions. Except for the Yssaril of course, who kept stalling, as is their way. The faction commanders plotted in the open how to stop Nekro. It wasn’t going to be that hard. They didn’t have a massive fleet yet (they had the capacity but not the build out), nor did they have 11 planets outside their home system. They’d have to work for either. And work for them they did, but they were stymied at every turn by the Vuil’raith and perhaps once even by myself. The Nekro commander boasted about finally having more planets than their neighbors (R1-2), but that was truly too little, too late. Having neutralized the Nekro, and seeing the Hacan was still too weak to assume power, everyone’s attention turned toward Yssaril and our people, the Yin. It looked hopeless for me, so the focus remained on Yssaril who still held secret objectives that could bring them a measure of power.

I spent my time shoring up troops and ships on Mecatol and Primor, and as I turned in a handful of relic fragments, I prayed for a power granting relic. Nope. I pulled a relic that allowed me to destroy a planet. I would have to eventually face my Blessed brothers and explain to them why I had failed. My hopes dashed, I sent out my trade consultants. At least I could gather some trade goods to bring back to Darien. To my surprise, Hacan offered to give me 6 commodities in exchange for 2 trade goods and 2 commodities. It seemed to be for no particular good reason, but I suppose they needed the trade goods to continue rebuilding their fleet. They were not giving up yet on themselves. I accepted the trade as they truly seemed repentant and in no position to harm me.

To finish things up what I assumed would be my last tour of duty, I looked for a high value target to destroy. Something with a lot of infantry or some structures. Then, at least I could tell the Blessed I went out with a bang and the event would be listed in my biography. I found it in a Vuil’raith system adjacent to their home. I called a 1:1 meeting with the Vuil’raith commander. While he watched, I unrolled a map of our galaxy and pointed to one of the planets bordering his home system. “I choose this planet”, I announced, as I showed him mercy with an advanced warning to evacuate. With a horrified look in his eyes, the Vuil’raith commander said, “Please don’t”, and pledged the support of the Vuil’raith for a Yin Brotherhood throne (SFTT1). Adrenaline surging, I agreed in earnest. I had not seen this coming and it was going to make all the difference.

Suddenly the factions were buzzing again. We picked up the chatter on every channel we interception. Now *I* would have the first audience in a bid for the thorne. I had 12 planets outside my home system, proving the Yin brotherhood worthy of ruling. Could they stop me? Only Nekro and Yssaril were still under normal operations at the time; the Vuil’raith and Hacan leaders had gone on holiday until our next council meeting. Vacation or not, they were still in communication with Nekro and Yssaril. Scheming together, the entire council plotted against me. They tried to work out the easiest planets to take from our people to bring our planet count below 11. Nekro made an incursion into one my systems and took a planet. Then came wave after wave of Yssaril attacks. After reducing our territory to just 9 planets outside our home system, there was a pause. The pause and the realization I had been calmly waiting for. The Yssaril commander called for a 1:1 with me, and when I arrived she wanted me to answer a burning question. Had I already submitted proof to the Blessed that I had completed the objective I’d been given to produce 16 votes of influence? “I have not”, I replied with a smile. “And how much influence does the Yin hold at this moment?” “TWENTY-SIX votes of influence”, I replied, with an even bigger smile. There wasn’t enough attacking and stalling in the world for Yssaril to knock us down below 16. I could buy 9 votes in trade goods alone, 4 from my heavily guarded home system patrolled by our suicide leaning flagship, and much more spread across the 6 or seven systems I controlled.

The Yssaril commander studied the situation from every angle. It was impossible. She had overlooked the key information – that I had finished my last tour of duty meeting both public objectives and she’d only stripped one of them from me. There was nothing she could do. She ended her tour of duty, dejected. Just before our next scheduled council meeting, Vuil’raith called a press conference on the steps of the council building to announce that they had won a measure of power by completing a secret objective they’d been given. (VS3). He also announced he had two planets with attachments under his control (R3-1). The crowd cheered for him. Everyone was really warming to these alleged monsters of the galaxy. And then I took to the steps and announced that our faction - the Yin brotherhood - who had peacefully resettled Mecatol and reinitiated the galactic council, were leaning on our 16 votes of influence to seize complete and total control of the galaxy. A gasp was heard from the crowd. And then cheering. Immense cheering from all sections of the crowd.

And that is how Yin took the unexpected Win.

End of R7 scores: Yin(12), Yssaril(9), Nekro(11), Vuil’raith(10), Hacan(9)

Last year I reviewed Expeditions and ranked it #1 among all Stonemaier games on account of the challenging intellectual puzzle it presents. This year I have played my way through the new expansion, Gears of Corruption, and I’m delighted to let you know that it makes the base game even better. That the expansion so cohesively builds on the base game should not be a surprise to anyone who closely examines the original box for Expeditions. All expansion components perfectly fit in that box including the 2 new mechs that nestle in the placeholder cubbies clearly made for them.  That can’t be coincidence. There might a few features rolled into Corruption of Gears that were developed as a result of consumer feedback on the base game (I’m looking at you, wild meeple), but my theory is that Stonemaier did a Lord of the Rings maneuver with this game and its expansions, designing the entire game with most of the additions integrated up front, and then breaking it into base + expansions for marketing and distribution.

Here’s a detailed breakdown of the components and features in Gears of Corruption:

 

• 2 new mechs
• Both new mechs use map tokens as discards to gain a benefit. The Scarecrow adds an extra action to your refresh turn while the Mole lets you access hex actions covered with corruption tokens. The Mole felt especially powerful in play.
• Replacement mech mats for the original mechs + 2 new mech mats for the new mechs
• The new mech mats are GREAT. They have inset spaces for the guile, strength, and action tokens to prevent player components from sliding off the mat during player.
• Hero worker meeples
• These meeples function as wildcards, and everyone is given one at the start of the game. This speeds up play and helps avoid the heavy disadvantage for the 3rd player and after who can’t get to the gain worker hex on their first turn.
• Replacement discovery card for one of the original cards in the base game + 5 new discovery cards
• The cards are all items and most if not all of them provide ongoing benefits in the form of when you do X also do Y
• 7 mech cards
• These cards are used for drafting/assigning a mech mat to each player and they also provide a list of starting resources to shorten the length of the game
• 12 corruption cards
• These cards are used both to control an additional mech on the main board (representing a malicious presence among us) that inflicts penalties on players whose mechs it would otherwise bump into AND to provide additional corruption targets for vanquishing by players. If all the corruption cards are vanquished, the corrupted mech wandering the board returns to the box, the threat eliminated. Three cheers to the player who accomplishes that!
• 4 pairs of new starting cards (character + companion)
• The new character/companion combos are pretty standard but one of the pairs (Baaliahon & Zephon) plays off the corruption card scoring added with this expansion. I played as this fellow and was competitive in all my games. A+ would recommend! ***Interesting side note: While I was researching the origin of the name Baaliahon (turns out to be a Phoenician name that means so that Baal will favor), I came across the website for the artist and worldbuilder on Expeditions, Jakub Rozalski. He’s got fantastic stories and lore for the game as well as additional artwork on the site and I encourage you to check it out at https://jrozalski.com/projects/JvAvPZ
• 6 new corruption tiles in lower values that the base game
• These tiles have a strength of only 2, making it easier to remove them.
• 6th player capacity
• Playing with an additional player DOES increase the game length, but this is well balanced by the time saved thanks to the new hero worker meeples and mech cards
• Additional coins & map tokens

-------------------------------------------------------------------------

Expeditions Gears of Corruption is a fantastic (although not absolutely mandatory) expansion for players who love the base game, like me. But this is not one of those expansions that fundamentally alters the overall feel or play of the game so if you’re among those that didn’t go gaga for the base, this will do nothing to change your mind. Yep, I see some of you over there complaining about the solitaire racing aspect of Expeditions and lack of strong player interaction, and to you ladies and gents I say go back to Scythe where you belong.

--------------------------------------------------------------------------

Publisher: Stonemaier
Designer: Jamey Stegmaier
Artist and Worldbuilder: Jakub Rozalski
Players: 1-6 (We played with 3, 4, and 6)
Actual Playing Time (vs the guideline on the box): About 90 minutes per game
Game type: worker placement, hand management
Retail Price: varies; direct from the publisher https://stonemaiergames.com/games/expeditions/gears-of-corruption/

Rating:

 The Victorian novelist Anthony Trollope, on a tour of the United States, passed through Utah, and decided to drop in on Brigham Young. It did not go well. From Trollope's autobiography:

"I did not achieve great intimacy with the great polygamist of Salt Lake City. [...] He received me in his doorway, not asking me to enter, and inquired whether I was not a miner. When I told him that I was not a miner, he asked me whether I earned my bread. I told him I did. "I guess you're a miner," said he. I again assured him I was not. "Then how do you earn your bread?" I told him I did so by writing books. "I'm sure you're a miner," said he. Then he turned upon his heel, went back into the house, and closed the door."

Alt text: Anthony Trollope. Looking, as usual, exactly like a miner.

Alt text: a stylish woman in a coat, who is emphatically neither an elephant nor a bear. Not everyone is.

 

1) Order the fish in a restaurant on a Monday. It'll be three days old. 

2) Base-jumping. He just doesn't see the appeal.

3) Cheat on his wife. Sandra is his world. 

4) Open a new battlefront without adequately securing supply lines first. This one probably won't come up. But still, he'd never do it. Look at Napoleon. 

5) That. He'll do anything for love. But. 

Edit: For some reason, a lot of people seem to be complaining that none of these have anything to do with dishwashers. Why should they? Our dishwasher expert knows a lot about dishwashers, sure, but they're not his whole life. Get some perspective, people.

Seventy-nine years ago, the era of atomic weapons began with the Trinity test. My novel about J. Robert Oppenheimer and the Manhattan Project is The Oppenheimer Alternatvie, and, in my humble opinion, it’s the best of my 25 novels: “Incredibly realistic: the characters, locations, the era, and even the science. I felt like I was […]

In the latest episode of their tightly-wrapped podcast, Ken and Robin talk vampire firewalling, the espionage of Jan van Eyck, weird war mummies, and the Quasi War.

Nomadland [US, Chloé Zhao, 5] When her town closes down in the wake of its gypsum mine’s closure, a self-reliant widow (Frances McDormand) moves into her van and joins the ranks of the nomad subculture, people who rove the US, taking whatever hard work they can get and living out of their vehicles. Rooted in social realist cinema, marked by a triad of transcendent qualities: poetic visual beauty, an indelible central performance and a deep love for the characters from the writer/director.

This is from Searchlight, formerly Fox Searchlight, now part of the Disney empire, so you’ll get a chance to see it. Likely as part of awards season, whatever the heck that’s gonna look like this year. Normally I don’t spend festival slots on titles with distribution but that’s out the window in the COVID-verse.

(At the moment cinemas are open, with distancing, here in Ontario but if you look at the numbers we’re in the early denial phase of a reimposition of lockdown measures. Whatever the deal is I don’t plan to be inside a theater in any foreseeable time frame.)

Her next project is a huge pivot from poetic verite dramas like this and The Rider— Marvel’s The Eternals. 

Memory House [Brazil, João Paulo Miranda Maria, 1] Racist harassment from German co-workers drives dairy worker to vengeance. Blunts the political anger of its subject matter with enervating pacing.

Another Round [Denmark, Thomas Vinterberg, 4.5] Burned out high school teacher (Mads Mikkelsen) embarks with three colleagues on an experiment to enhance their performance by maintaining a blood alcohol level of 0.5% throughout their days at work. Not only an original booze movie, but a big one, full of turns and ambiguities, and an utterly masterful performance from Mikkelsen.

Shadow in the Cloud [New Zealand, Roseanne Liang, 4] When an WWII RAF Flight Officer (Chloe Grace Moretz) boards a Samoa-bound cargo plane bearing a mysterious package, a monstrous gremlin on board is just one of the surprises. Enclosed space horror-action thriller tips an 80s-style hat to Carpenter and Cameron.

---

Capsule review boilerplate: Ratings are out of 5. I’ll be collecting these reviews in order of preference in a master post the Monday after the fest. Films shown on the festival circuit will appear in theaters, disc and/or streaming over the next year plus.

The Inconvenient Indian [Canada, Michelle Latimer, 4] Essay-format documentary examines the Indigenous struggle for sovereignty and cultural reclamation in North America, as hosted by novelist Thomas King and inspired by his nonfiction book of the same name. Makes its case through cinematic language, pushing the archival footage and talking heads format to the background.

Beginning [Georgia, Dea Kulumbegashvili, 4] Depressed wife of a pastor bears the brunt of a persecution campaign from a local man hostile to their minority Baptist faith. The camera acts as a pitiless eye in this harsh, austere drama of pervasive male oppression.

I Care a Lot [UK, J Blakeson, 3] Corrupt legal guardian (Rosamund Pike) who slaps unsuspecting seniors into care facilities to bleed them dry triggers a cat-and-mouse game when her latest prey (Dianne Wiest) turns out to be the mother of a wealthy gangster (Peter Dinklage.) Engaging thriller— until it betrays the contract it has established with the audience.

Concrete Cowboy [US, Ricky Staub, 3] After yet another expulsion from school, a troubled teen (Caleb McLaughlin) gets dumped for the summer with his father (Idris Elba), who belongs to Philadelphia’s threatened culture of inner city horse owners. A rich social milieu is the star of the show in this affirming drama, which could do with a stronger drive to activate its protagonist.

Lift Like a Girl [Egypt, Mayye Zayed, 4] From ages 13 to 18, under the tutelage of a volcanic, motormouth coach, with a rubble-strewn lot on a busy Alexandria street, weightlifter Zebiba trains to be a champion. Fly-on-the-wall documentary inhabits a hardscrabble community powered by loving verbal abuse.

The coach and his key athletes denigrate the skills of male lifters, while constantly referring to the girls as boys, urging them to man up, and telling them they need to grow balls if they want to win.

---

Capsule review boilerplate: Ratings are out of 5. I’ll be collecting these reviews in order of preference in a master post the Monday after the fest. Films shown on the festival circuit will appear in theaters, disc and/or streaming over the next year plus.

City Hall [US, Frederick Wiseman, 4] The latest of Wiseman’s distinctive epic-length observational documentaries studies the quotidian, procedural and human moments of human life as seen through the processes of municipal government in Boston, as held together by the thoughtful charisma of Mayor Martin Walsh. Improbably absorbing as always, this institutional cross-section offers a beguiling vision of an oasis of good government in the USA.

In a normal year I’d wait for the four and a half hour Wiseman documentary to arrive on television rather than taking up two time slots to watch it from the confines of a cinema seat at TIFF. But this is not such a year and with a digital screening you get a pause button when you need it. This is bound for PBS and due to the breadth of its subject matter will serve as an excellent introduction to those unfamiliar with this pillar of the documentary form. Or track down 2017’s Ex Libris, about the New York Public Library. In North America Wiseman’s filmography can be found on the Kanopy platform, which you may be able to access through your public library system.

The Father [UK, Florian Zeller, 4] Retired engineer (Anthony Hopkins) struggles to piece together the confusing reality of his living circumstances as his daughter (Olivia Colman) copes with his progressing dementia. Impeccably performed stage play adaptation puts the viewer inside the contradictory shifts of the protagonist’s subjective viewpoint.

Forget Draculas and Cthulhus. This is the real terror.

Summer of 85 [France, Francois Ozon, 4] Love between two young men in a French beach town leads to a bizarre crime. Teen emotions run high in a sunlit melodrama of Eros and Thanatos.

---

Capsule review boilerplate: Ratings are out of 5. I’ll be collecting these reviews in order of preference in a master post the Monday after the fest. Films shown on the festival circuit will appear in theaters, disc and/or streaming over the next year plus.

1. Wages growth slows faster than expected but still exceeds inflation  ABC News
2. Real wages are growing at highest rate since 2020. But it’s unlikely to last  Sydney Morning Herald
3. SBS On the Money: Wages growth slows but real wages turn positive  SBS News

1. Outback Queensland residents spend thousands on flights, grapple with Qantas service changes  ABC News
2. Airlines that love competition: Do you see pigs fly?  Sydney Morning Herald
3. Predictably, domestic airfares surged after the collapse of Rex. There aren’t many good solutions  The Conversation
4. Report finds just how much airfares spiked since end of Rex. One route doubled  The Canberra Times
5. Qantas’ single excuse for fare price hike  news.com.au

John Pesutto chalks up a first-time victory over Jacinta Allan in latest Resolve poll  The AgeView Full coverage on Google News

1. As it happened: Donald Trump ally taunts Kevin Rudd; WiseTech shareholders launch class action  Sydney Morning Herald
2. Ditching Rudd over Trump insults would be ‘worst possible signal’: Turnbull  Sydney Morning Herald
3. Senior Liberal calls for Rudd to be sacked after Trump advisor suggests US ambassador is on thin ice  9News

1. Murder charge after beloved Elvis impersonator found dead after karaoke night  9News
2. Beloved Elvis impersonator allegedly murdered after karaoke night  Sydney Morning Herald
3. Love Island winner's best mate is accused of killing beloved grandad - after the Good Samaritan had tried to h  Daily Mail
4. Video: Elvis impersonator named as alleged murder victim  WAtoday

When asking for a pledge, the fundraiser has many informational advantages over the donor. Simply asking for the proper amount ensures that a donor will consider giving at the level you request. Starting out with a sufficiently high donation request amount allows you to find your donors preferred level of giving as rather than targeting the amount which is the lowest possible amount that a donor can possibly give to your campaign.


If a donor could give more to their charity, they probably would. When donors who maintain a strict charitable budget and give a fixed amount annually hear requests for support that are above the amount which they are willing to give, they let fundraisers know just how much they are willing to give and when they intend to give it. In the rare event that a donor is offended by large or additional requests, a skilled fundraiser can apologize for the offense and leave the donor feeling good about the level of support which they do give.


There is no downside to “asking high”.




Becoming a better fundraiser is a continuing process. There is always more to learn and more skills to master.

The conclusion to this article will be posted here in the coming days.

Registration is now open for National O.T.O. Conference XIV, to be held in Denver, Colorado, August 3-6 2023. NOTOCON is normally held every two years, but it was canceled in 2021 due to the pandemic, so this will be our first NOTOCON since 2019.

The deadline to propose a presentation for National O.T.O. Conference XIV in Denver, CO, is May 10, 2023.

For potential speakers, a handy FAQ full of useful information is available here.

This was a big week in space, from Curiosity stumbling upon sulfur crystals to an exoplanet discovery and a major advocacy effort.

Detonating a nuclear weapon on or near an asteroid is one of several options for defending the Earth from an impact. Here's what nuking an asteroid might actually do, and why it isn't always the best option.

Europa Clipper is a big spacecraft with big solar panels, all so it can perform a big mission. The galaxy is big too, and a Planetary Society member painted it that way.

China is in the early stages of planning a huge space observatory to help answer the matter of whether we are alone in the galaxy.

A Planetary Society-funded project to understand asteroids achieved its main goals and scientific objectives this year.

NASA is preparing to launch its flagship mission to explore Jupiter’s moon Europa. Launching sometime in October 2024 and arriving in 2030, the mission will explore the icy world with a subsurface ocean that scientists think could have conditions favorable to life.

For a mission that doesn’t aim to find alien life, Europa Clipper may come surprisingly close.

The European Space Agency (ESA) is preparing to launch a mission to study the aftermath of DART's impact on the asteroid moonlet Dimorphos.

Europa Clipper will soon head for Jupiter's icy, potentially habitable moon. Without the advocacy efforts of The Planetary Society and our members, the mission may never have been possible.

NASA’s Europa Clipper spacecraft launched today aboard a SpaceX Falcon Heavy rocket from NASA’s Kennedy Space Center in Cape Canaveral, Florida.

Sneak peek — tray, citrus chess board, serving board.

We just made the decision to ship the remaining copies of Feast to us. There are about 800 left, out of the original 2000 copy print run. Which is a lot of copies, but given that we were originally scheduled to launch March 2020, and had to cancel an entire summer’s worth of scheduled bookstore […]

The great bear himself finally turns up... bloody late as usual.
After waiting a while for the second bear to arrive...the cutting and hacking could begin.
The plastic was very tough to get through with my craft saw. After what seems an age, the great heavy head fell off and the Orcs cheered. They soon stopped when they saw the angry head being wired into place.




I had to try a couple of different fur techniques, for this chunky, thick fur, I went for the classic GW wolf pelt look. This is the one where you cut lots of little triangles into the putty and push them up.
Beorn laughs at his new coat... Hopefully that's a good sign he likes it.
I did take the opportunity to bulk up his hump while applying the putty. I will also add some to his forelegs and make them a bit more shaggy.

Table of Contents

1. Dynamic Bindings
2. The problem
3. The solution
4. Dynamic slots
5. The context
6. Summary

Dynamic Bindings

Common Lisp has an important language feature called dynamic binding. It is possible to rebind a dynamic variable somewhere on the call stack and downstream functions will see that new value, and when the stack is unwound, the old value is brought back.

While Common Lisp does not specify multi-threading, it seems to be a consensus among various implementations that dynamic bindings are thread-local, allowing for controlling the computing context in a safe way.

Before we start experiments, let's define a package to isolate our namespace:

(defpackage "EU.TURTLEWARE.BLOG/DLET"
  (:local-nicknames ("MOP" #+closer-mop "C2MOP"
                           #+(and (not closer-mop) ecl) "MOP"
                           #+(and (not closer-mop) ccl) "CCL"
                           #+(and (not closer-mop) sbcl) "SB-MOP"))
  (:use "CL"))
(in-package "EU.TURTLEWARE.BLOG/DLET")

Dynamic binding of variables is transparent to the programmer, because the operator LET is used for both lexical and dynamic bindings. For example:

(defvar *dynamic-variable* 42)

(defun test ()
  (let ((*dynamic-variable* 15)
        (lexical-variable 12))
    (lambda ()
      (print (cons *dynamic-variable* lexical-variable)))))

(funcall (test))
;;; (42 . 12)

(let ((*dynamic-variable* 'xx))
  (funcall (test)))
;;; (xx . 12)

Additionally the language specifies a special operator PROGV that gives the programmer a control over the dynamic binding mechanism, by allowing passing the dynamic variable by value instead of its name. Dynamic variables are represented by symbols:

(progv (list '*dynamic-variable*) (list 'zz)
  (funcall (test)))
;;; (zz . 12)

The problem

Nowadays it is common to encapsulate the state in the instance of a class. Sometimes that state is dynamic. It would be nice if we could use dynamic binding to control it. That said slots are not variables, and if there are many objects of the same class with different states, then using dynamic variables defined with DEFVAR is not feasible.

Consider the following classes which we want to be thread-safe:

(defgeneric call-with-ink (cont window ink))

(defclass window-1 ()
  ((ink :initform 'red :accessor ink)))

(defmethod call-with-ink (cont (win window-1) ink)
  (let ((old-ink (ink win)))
    (setf (ink win) ink)
    (unwind-protect (funcall cont)
      (setf (ink win) old-ink))))

(defclass window-2 ()
  ())

(defvar *ink* 'blue)
(defmethod ink ((window window-2)) *ink*)

(defmethod call-with-ink (cont (win window-2) ink)
  (let ((*ink* ink))
    (funcall cont)))

The first example is clearly not thread safe. If we access the WINDOW-1 instance from multiple threads, then they will overwrite a value of the slot INK.

The second example is not good either, because when we have many instances of WINDOW-2 then they share the binding. Nesting CALL-WITH-INK will overwrite the binding of another window.

The solution

The solution is to use PROGV:

(defclass window-3 ()
  ((ink :initform (gensym))))

(defmethod initialize-instance :after ((win window-3) &key)
  (setf (symbol-value (slot-value win 'ink)) 'red))

(defmethod call-with-ink (cont (win window-3) ink)
  (progv (list (slot-value win 'ink)) (list ink)
    (funcall cont)))

This way each instance has its own dynamic variable that may be rebound with a designated operator CALL-WITH-INK. It is thread-safe and private. We may add some syntactic sugar so it is more similar to let:

(defmacro dlet (bindings &body body)
  (loop for (var val) in bindings
        collect var into vars
        collect val into vals
        finally (return `(progv (list ,@vars) (list ,@vals)
                           ,@body))))

(defmacro dset (&rest pairs)
  `(setf ,@(loop for (var val) on pairs by #'cddr
                 collect `(symbol-value ,var)
                 collect val)))

(defmacro dref (variable)
  `(symbol-value ,variable))

Dynamic slots

While meta-classes are not easily composable, it is worth noting that we can mold it better into the language by specifying that slot itself has a dynamic value. This way CLOS aficionados will have a new tool in their arsenal.

The approach we'll take is that a fresh symbol is stored as the value of each instance-allocated slot, and then accessors for the slot value will use these symbols as a dynamic variable. Here are low-level accessors:

;;; Accessing and binding symbols behind the slot. We don't use SLOT-VALUE,
;;; because it will return the _value_ of the dynamic variable, and not the
;;; variable itself.
(defun slot-dvar (object slotd)
  (mop:standard-instance-access
   object (mop:slot-definition-location slotd)))

(defun slot-dvar* (object slot-name)
  (let* ((class (class-of object))
         (slotd (find slot-name (mop:class-slots class)
                      :key #'mop:slot-definition-name)))
    (slot-dvar object slotd)))

(defmacro slot-dlet (bindings &body body)
  `(dlet ,(loop for ((object slot-name) val) in bindings
                 collect `((slot-dvar* ,object ,slot-name) ,val))
     ,@body))

Now we'll define the meta-class. We need that to specialize functions responsible for processing slot definitions and the instance allocation. Notice, that we make use of a kludge to communicate between COMPUTE-EFFECTIVE-SLOT-DEFINITION and EFFECTIVE-SLOT-DEFINITION-CLASS – this is because the latter has no access to the direct slot definitions.

;;; The metaclass CLASS-WITH-DYNAMIC-SLOTS specifies alternative effective slot
;;; definitions for slots with an initarg :dynamic.
(defclass class-with-dynamic-slots (standard-class) ())

;;; Class with dynamic slots may be subclasses of the standard class.
(defmethod mop:validate-superclass ((class class-with-dynamic-slots)
                                    (super standard-class))
  t)

;;; When allocating the instance we initialize all slots to a fresh symbol that
;;; represents the dynamic variable.
(defmethod allocate-instance ((class class-with-dynamic-slots) &rest initargs)
  (declare (ignore initargs))
  (let ((object (call-next-method)))
    (loop for slotd in (mop:class-slots class)
          when (typep slotd 'dynamic-effective-slot) do
            (setf (mop:standard-instance-access
                   object
                   (mop:slot-definition-location slotd))
                  (gensym (string (mop:slot-definition-name slotd)))))
    object))

;;; To improve potential composability of CLASS-WITH-DYNAMIC-SLOTS with other
;;; metaclasses we treat specially only slots that has :DYNAMIC in initargs,
;;; otherwise we call the next method.
(defmethod mop:direct-slot-definition-class
    ((class class-with-dynamic-slots) &rest initargs)
  (loop for (key val) on initargs by #'cddr
        when (eq key :dynamic)
          do (return-from mop:direct-slot-definition-class
               (find-class 'dynamic-direct-slot)))
  (call-next-method))

;;; The metaobject protocol did not specify an elegant way to communicate
;;; between the direct slot definition and the effective slot definition.
;;; Luckily we have dynamic bindings! :-)
(defvar *kludge/mop-deficiency/dynamic-slot-p* nil)
(defmethod mop:compute-effective-slot-definition
    ((class class-with-dynamic-slots)
     name
     direct-slotds)
  (if (typep (first direct-slotds) 'dynamic-direct-slot)
      (let* ((*kludge/mop-deficiency/dynamic-slot-p* t))
        (call-next-method))
      (call-next-method)))

(defmethod mop:effective-slot-definition-class
    ((class class-with-dynamic-slots) &rest initargs)
  (declare (ignore initargs))
  (if *kludge/mop-deficiency/dynamic-slot-p*
      (find-class 'dynamic-effective-slot)
      (call-next-method)))

Finally we define a direct and an effective slot classes, and specialize slot accessors that are invoked by the instance accessors.

;;; There is a considerable boilerplate involving customizing slots.
;;;
;;; - direct slot definition: local to a single defclass form
;;;
;;; - effective slot definition: combination of all direct slots with the same
;;;   name in the class and its superclasses
;;;
(defclass dynamic-direct-slot (mop:standard-direct-slot-definition)
  ((dynamic :initform nil :initarg :dynamic :reader dynamic-slot-p)))

;;; DYNAMIC-EFFECTIVE-SLOT is implemented to return as slot-value values of the
;;; dynamic variable that is stored with the instance.
;;;
;;; It would be nice if we could specify :ALLOCATION :DYNAMIC for the slot, but
;;; then STANDARD-INSTANCE-ACCESS would go belly up. We could make a clever
;;; workaround, but who cares?
(defclass dynamic-effective-slot (mop:standard-effective-slot-definition)
  ())

(defmethod mop:slot-value-using-class
    ((class class-with-dynamic-slots)
     object
     (slotd dynamic-effective-slot))
  (dref (slot-dvar object slotd)))

(defmethod (setf mop:slot-value-using-class)
    (new-value
     (class class-with-dynamic-slots)
     object
     (slotd dynamic-effective-slot))
  (dset (slot-dvar object slotd) new-value))

(defmethod mop:slot-boundp-using-class
  ((class class-with-dynamic-slots)
   object
   (slotd dynamic-effective-slot))
  (boundp (slot-dvar object slotd)))

(defmethod mop:slot-makunbound-using-class
  ((class class-with-dynamic-slots)
   object
   (slotd dynamic-effective-slot))
  (makunbound (slot-dvar object slotd)))

With this, we can finally define a class with slots that have dynamic values. What's more, we may bind them like dynamic variables.

;;; Let there be light.
(defclass window-4 ()
  ((ink :initform 'red :dynamic t :accessor ink)
   (normal :initform 'normal :accessor normal))
  (:metaclass class-with-dynamic-slots))

(let ((object (make-instance 'window-4)))
  (slot-dlet (((object 'ink) 15))
    (print (ink object)))
  (print (ink object)))

ContextL provides a similar solution with dynamic slots, although it provides much more, like layered classes. This example is much more self-contained.

The context

Lately I'm working on the repaint queue for McCLIM. While doing so I've decided to make stream operations thread-safe, so it is possible to draw on the stream and write to it from arbitrary thread asynchronously. The access to the output record history needs to be clearly locked, so that may be solved by the mutex. Graphics state is another story, consider the following functions running from separate threads:

(defun team-red ()
  (with-drawing-options (stream :ink +dark-red+)
    (loop for i from 0 below 50000 do
      (write-string (format nil "XXX: ~5d~%" i) stream))))

(defun team-blue ()
  (with-drawing-options (stream :ink +dark-blue+)
    (loop for i from 0 below 50000 do
      (write-string (format nil "YYY: ~5d~%" i) stream))))

(defun team-pink ()
  (with-drawing-options (stream :ink +deep-pink+)
    (loop for i from 0 below 25000 do
      (case (random 2)
        (0 (draw-rectangle* stream 200 (* i 100) 250 (+ (* i 100) 50)))
        (1 (draw-circle* stream 225 (+ (* i 100) 25) 25))))))

(defun gonow (stream)
  (window-clear stream)
  (time (let ((a (clim-sys:make-process #'team-red))
              (b (clim-sys:make-process #'team-blue))
              (c (clim-sys:make-process #'team-grue)))
          (bt:join-thread a)
          (bt:join-thread b)
          (bt:join-thread c)
          (format stream "done!~%")))  )

Operations like WRITE-STRING and DRAW-RECTANGLE can be implemented by holding a lock over the shared resource without much disruption. The drawing color on the other hand is set outside of the loop, so if we had locked the graphics state with a lock, then these functions would be serialized despite being called from different processes. The solution to this problem is to make graphics context a dynamic slot that is accessed with WITH-DRAWING-OPTIONS.

Summary

I hope that I've convinced you that dynamic variables are cool (I'm sure that majority of readers here are already convinced), and that dynamic slots are even cooler :-). Watch forward to the upcoming McCLIM release!

If you like technical writeups like this, please consider supporting me on Patreon.

Superbowl



View Comic!

1. Why Virat Kohli, Jasprit Bumrah were missing from Perth nets; India ramp up privacy amid Manchester United-like security  Hindustan Times
2. Virat Kohli in focus: Intense net session begins for upcoming Test series against Australia  The Times of India
3. Virat Kohli in Australia for BGT: A timeline  India Today
4. Black veil of secrecy: India begin training in privacy in Perth  ESPNcricinfo
5. India to play intra-squad warm-up match at WACA on Friday ahead of Australia Tests but BCCI denies public viewing  Hindustan Times

1. Melania Trump's 'I am the most bullied person' video viral as she 'rejects' Jill Biden's tea invite  The Times of India
2. Melania Trump declines invite to meet Jill Biden over Mar-a-Lago raids when FBI ’snooped through her wardrobe’  Mint
3. Jimmy Kimmel again mocks Donald Trump for Melania's ‘interesting’ decision to…  Hindustan Times
4. Biden Invites Trump To White House, But Why Is Melania Refusing To Go?  News18
5. Melania Trump To Skip White House Meeting With Jill Biden: Report  NDTV

1. 3 Children, 3 Women Missing After 10 Suspected Kuki Militants Killed In Encounter In Manipur's Jiribam  NDTV
2. Manipur on boil: 2 more bodies found, 6 missing  The Times of India
3. Additional paramilitary forces rushed to Manipur amid spike in ethnic violence  Hindustan Times
4. Letters to The Editor — November 13, 2024  The Hindu
5. 2 men found dead, 6 of family missing day after militants killed in Manipur  India Today

Full Article