The first minute was confusing and I couldn't see a clear game loop.
- The Gnome (I don't recall he said his name) told me to run the benchmark but I had to actually place a core first.
- I didn't know why the benchmark failed?
- What is even a benchmark? I am a programmer (not a chip maker) and I still can't tell what is it or why should I care. It is meaningless at this stage for me.
- The components look boring, color and "HS" is not enough. I think you could do better to make them more engaging and representative of their job.
- How does CPU, RAM, Telemetry fit together? Why should I care? They are just numbers at the bottom of screen. Obviously they need to be more visible and maybe given icons and animated particles. This is the core of the game. Even if the UI says to use a statusbar, there are other UI options that are more prominent (e.g. top bar in the win xp explorer)
- 1- Gnome told me to run benchmark 2- benchmark failed for no reason 3- Gnome: "it was a mistake hiring you after all" 4- should I leave now? I think this sums up the root problem with this demo. The loop and connections might be clear in your head, but I can't understand or care about them (even though I am familiar with these terms, I can't understand how the game connects them).
- Clicked Gnome icon (after he left) to get help with above, he said "Connectors carry heat better than ALUs or cache". What are connectors? ALU? cache? why should I care about heat? what is the actual goal of all this? I got a random tooltip instead of the help I need at the moment.
- What is TDB?
- So much wasted potential with the Gnome.
- He could wear cloths that fit the game better,
- he can move around and point at the exact point I need to interact with,
- his hat can get heat vfx to teach me about heating...etc.
- He could also have a "we are in this together we are both learning" instead of sounding bossy or having assumptions.
- MS Office Clippit was doing random moves from time to time (flips, scratches head, looks at something, ..etc)
- The game is literally flat UI but it doesn't have to be flat experience, Gnome can be much more engaging to fill this gap.
- The grid is ambiguous. It is divided into small squares but you can't place on them, it snaps to 2x2 slots (instead of 1x1 shown). At least make 1x1 squares faded and the 2x2 bold.
A better FTU flow could be for example:
- Gnome: hello I am [name] and we are here to test silicon chips.
- We get paid when our chips pass benchmarks (highlights benchmarks)
- There are lots of details that go into this, but let's focus on Components for now (jumps next to components)
- Cores are, well, the "core" of the chip. Place one on the grid.
- Let's run the benchmark (teleports and points arm toward the button)
- (Benchmark fails.) (log shows actual reason)
- Dang! it failed. You can see the reason (here). It says the Temp was off the charts, literally, you can see it on this graph (points to it, glowing red from heat)
- Seems we need a heatsink to suck up all this heat so we can get paid.
- (Adds HS, preferably shaped like an actual HS not a primitive cube)
- Let's run again.
- (Benchmark success)
- Ah much better! Temp is within metrics (points at metrics).
- We got valuable test data from all this, it is called Telemetry. Let's spend it on Research (points to tab) and improve our next iteration.
Easy W's 👍
P.S I love what you guys are doing and want your game to succeed <3

























