Constraint Manipulation Across a Season

Definition

A season-long constraint plan sequences task constraints across blocks so behaviors first emerge under simplified conditions, then stabilize, and finally generalize back into the full game.

Why it matters

Without sequencing, constraints become gimmicks. With sequencing, they become a development engine that compounds across months.

Examples

• Block 1 (Sep): paint-touch bonus. Block 2 (Oct): paint-touch + 0.5 timing. Block 3 (Nov): same constraints, full 5v5. Block 4 (Dec): remove constraint, audit behavior.

Practical application

• Map 3-4 behavioral targets across the season.
• Each block lasts 3-5 weeks — long enough for behavior to stabilize.
• Always include a 'remove the scaffolding' block to test transfer.

Common mistakes

• Adding new constraints every week — players never stabilize anything.
• Never removing the constraint, so behavior is dependent on the scoring rule.