Birds of a Feather win screen: Everyone made it, score 485

P3: Reflection – Noé Chicas-Aranda

The types of systems games I enjoy are ones where players can dictate their own gameplay experience, such as Root. Players choose a faction that aligns with their playstyle, and even within that faction they have multiple different ways of playing. That is to say, I value player agency in games, but without overwhelming players with too much information.

When making Birds of a Feather, that was the first thing I kept in mind: how do we give players autonomy over their choices and what they do? That was also the biggest challenge. In the first part of our game, players didn’t have to think much. The game ramped up, but that meant the first act was really easy and people just spammed through it. This made me panic, and I started asking myself: is our game actually fun?

I asked my teammate, is our game fun? IS OUR GAME FUN? That sent me back to our fundamentals, back to the main mechanic. Is our main mechanic fun, and is there any way we can embody that?

I realized our game didn’t take advantage of the grid we were using, and my teammate said we could make it more like a grid puzzle, which really evoked something in me. I made the grid bigger and gave cards more movement opportunities, even some chess-style ones that let birds move in interesting ways, because I want players to build their decks around these interesting movement cards. I also added more synergy between our cards, such as cards that give you stamina for moving and cards that move the whole flock! The flock is kind of our ecosystem: birds fly cheaper when they stay close, but losing one makes it way easier to lose the next.

The fun we ended up with is mostly challenge, the puzzle kind. Every flight is a little grid puzzle, and the best moments were when someone found the right move or the right time to use a formation. One player even got home with just one bird by hopping between updrafts, which I didn’t expect! Onboarding was tricky, and I feel we still have a lot to improve. For P4, I hope to keep playtesting, see how people interact with onboarding, and find out how we can improve it.

Something else I learned is the value of having a messy first product. In the realm of AI, it really always does more than you ask, and I really appreciated the first playtest, because I got to help brainstorm how our system would look rather than the whole thing. My biggest takeaway is to ask early if the game is actually fun, and to keep asking. Getting a messy first version in front of people taught me way more than building more ever did. AI will build almost anything I ask for, plus some stuff I didn’t, so deciding what the game is for is still on me. I’m excited to see where the BOAF goes next.

About the author

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.