Match Night Scheduler — the season, on the calendar

The season is generated by counting days, not milliseconds. Starting from the first night you pick, each candidate date is built fresh from the year, the month and the day-of-month plus k × the cadence — 7 for every week, 14 for every other week — and then the start time is attached as a plain wall-clock time. Doing it that way hands month ends, leap days and daylight-saving changes to the calendar, which is what a calendar is for; adding 604,800,000 milliseconds to a timestamp is how a Tuesday night quietly becomes a Monday in late October.

Skipped dates are removed and then made up. A skipped night does not shorten the season: the generator keeps walking the cadence until it has the number of nights you asked for, so skipping two dates in a ten-night season pushes the last night two slots later rather than leaving you with eight. The walk stops after 400 candidate dates, which is the guard against a skip list that could never be satisfied.

The calendar file is written in your browser, as iCalendar text to RFC 5545. Each night is its own 90-minute VEVENT in local wall-clock time with no time zone attached, so a clock change moves nothing. Content lines are folded at 75 octets with a leading space on the continuation, and never in the middle of a multi-byte character. Each event's UID comes from an FNV-1a hash of the whole schedule — weekday, time, cadence, length, first date and skip list — so importing the same season twice updates the events you already have instead of doubling them, while a season with any detail changed gets its own set of ids.

Ninety minutes is our default event length, not a rule; it is the booking length most clubs sell. There is no account, and the file is built and downloaded by the browser itself.