Every config saved before 0.1.3 holds the old default (or preset) Background and Primary colors fully opaque, because the config saves every property. Since #8, panels use those colors' own alpha, so glass and translucency wouldn't show for anyone updating until they applied a preset again.
On a config saved by an older version, recognized by it having no Menu blur (new in 0.1.3), Background and Primary colors that are exactly an old default or preset, fully opaque, get the preset's translucent alpha. Colors players picked themselves are left alone.
It only runs on those older configs, so a preset color set to 100% opacity on purpose later stays opaque.
ConfigManager.isSaved(name) tells whether the config file has a value, sharing the lookup with loading a property.
To test: in run/saturn.json, remove Menu blur and set UI Style › Background to "#FF12100D" (the old default). On launch, panels are translucent again. With Menu blur left in, the opaque color stays.
Every config saved before 0.1.3 holds the old default (or preset) Background and Primary colors fully opaque, because the config saves every property. Since #8, panels use those colors' own alpha, so glass and translucency wouldn't show for anyone updating until they applied a preset again.
- On a config saved by an older version, recognized by it having no `Menu blur` (new in 0.1.3), Background and Primary colors that are exactly an old default or preset, fully opaque, get the preset's translucent alpha. Colors players picked themselves are left alone.
- It only runs on those older configs, so a preset color set to 100% opacity on purpose later stays opaque.
- `ConfigManager.isSaved(name)` tells whether the config file has a value, sharing the lookup with loading a property.
To test: in `run/saturn.json`, remove `Menu blur` and set `UI Style` › `Background` to `"#FF12100D"` (the old default). On launch, panels are translucent again. With `Menu blur` left in, the opaque color stays.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Configs saved before 0.1.3 hold the old default and preset background
and primary colors fully opaque, so glass didn't show for anyone
updating. On a config without Menu blur (new in 0.1.3), colors that are
an old default or preset get their translucent alpha; colors players
picked stay as they are.
Co-Authored-By: Claude Opus 5.5 <[email protected]>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Every config saved before 0.1.3 holds the old default (or preset) Background and Primary colors fully opaque, because the config saves every property. Since #8, panels use those colors' own alpha, so glass and translucency wouldn't show for anyone updating until they applied a preset again.
Menu blur(new in 0.1.3), Background and Primary colors that are exactly an old default or preset, fully opaque, get the preset's translucent alpha. Colors players picked themselves are left alone.ConfigManager.isSaved(name)tells whether the config file has a value, sharing the lookup with loading a property.To test: in
run/saturn.json, removeMenu blurand setUI Style›Backgroundto"#FF12100D"(the old default). On launch, panels are translucent again. WithMenu blurleft in, the opaque color stays.🤖 Generated with Claude Code