It comes round. Type it once.

Six. Daily, weekly on the days of the week you tick, every N weeks on the days you tick (from 2 to 52 weeks), monthly on the same date, monthly on the same weekday, and yearly. The day-of-week checkboxes only appear for the weekly and every-N-weeks patterns; the monthly and yearly patterns take their day from the event's own start date, so a monthly event that starts on the second Tuesday keeps landing on the second Tuesday.

Not from inside the series, and it is worth knowing exactly where the line falls. A recurring event is one record: the name, the start time, the length, the description and the ticket types belong to the whole loop, so editing the start time moves every date. What is genuinely per date is the part that has to be: ticket inventory, registration capacity, check-in, each date's own page, and the list of people who asked to hear about that date. If one date is really a different event, take it out with an Exclude Date and add it back as its own event.

Yes. Exclude Dates take a date out of the pattern, and Include Dates add a date the pattern would not have produced. Exclude wins if a date is in both lists, and an included date is kept even when it falls outside the pattern or past the end condition, so a one-off extra session does not need the loop rebuilt around it.

Nothing. The date is simply not on the calendar. There is no struck-through row and no cancellation notice, so an excluded date reads as "we are not on that week" rather than as something having gone wrong.

No, and that is worth saying plainly. A recurring event carries one start time and one length, so it produces at most one date per day it falls on. A matinee and an evening, or a morning class and a lunchtime class, are two events with two patterns. It is slightly more setup, and it keeps the two start times and their tickets properly apart.

Two-way sync with Google Calendar, Outlook and Microsoft 365, or any CalDAV server is free on every plan, and it carries the event record itself across. What it does not do is hand the connected calendar a repeat rule, so do not expect the series to appear there as a repeating entry. The place a loop is expanded date by date is your schedule's iCal feed: it writes one entry per date for the next 90 days, each linking to that date's own page. Every event page also offers a download for the single date somebody is looking at, sharing its identifier with the feed so a calendar app updates the entry it already has.

Yes, through your schedule's calendar feed, which carries every date of the loop for the next 90 days alongside everything else you publish. Your schedule and event pages offer it as "Subscribe to all events from" followed by your schedule's name, and it costs a guest no email address. Their calendar app keeps checking the feed, so when you change the time or take a date out, their calendar follows at its next refresh. The one-date download is different: it is a snapshot of the moment they took it.

Yes. On that date's page a guest can leave an email address, with no account and no name, under "Tell me when tickets go on sale", or "Tell me if anything changes" once the date is already selling. They hear about that date and no other: one email when its tickets go on sale, if they were not on sale already, and a reminder shortly before it starts. If you save a venue change or cancel the event and choose to notify people, that reaches them too. Every email carries a one-click unsubscribe, and it is free on every plan.

Yes, on the Pro plan. A season pass can be set to cover every date of the loop, once per date, and it is sold alongside single-date tickets rather than instead of them. Advance booking is off by default, which means the pass is scan-at-the-door until you switch it on; switching it on is also what lets you cap how many seats pass holders may reserve on a given date.