Solver rules and weights
The Rules step tunes what the constraint solver may do (hard rules) and what it optimizes for (soft rules and objective weights).
Hard vs soft
- Hard rules are never broken: field overlaps, team clashes, rest minimums, painted-availability bounds, dependency order. A schedule that would violate one is rejected outright.
- Soft rules express preferences - balanced loads, preferred fields, compact days. Their weights trade them off against each other.
Weights and defaults
The page ships sensible defaults; guidance text on the page explains each rule. Turn a rule off to remove it entirely, or adjust a weight to change how strongly it pulls the solution.
Presets
A one-line legend above the rules explains the Hard / Soft / Off modes, and each weight slider shows its 0-10 scale; higher weights matter more relative to the other objectives.
Three preset chips apply a coherent bundle of modes and weights at once - the chip matching your current settings is highlighted, and any deviation shows a Custom badge:
- Relaxed turns every enabled preference into a soft rule at weight 1 - rules that are off stay off, and hard-only rules such as team availability are untouched.
- Balanced restores the shipped defaults.
- Strict makes every soft-capable rule a hard constraint.
Numeric caps (games per day, referee matches per day, field-change gap) are values, not modes, so they carry over. Change any control afterwards and the badge flips to Custom - the underlying options are still stored per rule.
Coach groups - teams sharing a coach - get their own setting for whether their matches may overlap, from a hard block to free overlap.
When to change them
Loosen rules when generation is infeasible (the review page's diagnostics name the blocking rule), tighten them when a published quality bar matters more than solve time. Rule changes apply to the next solve - they never mutate an existing version.