ColorQuads devlog #7: 0.6.2, the symbols
ColorQuads 0.6.2: runes become the innermost layer of a quad, the Joker an undecided colour, and a turn that cancels a match now shows it.
Two weeks ago, 0.6.1 answered what players could not read about the sweep line. The second round of feedback confirmed that part: "seeing the cells being validated helps a lot, really more fluid". It also named what was left, in one sentence I have been designing against since:
"For block-game players it matters that things are predictable. You place a T, it does not turn into an S. The game has its grammar, but it is not explained, and the symbols in the middle of the quads have no affordance."
Two symbols, the rune and the Joker, were changing the board in ways nobody saw coming. 0.6.2 is about both, and it follows one rule: a mark is the layer it acts on, never a sign drawn over the quad.
Runes are a layer now
A rune used to be a glyph floating over the rings. It read as decoration, and nothing said whether it would help or hurt. Now the rune is the innermost layer: its silhouette, filled with that ring's colour. When the outer rings are gone, what is left is the rune itself.
Which side it is on is in its outline. A bonus rune is smooth. A penalty rune is serrated like the edge of a stamp, and when the sweep line reaches it, the teeth bite.
And when a rune is cleared, it says so: its name, then what it did, a beat after MATCH!. BURST! / clears neighbours. CURSE! / +1 quad. The cause, then the consequence, in the same voice as the match.
The Joker is an undecided colour
The Joker takes the colour of the largest group it lands against. Its old mark was a star, and a star next to runes reads as another rune. Now its outer ring is a slow drift of every colour in the level: every hue at once is no hue yet. When it lands, the ring settles on one colour, flashes, and says JOKER! in that colour.
The landing preview had a bug in exactly the wrong place: it showed the quad's own colour while the match was going to be made with another one. It now shows the colour the Joker will take. The preview is a promise, and it was half-kept.
A turn that cancels a match now shows it
One report was: "the line starts validating them, reaches the end, and nope." Turning the board while the line is over a group can carry that group behind the line, and the rule is that the line only takes what is ahead of it. The rule stays. What was wrong is that the light disappeared in one frame. Now it runs back along the group, and the group waits for the next pass.
Smaller things
Rings cast soft shadows from a fixed light, so a three-ring quad looks like a stack. And a quad never carries the same colour twice: stacked duplicates made some matches look like they did nothing.
Not in this one
Cycling backwards was asked for, and it is noted. Sound is still off, on purpose. And the last stage is still too comfortable to sit in; that is the next thing to calibrate, once these runes have been played by someone other than me.
The question for this build
The first time a rune was cleared in front of you, could you tell what it had just done to the board, without reading anything but the label?
Desktop builds write a session log; the itch page says where it lives. Send it to colorquads@proton.me if you are willing.