Glitchcon

Galcon's pitch has been cloned dozens of times because it's a genuinely good fit for a small file size and a touchscreen: drag from a planet you own to one you don't, and a fleet launches automatically to fight over it, all happening continuously in real time against an AI. Glitchcon is a 2016 js13k entry built on exactly that idea, with a glitch-themed aesthetic layered over it, and reading the source rather than guessing confirms the mechanical part actually works. What it doesn't do is tell anyone that.

The drag mechanic works, confirmed directly

Rather than trust the premise, this review tested it: a held drag from a controlled planet (rendered green, with a troop count) to any other planet on the map, run through a real touch-emulated drag on a simulated phone screen. It worked exactly as a Galcon clone should — the source planet's number dropped, and new arrow-shaped ship sprites appeared in transit toward the target, all with zero console or page errors across every test run on both the phone and desktop profiles. Reading glitchcon_minified.html confirms why it holds up on touch: touchstart, touchmove and touchend run through the identical function as mousedown, mousemove and mouseup, with no separate mobile code path and no user-agent gate disabling either one. The canvas itself is genuinely responsive too — the full map fits a 390-pixel phone screen with no horizontal overflow and no forced pinch-zoom, which is more than several other candidates in this review batch can claim.

Nobody told the judges either, and nobody tells you

Here is the actual problem, and it isn't a guess: a search of the full page source for any player-facing instruction, help text, tutorial or how-to-play string comes back with nothing. Not a tooltip, not a first-launch overlay, not so much as a caption. That would be a minor gap in a game with an obvious, familiar interface, but Galcon's whole control scheme is a drag gesture that isn't visually hinted at anywhere on screen, and the historical record shows real people hitting exactly that wall. A 2016 js13kgames.com judge's comment, still visible on the competition's own results page, describes it plainly: "I wish there was some instructions so that I knew exactly what I was doing. I found that I needed to click on the biggest circle and the number would increase. Other than that, nothing seemed to work, sadly." That is close to word-for-word what this review would have concluded too, had the source code not been read first to confirm the drag gesture was the actual answer. Ten years on, nothing about that has changed.

Two smaller gaps compound it. No win condition, score, or end-of-game state of any kind turned up in a search of the source — a session is an open-ended skirmish with no marker for what winning even looks like. And the competition's own numbers are honest about where this landed at the time: 43rd of 60 entries in the 2016 Overall category, with judge reactions on record that split between "very cool" and "very inventive" on one side and the confused, instruction-less experience quoted above on the other.

The verdict

The mechanical core here is real, and it deserves credit: a live, continuously-simulated RTS with working AI opponents and functioning touch controls, built to fit inside 13 kilobytes, is a genuine achievement, and this review confirmed the touch layer works rather than assuming it. But a control scheme nobody explains is a control scheme most players will never find, and that isn't a hypothetical risk here — it's a documented outcome, reported by a professional reviewer the first time this game was ever shown to anyone. Worth five minutes for the curious who read this review first; not something to hand a friend with no context.