Checked . Play the build at /play/crow-cap/. No public store rating is printed for this browser games build, and I will not invent one.
Crow Cap — session frame from the hosted browser build
I opened Crow Cap expecting another stacker from the tower-rush shelf. Instead the hard hat sat behind a turret that already tracked the pointer, and the first crows drifted in slow enough that a single Space tap explained the whole browser games contract: aim, fire, watch feathers.
The scaffold and skyline do more than decorate. They tell me the fantasy without a splash speech. On a Leikanger morning that matters — I want the skerry diary to start with what the build shows, not what a marketing paragraph claims.
Mute and pause were reachable before the first death. The Close control we pin on this domain sat clear of the HUD after a small left pad. That is the kind of housekeeping I now write into every browser games check so a later pass can reuse the same notes.
By noon I was letting swarms close for CLOSE! bonuses. Empty bolts reset the combo, so holding fire into empty sky is vanity dressed as aggression. Night Shift doubled the score window; Gust nudged the aim just enough to punish lazy tracking.
Golden crows zigzag high and ask for a deliberate miss risk. I missed two before landing one, and the diary line writes itself: the build rewards composure more than spray. There is still no public star average or install counter for Crow Cap, so those fields stay blank on the ranking card.
Compared with the other three browser games on today’s shortlist, Crow Cap teaches failure fastest. A peck ends a life; three pecks end the run. The learning curve is steep without being obscure, which is why the midday stamp stayed generous.
The thick drone with six hits forced me to clear space first. Nuts fell while I was still finishing the swarm edge. That is the afternoon test for these browser games: does an event change the verb or only the scenery? Here the verb stays aim-and-fire, but priority management appears.
I checked missions and skins after a bot pass. They unlock from tangible goals — crows, combos, near-misses — not from a store IAP wall. That fits the skerry rule: facts come from the build under /play/, never from an invented listing.
Portrait on a phone stayed readable. The turret tracking with a thumb is slightly coarser than with a mouse, yet the first thirty seconds still communicate the fantasy. That portability is part of why Crow Cap leads the browser games ranking tonight.
I put Crow Cap first among these browser games because the teaching loop is merciless and fair. Short arcade bursts fit an evening better than a long haul under ice. Tomorrow I might chase golden crows for a cleaner combo graph; tonight the stamp stays 3 November 2026.
If a later pass finds a store card, I will add rating and size then. Until that day the diary refuses to fill the gap with a plausible number. The play link remains /play/crow-cap/ on this domain, and the review link on the ranking card points here.
After four builds, Crow Cap is still the one I would hand a visitor first. The turret fantasy is readable from the doorway of the room. Failures are loud, recoveries are immediate, and the near-miss economy gives skilled hands something to chase after the novelty fades.
I re-opened the ranking card and re-read the facts line aloud: mechanic, controls, no public store rating, checked date. That sentence is the whole editorial contract of this skerry. Anything beyond it would be decoration pretending to be evidence.
For readers who only want the play button: it is one click from the home ranking and again from this diary. For readers who want the method: the timeline on the home page explains how the shortlist was timed on 3 November 2026. Both paths matter; neither replaces the other.
I will revisit Crow Cap when a build note changes or when a store card finally appears. Until then this page stays the record of one roof, one turret, and one honest blank where a star average would usually sit among other browser games write-ups.
