Add every eligible full-match score inside the configured day, week or month, then divide by the number of eligible matches. More activity stabilises the average; it does not farm points.

A single match score is floored at zero after all positive and negative events are combined.

Only finished matches matching the configured GibHub channel and team size are eligible. Each imported performance remains linked to its match and stable GibHub player UUID.

While registration remains open, squad corrections are free and prepare matchweek 1. They consume neither transfer allowance nor transfer points.

An existing team can edit only the earliest future matchweek whose roster deadline has not passed. The current scoring lineup stays locked.

Transfers are the final player OUT → IN difference from that target matchweek's locked baseline. Re-saving replaces the plan; returning to the baseline restores zero transfers and zero penalty.

Changing captain, vice-captain, starter or backup position is a squad edit but not a player transfer. Weekly and season limits for squad edits and transfers are enforced separately.

The outgoing player remains in every earlier roster snapshot and keeps all points already earned there. The incoming player starts only in the target matchweek; recalculation always uses the roster saved for each matchweek.

The free allowance is applied first. Every additional transfer costs the configured points in the target matchweek. Dropping the worst finalized performance can never remove a transfer penalty.

NEXT_OPEN_MATCHWEEK starts with the next editable matchweek. CURRENT_MATCHWEEK starts at the exact save time, so matches that began earlier in the same matchweek are never added retroactively.

Locked, finished and archived seasons can be inspected but not edited. Their matchweek squads, captaincy, substitutions, points and ranking remain auditable.

BUDGET immediately increases the team's available squad budget for later saves in that season.

POINTS is credited to the matchweek that owns the spin and appears in that matchweek and the season total.

TRANSFER increases both the free allowance and weekly transfer limit for the nearest future editable matchweek. It does not increase the season transfer cap.

A transfer won during registration never applies to the free matchweek 1 build. It targets the nearest future editable matchweek — normally matchweek 2.

If no future editable matchweek exists, a transfer prize is removed from the draw and the remaining positive weights are used.

NONE records a valid spin without changing budget, points or transfers. A locked season accepts no more spins.

For matches dated 26 August 2026 onward, the worker stores only the Live summary and current score. Opening the row shows an on-demand projection; it is never added to prices, matchweeks or rankings.

Only GibHub state finished unlocks the complete player totals. The same match UUID replaces its Live summary transactionally, so retries cannot create duplicates.

After a successful import, eligible active-season performances and rankings are recalculated automatically.

An authorised admin may exclude a complete match from fantasy scoring or restore automatic rules, and may INCLUDE or EXCLUDE an individual imported player row after final import. Every action requires a public reason. Raw GibHub results and statistics are never rewritten; the full author, time and superseded history stay visible, affected season scores are rebuilt, and a terminal season republishes its Hall of Fame atomically.

Prices never change silently. Admin runs Calculate Preview, reviews every player, then explicitly publishes a versioned market snapshot. A season pins one published snapshot, so every manager builds and transfers against the same season market.

Admin can run a normal incremental sync or a full repair scan. Every administrative change is written to the audit log.

Admin can run deterministic random season simulations in memory to test transfers, captaincy, backups, penalties and drop-worst invariants. A simulation never writes production season data.

One to twelve days, weeks or calendar months per matchweek. A player's matchweek score is always the arithmetic average of all eligible full matches inside that window.

Close entry when the season starts, or keep it open until an optional date. Late entrants can start in the next open matchweek or from their exact save time inside the current matchweek; earlier matches are excluded.

Exactly six starters, zero to four configurable automatic backups, a shared budget, captain multiplier and independent transfer and roster-edit limits.

One public competition can run alongside administrator-created private invite-only seasons. Password leagues remain disabled.

Admin may discard zero to fifteen lowest finalized lineup-plus-points-bonus results before transfer penalties, while always retaining at least one matchweek. Individual matchweek points stay visible and every transfer penalty remains charged.

Matchweek structure, roster, budget, visibility and drop-worst are Draft-only. Transfer allowances, cost and squad-edit limits freeze at kickoff. Other permitted changes can take effect only from a future unlocked matchweek.

The bonus wheel, prize mix, spins per matchweek and each lifecycle notification can be enabled or disabled independently.

At least 8 completed gathers in the last 30 days and last played within 7 days.

At least 3 completed gathers in the last 30 days and last played within 14 days.

A recent but small sample is marked Low activity. No completed gather in the last 30 days is Inactive.

An administrator creates the season and a time-limited invite. A signed-in FantasyPlayer claims it once and then sees its season, squad and rankings.

Season start, matchweek start, roster lock, matchweek end, ranking-ready and private-invite events appear in the notification centre and can also be delivered through the Discord bot.

The header shows when GibHub data was last successfully synchronized. Admin Health exposes queues, unmatched records and import failures.