Subject: Game Playtest Review & Design Feedback (Including Live Playtest Log)
Hi there! Since you gave me such a thoughtful and detailed feedback earlier, I wanted to return the favor by playing your game thoroughly and sharing an equally detailed review.
First off, I really like the tabletop board-game approach. For players to immediately recognize a project as a "game" and enjoy it, having that tactile board-game structure is great, and I can tell you put a lot of thought into building the core system. Choosing a number from the 5 cards at the bottom, assigning a direction to it, and issuing commands to reach a destination is a very solid puzzle foundation. I actually thought that if you expand on this simple puzzle adding more variables and scaling it up to a 5x5 grid—it could become deeply engaging and super fun. Pulling off this level of system design as a solo developer is truly impressive.
While the core mechanics are charming and definitely have that unique board-game appeal, I want to focus mostly on the areas that felt lacking during my playthrough. Below is a 100% honest, unfiltered log of my actual playtest experience. Please don’t take any of this the wrong way
I genuinely tried every method at my disposal to understand and beat the game!
My Live Playtest Log (Unfiltered First Impressions)
1. Right at the start of the game (Scanning the screen)
- As soon as the game starts, I see the board in the center. There are 9 tiles, directions like East, West, and North, and something blue in the middle.
- (Looking at the top-left corner) "What is 'Rite'? What kind of currency is 'Fortune'? Is 'Wax' my health/lives? What do these mean?"
- "'Four'? Why does the number 4 become 'unmarked'?"
2. During the tutorial
- "Whoa, okay, hold on, so much info... Alright, so 'Fortune' is my health. And I pick a number at the bottom, move along the gold-highlighted path, and get my piece to the destination. The goal is simpler than I thought."
- "Wait, why did 'rotating' move it over there? Oh, there’s a pivot in the center! (Note: I only figured this out because I’m a game developer myself—for a regular player, deducing the concept of a 'pivot' here would be nearly impossible.) So does it just rotate the entire board 180 degrees? Ugh, I have no idea. Gemini, help me!" (I actually took a screenshot and asked an AI assistant to explain it.) "Oh... so that's what it does. Aha!"
- "The audio is a bit quiet. Let me turn it up... Oh, there’s only a Mute button. That’s a slight bummer. Anyway, let's give this a shot! Hey, it's actually pretty doable!"
3. During actual gameplay
- "Moving around feels pretty decent. Seeing the piece actually move makes things clear. However, the concept of the board rotating still feels unfamiliar. Without those golden guide lines, I would have had a really hard time."
- "Huh? Why is 'Wind' blowing at the end of the turn? Where is the wind coming from? What? Where is it?! I don't see it... (Clicks the Guide button) Ugh, there’s a mountain of text... (Opens the Ledger) Oh, the wind really is blowing? Aw man, I just lost 2 lives so unfairly."
- "Oh, when I lose a life, one of the candles (Wax) goes out. So that is my life bar. Man, that feels so unfair... sigh. So where is the wind blowing from and in what direction on this round? And what is that number 4 and the orange diamond/square sitting on top of it?"
Overall Rating: 3 / 5
The system has great potential, but because way too much information was thrown at me all at once, I ended up needing an AI assistant sitting beside me just to get through it. (Though to be fair, being a non-native English speaker might have made that barrier feel even steeper.)
Detailed Breakdown
When we develop games, a very common trap is expecting a brand-new player to rely on external text or documentation outside of actual gameplay. Even if a game jam page asks you to write instructions on the submission page, if a player has to read that text during gameplay, it usually means the game's flow has already broken. On the flip side, reading a manual before playing without visual context rarely sticks, so players end up relying entirely on what the game shows them in real time.
Of course, in the age of the internet, players can look up walkthroughs, screenshots, or gameplay videos but we shouldn't design assuming our game will already have a massive community making guides for it. Stepping away to search for info breaks immersion, which is never ideal.
When you showcase a game in person, you quickly realize that players notice way more than you intended, yet miss the most obvious things. (A classic industry example is The Legend of Zelda: Ocarina of Time, where players got bombs right next to a cracked wall, yet still didn't think to blow up the wall.) That’s why tutorials and pacing information over time are so crucial. You did a great job building this solo, especially the system, but here are three specific areas where it fell a bit short:
1. Information Overload from Too Many Custom Terms
The tutorial introduces way too many unfamiliar terms all at once. If introduced one by one, they’d be easy to grasp, but throwing them all together makes the player’s brain feel like it’s trying to decipher an ancient Latin religious doctrine with a dictionary. Instead of using "Lives," you used "Fortune," threw "Rite" onto the board, and left "Wax" unexplained (I still wasn't sure what Wax meant...). Showing off too many cool mechanics too quickly just gives the player "cognitive indigestion." Rather than looking deep or stylish, it mostly just feels dizzying.
2. Unfair Failures Due to Missing Visual Cues (Especially the Wind)
Unlike action games, puzzle games rely heavily on intellectual learning and deduction. Players want to analyze a system, solve the problem, and feel smart when their plan works ("Whoa, I actually figured that out!"). However, when a player carefully meets all the visible conditions, hits "End Turn," and gets slapped with a "Failed" stamp because of an invisible mechanic, it feels deeply unfair—like getting arbitrarily rejected at the border in Papers, Please. The Wind mechanic is the biggest culprit here. I still haven't figured out how to tell which direction the wind is blowing on a given stage, meaning I’m guaranteed to keep failing unfairly. I actually ended up resetting the stage because of this.
3. Lack of a Clear "Why" (Motivation to Solve the Puzzle)
Right now, the game hits the player with a wall of rules before giving them a clear reason why they should care about solving this puzzle. Hardcore puzzle fans will happily run toward a goal just for the sake of solving it, but most players will quickly hit Alt+F4 if they don't feel a strong hook or purpose early on. Furthermore, relying purely on puzzle mechanics to carry the game inside a 3x3 grid puts immense pressure on level design which is honestly one of the hardest, most exhausting disciplines in game design (the kind major studios hire dedicated specialists to pour their lives into). I worry that trying to carry a 3x3 puzzle purely through complex mechanics might burn you out, so giving players a clearer narrative or thematic hook right on the first screen would help tremendously.