Under the hood
Skill overrides use a safer storage format, and settings now warn when a skill's name can't be stored
What
The local skillOverrides setting, which lets you hide or collapse a skill from settings without editing its file, is now built using a storage object with no inherited prototype instead of a plain JavaScript object. This avoids clashes with built-in object properties.
- The settings dialog used for managing skills now checks which skill names would collide with properties that Settings storage can't hold.
- When a skill's name can't be stored or toggled for this reason, a new message now surfaces explaining that Settings can't store an entry with that name.
Why
This prevents a skill whose name happens to match a reserved property name from silently failing to save its override, and tells you clearly when that happens instead of failing silently.
Names in the bundleskillOverrides