Before the plugin enters the chat.
"Drop scalability for the demo" — and the project never quite returns.
Someone types a few CVars for a capture session. QA applies a different scalability combo for testing. Monday's authoring machine still runs last week's leftovers.
Performance state lives in chat logs and muscle memory instead of named assets. Restoring 'normal' becomes guesswork — and nobody agrees what normal was.
What that feels like
- Scalability and CVar tweaks scatter across people and sessions.
- Capture, QA, and authoring each invent their own console recipe.
- Rollback depends on remembering what changed — not on a stored preset.