Sort the Court!

Sort the Court's reputation precedes it: a Ludum Dare 34 entry expanded into a full release, a name-your-price itch.io page with almost 11,000 ratings averaging 4.7 stars, and comment after comment calling it "absolutely adorable." Played directly on a desktop browser, none of that reads as inflated. You rule a small kingdom from a hand-drawn throne, and a rotating cast of petitioners bring you decrees — a princess at the gate, a merchant with a proposal, a wizard with a warning — each one a yes-or-no call that nudges population, happiness, and gold in different directions. It's quick, funny, and often sharper than it needs to be for a joke game about running a kingdom. None of that is in question.

The gate this shelf exists to enforce, and a plain failure of it

What is in question is whether it belongs here, and the answer, confirmed rather than assumed, is no. This shelf's second gate is that a game has to actually work with a thumb, tested rather than inferred, because that is specifically the thing Flash-era games couldn't do and this section exists to fix. Sort the Court's standalone build — a classic, pre-WebAssembly Unity WebGL export — does not clear it. A tap on "New Game" on a simulated touch phone did nothing. A genuine 150-millisecond touch-and-hold through the browser's real touch input pipeline, the same mechanism a real finger uses, also did nothing, on the identical button that a desktop mouse click reached instantly. This isn't a matter of the button being small or mispositioned — nothing in the entire interface responds to touch input at all, on any control tested.

The developer isn't hiding this. The game's own itch.io page tells mobile visitors directly to go elsewhere: "To play on mobile devices, or in other languages, check out the updated version exclusive to Poki." That's a plain admission that this specific build was never built or intended for a touchscreen, and that the version which was is under an exclusive arrangement with a different platform this shelf has no licence to touch, copy, or link around. There's no proportionate fix available here the way there was for other candidates this cycle — this isn't a missing relative path or an easy toggle, it's a different, separately-built, separately- licensed piece of software that happens to share a name.

What else needed handling before this could even be fairly judged

Two more things surfaced during installation, worth recording even though they don't change the outcome. The build makes an outbound call on every load to stats.unity3d.com/HWStats.cgi — Unity's own anonymous hardware-telemetry ping, baked into the compiled engine rather than anything the developer wrote — and a second call to a GameJolt leaderboard endpoint carrying this game's specific GameJolt ID. Neither string appears anywhere findable in the roughly 27MB of compiled game code in a form that could be safely edited out without risking the whole build, so both are blocked at the browser level with an added Content-Security-Policy header restricting outbound connections to this game's own origin. That's a clean fix and it works — confirmed by testing, both calls are refused rather than silently sent — but it's a meaningfully different kind of intervention than editing an HTML attribute, and worth naming as what it is.

Separately, no licence exists anywhere for this game's actual files. There's a sticky community post on the game's itch.io page about "monetisation permission," but reading it shows it covers video and streaming content specifically, not redistribution of the game itself — a different grant entirely. Had this game cleared gate 2, it would still have needed the same unlicensed-work treatment given to other candidates this cycle: hosted with the author credited, linked to their own release, and offered a same-day takedown, not represented as openly licensed.

Where that leaves it

None of this is a judgment on Sort the Court as a game — by every available measure, including direct play, it's a well-loved, well-made, and completely charming way to spend a few minutes. It's a judgment on this specific build's fitness for a shelf built entirely around phone playability, and on that single, decisive point, it doesn't clear the bar. A 4.5 reflects strong scores everywhere except the one category this section can't compromise on: a game that flatly does not work with the input method most of this shelf's audience will actually try first.