P3: Reflection – Paprika

When we were deciding whether P3 would be analog or digital, I voted for digital. Part of that was because I thought I had a lot of experience with digital games (Actually I didn’t). The other part was that I think digital games are easier to share and preserve.

Actually building it turned out to be way harder than I expected. In P2, my interactive fiction only had to deal with text, background images, and some simple interactions. The simulation web game we aimed for in P3 gave us a completely blank canvas. There were no set layouts and no default interactions. Everything was open, which also meant everything had to be carefully designed and tuned.

It was really different from our analog game in P1 too. Players of web games just aren’t as patient as players reading a long rulebook. Since everything is digital, we didn’t have to squeeze lots of text into every corner. Instead, we had to manage where players were looking and keep their attention, so they’d never feel like leaving. That made it really important to keep the interface clean, fun, and immersive. The other big difference was control. In an analog game, players get the pieces and a simple board, and they have a lot of freedom in how they play: they can set their own pace and decide how they interact with each other. In a digital game, the designers have full control over all of that, which also means we have full responsibility for it.

The hardest part was the actual design. In meetings, we could usually agree on things like “this page is the Market, and here’s roughly how it works.” Once we ran out of things to discuss, I’d say, “Okay, I’ll go build what we talked about with AI.” But the truth was, we only knew what each page was supposed to do, not how to make it happen. We wanted players to feel rushed, like they had to compete for things, and we wanted the whole thing to be fun and tense. When it came time to build it though, I had no idea how long each timer should be, where things should go, what colors to use, or what the hint text should actually say word by word. I often went through countless rounds of iteration with AI just to get a version that worked, and even then it usually didn’t feel quite right.

What finally helped me get a feel for this kind of design was reading some related papers and looking at the layouts of similar games like PlateUp.

A screenshot of PlateUp!

One paper (Wu & Wolfe, 2016) said that players can’t pay attention to more than three things at once, and that really made me think. It made me even more set on keeping the UI super minimal and using lots of visuals instead of text. It also made me decide not to throw every mechanic at players on Day 1. Instead, we added one new mechanic each day, so players never had to learn too much at once, and the later days still felt fresh. The Service phase used to be mostly simple lines and lots of text. When we replaced it with a big, colorful restaurant view, with clear zones and guests, servers, and chefs moving around to show the rules and flow, my first thought was: yes, this is it! That’s when I realized that grinding through painful iterations until something finally feels right is one of the real joys of making games.

A screenshot of our Spoon Fight

But like I said at the start, I really underestimated how complex a seemingly simple system web game could be. With just two weeks, there are still a lot of parts that aren’t where I want them to be, whether it’s the UI, the mechanics, or the balance. I also know these aren’t things you can fix quickly. Every page of text and every interaction needs a lot of playtesting and tweaking to get better. I might not get to keep working on this project for now, but I’m really grateful for everything it taught me and how much it helped me grow.

Reference:

Wu, C.-C., & Wolfe, J. M. (2016). Multiple event monitoring. Cognitive Research: Principles and Implications, 1(1), Article 21. https://doi.org/10.1186/s41235-016-0022-7

About the author

Leave a Reply

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