Reed's Website

Project: Counting-Up Party Game

Printable cards here!

Inspiration

The mechanic of a group counting up via cards is directly from "The Mind" designed by Wolfgang Warsch. That game restricts all communication to promote tension and uncertainty. The game described here is more ridiculous and unwieldy.

The idea of switching communication methods was inspired by the classic parlor game "Fishbowl", later immortalized into the mechanics of "Monikers" by Alex Hague & Justin Vickers.

Name ideas

I need a name for this game. Just going to brainstorm ideas here:

  1. Count Away
  2. The Count
  3. The Counting
  4. Count Together
  5. Count Up
  6. Order Up
  7. Order In

Log Book

Tue Dec 19 07:45:22 PM PST 2023

By the time I'd started this page, I'd already played the game at 3 different parties and gotten really positive feedback.

I recorded all of the communication method details I had on my most recent version of the cards into a JavaScript data structure in a new page file on my site here

Tue Jan 2 10:33:04 AM PST 2024

Future:

I had a random side thought about constraints-based programming in web development. E.g. the constraint "this content should fit comfortably inside its container". How would you test that in JavaScript (outside a browser)? I don't know of a way. But within a browser, I know a test for that:

  1. Make the content overflow: auto
  2. If a scrollbar appears, then it doesn't fit.
  3. If no scrollbar appears, then it fits.

But the only way to see if that constraint would hold up is to run the program in the browser environment, because there's no simulation for the complex rules of the browser.

And here's where Playwright comes in. Playwright is a headless controller for a browser. So if I could ask Playwright to run my site, and verify my constraints live, then I'd have a live constraint solver.

For this project, I could imagine that being very useful for making some constraint-based assertions on the shapes of cards.

Sat Apr 27 12:06:37 PM PDT 2024

I had an idea of how to solve "the one problem" which brought me back to this game. What's "the one problem?" The original rules of this game had the numbers always counting up from the lowest to the highest. Unfortunately, if you got the number 1 in your hand, you knew immediately you could play that, because it was guaranteed to be the lowest. That meant whoever had the 1 had a better strategy (immediately play the card) than the fun strategy (follow the communication method). This game was supposed to be fun first, so one person not having fun was an immediate failure for me in the role of the game designer. Worse, if someone played 1 immediately and someone else had 2, they could play their 2 immediately next! And 3, and so on!

So, I had an idea for how to fix this, but it complicated the game a bit. I felt like I'd have to try iterate more versions of the game to work out the kinks of the new, additional complication. And to make more incremental progress, I thought I'd have to make more cards. I wanted to automate some bit of the process of making the cards for a couple reasons. One, I wanted to start to work towards a cleaner version of the cards. Second, I wanted to make many versions of the deck with slight variations to test out different gameplay ideas. And I didn't want to keep using the hand-made version of the game anymore anyways because the first version I made on index cards was getting a little worse for wear.

I began to make a generated printable page on my website so I could upgrade from hand-drawn-and-cut cards to stylistic, printed cards. My friend said he would help me laminate, and I wanted a visual I could be proud of before I did that. Laminating it somehow felt significant enought to warrant prior effort, though this was probably one of those useless mental blocks.

I made a page for the cards and got to work.

I had to research how to make a printable page. I had done this before to make an easy resume builder, but it had been a while.

I learned about a new tool! In Chrome DevTools (not sure about other browsers), under the three-dot menu in the top right -> More tools -> Rendering -> Emulate CSS type select "print" to help simulate

I found this interesting project (github) and online where some people worked on a generic, reusable tool for making the kinds of cards I wanted to make in HTML.

Sun Apr 28 07:46:54 PM PDT 2024

I went to the library for a test print. Some interesting results. First, the measurement of poker cards I found online 2.5in width by 3.5in height was over by 1/32in width and 1/16in height. I was surprised to find the border radius I found, 1/8in worked perfectly via CSS.

I felt silly when I realized I hadn't printed any of the cards with English on them.

Mon Apr 29 01:37:36 PM PDT 2024

I went back to the library for more printing, this time with my laptop. I found energy there to focus on coding. I refactored all my cards to use a single component since they'd been converging to a similar structure. I also added some runtime checks to assert that all my ducks were in a row, for example that I had a symbol for each tag I used.

I made card backs with the number and communication symbols big on the back. It took some programming to make the pages interspersed, 9 cards then 9 backs on the next page to line up with Chrome's printing dialog.

I differentiated the card backs based on the type of card. This proved to be a bit of a coding challenge because I needed to interleave the pages. I.e. Page 1 was 9 card fronts, and Page 2 was 9 card backs, and they should all line up exactly.

Mon May 20 12:22:33 PM PDT 2024

I found an error where two cards had the wrong back. This suggested that I had the backs reversed. I should reverse the horizontal ordering of the card backs so that they match up when the two pages are placed back to back.

I learned it was difficult to match up the backs and fronts of papers when printing double sided on inkjet printers to within a centemeter accuracy. At least that was true of the commercial printers I used for free at the local library (thank you library!). This resulted in the backs of cards looking unrefined, imprecise. I thought of a way to make it a little less of an eye-soar. I changed the borders on the backs of the cards to all-white, so that a slightly-off border wouldn't show through.

I learned from people holding them in their hands that the two kinds of cards looking so similar added a small amount of friction all over the place. Someone pointed out the wisdom of the Cards Against Humanity decks: the different types of cards were totally inverted, immediately comprehensible as different. I tried to differentiate my card types by inverting the color schemes.

Sat Jun 29 12:48:15 PM PDT 2024

I made the two different decks into starkly different color palletes, using black backgrounds for one and white or light gray for the other. I also fixed the bug I found with the backs being mismatched where if a row contained cards of different types, because the back and front pages were printed back-to-back, they would be misaligned. A bit of programming fixed that.

Future: I changed the name of communication cards to "Directives". I looked at "Dossiers" from classic spy/war films/props for more thematic inspiration.

I considered putting indicators on the card for "right" and "wrong", but I couldn't think of how to do it. I took my previous prototype in my hands, fanned the cards, and stared at a mirror on my bathroom. I tried to play out the game with other people in my mind. I felt only a little insane. Eventually I saw that it was pretty confusing understanding the order of the cards fanned out in someone's hand. From the holder's perspective, they'd be lowest-to-highest, but from another person's perspective, staring at the back, they'd be in the reverse order. So before indicating "right" and "wrong", I wanted to help people understand "greater than" and "less than", i.e. what order the person was holding the cards in. So for the next prototype, I put "less than" and "greater than" symbols ("<", ">") in the corners of the cards. On the reverse, they were the opposite direction, and also on the reflection on the bottom of the card they were in the opposite direction. So the system could account for someone holding the cards in their hand in whatever orientation, and they could "fix" the symbols simply by flipping the card over.

Future: Later I came back and considered how to indicate what was "right" and "wrong", if that was actually important. One theory I had for how to build tension and stakes was to make it more clear how many "strikes" (wrong guesses) the team had, and I thought the "wrong" indicator, bright and obnoxious would help establish the raising stakes and tension. And an equally garish "right" indicator might make success feel more awesome.

Tue Jul 2 06:05:39 PM PDT 2024

Considering names, I looked up "Numberlines" as recommended by Jed and Griffin. I didn't love the name but two separate people saying they liked it compelled me to check it out. I did find a game called Numberline (no "s"), but it didn't seem to be a huge release. I wasn't sure of the legal implications for using such a similar name. I also thought about "Numsense", but that name is also not original. Another name I considered was "Flaw In Order," but I felt like I would need to follow that name up with a detective theme, and I wasn't sure I could.

Fri Jul 5 03:56:03 PM PDT 2024

At a playtest this week I attempted a couple different rulesets. In the first round, we used the old ruleset; each player held their card face down in front of them, and the goal was for each person to flip over their card in order, from lowest to highest. The "one" problem was definitely present, since the person with the "1" card immediately flipped their card over. The next rule set was for all the players to swap cards with each other, still face down, until they were in order, without revealing a single one until the end. In that version, the Director (the player who picked the Directive card) had to have the lowest card, the person to their left had to have the next higher, all the way around the group until the person on the Director's right had the highest card. The final ruleset was similar, except the Director held onto their card (not swap), while all the other players swapped their cards to put them in order around the Director. The benefit of this cascading ruleset was that it introduced slight changes to make the game more complicated incrementally, slowly until the "one" problem was solved.

For me, the first round was the only fun and light and quick one. The other two rounds, especially the last one, were a slog. Some people in the group found it an engaging puzzle, but it wasn't the type of puzzle I wanted to play. In my view, it involved keeping too much information in your head. Especially in the last round, everyone wanted to collaborate to figure out what all the other players had before they made any swaps.

Players weren't sure if they should minimize swapping. There wasn't any rule against swapping a lot, but it would probably be a bad idea to swap a lot because you could "lose" a card, forgetting whose card you were holding. That would be really boring to try to figure out. Well, boring might be too inspecific a description. Because this might be an interesting challenge for a group that was really good at the rest of the challenge.

For the next playtest, I wanted to try the same concept of increasing the difficulty round after round. But I didn't want to do the swapping with the hidden information. Maybe it would be easier to do the swapping without the hidden information part. That is, everyone can look at any card they swap with. And maybe they can only swap twice? That sounds like obnoxious book keeping. On top of that, the "optimal number of swaps" is not the fun puzzle i want to play. So for the next playtest, I thought we could try keeping the cards in each players' hands (instead of the Director collecting them and ordering them in their hand). But players could only flip their card when the Director directed them to by pointing at them and saying "flip!" I tried to think of another a more thematic command, but none came quick. And similar to in the previous playtest, in the more advanced round, the group would need to have the cards flipped in order starting with the Director's card, wrapping around.

Maybe it would be helpful for me to attempt to write out what I think is fun about this game, so that I can refocus on my goal. The fun part is people trying to figure out how to express the number 17 given the directive "Vehicles." It's nonsense (hense my desire to make the game called "numsense"). The ordering puzzle presents a devilishly straightforward framework which beckons the players with the question, "come on, this is a simple game, you can do this can't you?" That is basically a trojan horse which leaves the players' guards down for the highly uncomfortable actual task of saying song lyrics which include the number 6.

Also during this playtest I gave out "strikes" if people said any numbers at all. While conversing, many people couldn't seem to avoid saying "one." This was effective for reminding people of the

Also during that round I came up with a name I really love, "Countability."

Mon Jul 15 12:01:36 PM PDT 2024

I added some more Directives, "Movie titles,", "Flavors," "Vacations," and "superheroes." Then I realized I already had Movie Titles. Whoops. I almost added "countries" and "US States," but I held back. Something about them irked me. That they might turn into a trivia competition, with people feeling bad about not knowing the relative sizes of different nations or territories. I was 50/50 on the decision, my logic did not feel sound to me, but I went with my gut.

I took another stab at writing out the rules on cards of their own. This was the last major component I wanted to work hard on before trying to connect with a visual designer.

Future: I fixed my card front and back printing algorithm to allow me to print the rules cards filling both front and back. Then I combined the key card into one of them.

Future: I changed the background color for my tag icons so that they didn't blend in with the background

I also removed the less than and greater than symbols from the cards, since I had moved on from the version of the game where players fanned the cards in their hands. And I also removed the pips from 2 of the corners, so that they only remained on 2 of the corners.

And I removed the saboteur card. I'd never actually playtested it. The game was fun without it.