Jet Lag: The Game · Hide+Seek

Is your city a good map?

Give it a GTFS feed — the schedule file almost every transit agency publishes — and it works out how many distinct places there are to hide, which of the deck's questions actually split the map, which curses are unplayable here, and what all of that adds up to out of 100. Everything runs in this browser: the feed is never uploaded anywhere.

Fetching a URL only works if the agency's server sends CORS headers, and plenty of them do not. When that happens the browser refuses the request before this page ever sees it, and there is nothing either of us can do about it from here — download the zip yourself and drop it in above. Same answer, one extra step.

Looking for a feed? Try the Mobility Database or Transitland.

Every field here is an override. Most of them are inferred from the feed if you leave them alone; departure time, board slack and border shape are fixed defaults instead — the same ones the command-line tool uses. Change one and you are telling the generator you know better than the feed, which is sometimes true.

Small

Medium

Large

A stop_id from the feed. Overrides the inferred round-start station.

Rectangle

Circle

Out-of-play stations. Comma-separated stop_ids.

Routes your group agreed are off limits. Comma-separated route_ids.

Where the prebuilt map files are served from — the directory holding manifest.json. Blank uses the published one. Point it at a local static server to try a build before it ships; it has to answer HTTP range requests and expose content-range to CORS, or the files read as corrupt.

Skip OpenStreetMap (much faster) Reading the map files is the slow part of a run, by a wide margin. Skipping them keeps everything the feed alone can answer and excludes every question, curse and sub-score that needs map features — excluded, not guessed at, so the score says so out loud.

Ignore the cached transit feed The transit feed is cached in this browser and reused, which is what makes a second run of the same feed quick to start. Turn this on to download it again — worth doing when the operator has published a new one. It does not affect the map files: those are immutable, addressed by content, and always read from the network.

Use only the cached transit feed The mirror image of the switch above: a cache miss becomes an error instead of a download, so the feed either reproduces exactly what an earlier run saw or stops and says so. This does not make the run offline — the map files are still read over the network unless OpenStreetMap is skipped as well.

Analyse

Most of a run is spent reading the map files; skipping them above is much faster.

The verdict

Every point, traced

Where the points came from

Before you play

What this means for your game

House rules

What works, what fights you

Key numbers

The map at a glance

Every figure is measured on this feed, on the representative day for the service type selected above. Tiles with a gold rule and a “changes by day” chip move when you change the day; the rest are map-wide or come straight from the rulebook.

The network

The map you’re playing on

How long things take

Getting around

The deck

The questions

The curse deck

Every curse in the hider's deck, checked against this map's geography and this feed's network. A count is the number of qualifying features inside the border — outside does not count, because outside does not exist for this game.

Provenance

Where these numbers come from

Every number above, traced to the query that produced it.