Please excuse any awkward phrasing, as I am Korean and relying on a translator to write this.
The game looked remarkably well-crafted, so I played it all the way through from start to finish. It really is a great piece of work, and looking at the depth of its systems, there is a lot to learn from a game design perspective. It offered plenty to enjoy, and I walked away having learned a great deal myself. Personally, I consider it close to a "well-made" title overall—something you should genuinely take pride in. Every piece of the design feels thoughtfully put together without missing a beat.
My Breakdown of the Game Loop
To summarize how I understood the core loop: The protagonist and the heroine (seen only from the mouth down) are acquaintances, and the storyline unfolds in a cafe. The heroine asks the protagonist to playtest and give feedback on her game, which brilliantly uses narrative to motivate the player's actions.
As you play, the loop naturally progresses: "Hey, wouldn't it be fun if we added this system?" -> "Alright, let's add it and playtest it." -> After the test, lucky 7s pop up on the UI, leading to "What should we add next?" Repeating this process to make the number 7 appear on the UI screen completes the loop. It was awesome to see the classic game development process authentically reflected and adapted directly into the core gameplay loop.
Naturally, as options increase and more features get developed, the player gets an additional "task" per UI element, causing the difficulty to scale exponentially. In other words, it is structured to maintain a state of Flow where the difficulty rises alongside the player's growing skill over time. What is even more brilliant is that you let the player choose how to increase the difficulty. Normally, difficulty scales automatically to match player skill, so letting players customize their own difficulty curve is not just clever—it's genuinely thrilling. I suspect this was a bold, experimental area that you, KelvinHM, specifically wanted to test out.
Performing well in any given moment yields more 7s, which unlocks more systems to add next, sparking curiosity about what's coming, and delivering a satisfying difficulty spike. This escalation between core loops is theoretically elegant and seamless—a textbook example of great design.
Gameplay Flow & Player Reaction
Here is how my emotional and cognitive experience progressed step-by-step while playing. I'm sharing this chronologically in hopes that it proves helpful to you:
- Start: Story Cutscene Clicking through the dialogue, I immediately thought, "Aha, so I'm testing this game on her behalf. What happens next?"
- First Playtest: Just shooting with a basic character At first, it feels a bit dull because it's so easy. I thought, "I can beat this with my eyes closed," which clearly induces a state of Boredom—referencing Mihaly Csikszentmihalyi’s Flow graph. However, boredom is actually the best state for highlighting new mechanics because the player is actively looking around thinking, "I'm bored, is there anything new?" Right on cue, the number 7 pops up on screen, emphasized by the heroine's dialogue ("Oh, got a 7!"). At this exact moment, the player realizes, "Aha, making 7s appear on screen triggers something."
- Post-First Test: Dialogue & Upgrading Using the 7s earned as currency, the game hands you just one single option to upgrade the game, showing you how the game can evolve. You conveyed this smoothly through short English prompts without needing heavy exposition—honestly, this seamless transition is the part I envy the most as a designer. It made me eager to see how the game scene would change next.
- Second Playtest: Earning 7s through the newly added UI and systems There is a very smart "soft-gear" mechanism built in here: even if a player doesn't fully grasp that triggering 7s is the main goal yet, the difficulty still scales up very gently. Up until this point, I was playing casually, thinking, "Okay, I just need to make a 7 pop up once," assuming the next upgrade would also just cost a single 7.
- Post-Second Test: New variables in the upgrade phase Suddenly, there are multiple options! Seeing multiple choices at once made me think, "Wait, does that mean I can collect multiple 7s in a single run?" That made me reflect back on what triggered the 7 during the first test. Through this realization, I smoothly grasped the underlying mechanics and got completely hooked. The pacing of guiding the player without over-explaining is exemplary—it genuinely made me want to take notes as a fellow game designer.
Overall Rating: 4.5 / 5 Stars
To sum it up: This game is exceptionally well-made, and honestly, I believe it deserves to be ranked even higher than it currently is.
Three Design Concerns & Questions
After playing through the sequences multiple times, I noticed three potential pitfalls. Since you have crafted such a great game, I would love to hear your thoughts as a developer on these points:
1. Information Asymmetry in Player-Chosen Difficulty Letting players decide how many 7s to aim for and how to scale their power is fantastic, provided players can accurately gauge their own skill against what's coming. However, in this setup, players can only judge based on the previous round—they have no way of knowing how drastically a new feature will spike the difficulty because that information is hidden behind your curtain as the developer. For example, a player might think, "I'm pretty good at this, I can handle a bit more," and pick something like "Give the character a revolver instead of the other weapon." Then, once they actually try it, it turns out to be a terrible fit or way harder than expected—and there are no refunds.(Of course I played well, but we had to talk what if.) Being stuck with a bad build makes continuing feel worse than just resetting the whole run, risking a complete breakdown of Flow. What are your thoughts on this?
2. A Sense of Over-Controlled Restriction (Lack of Agency Outside the Frame) Depending on how the game gives feedback, players can start to feel overly restricted. Players naturally desire autonomy—they want to see how their choices impact and reshape the world around them. Because your concept uses a "game-within-a-game" framing device (developing a game inside a cafe with the heroine), the player is essentially just watching polygons, capsules, and cubes change inside a tiny box. Around the mid-game (past the 15-minute mark), players are likely to feel, "Wait, is this mini-game the only thing I can change? I can't affect anything else? Are these 4 choices really all I get?" This can lead to a strong sense of claustrophobia or frustration from being too tightly controlled. How do you view this dynamic?
3. Unclear Core Emotional Target I struggled to pinpoint the exact primary emotion you wanted players to feel while playing. Since playtesting is essentially an extension of "work," adding new features just to grind out more 7s can start to feel like a checklist of chores rather than an emotionally thrilling experience. I really admire game designer Tynan Sylvester, who emphasizes that evoking emotion requires shifting the state of something the player values. In this game, I didn't feel a strong shift in value or emotional stakes as new features were added. Was there a specific emotional arc you were aiming for?
I apologize for making you read such a long message! I simply wanted to ask for your insights because you've built such an impressive game.