fix: Don't persist namepool theme in state file
Theme is configuration (from settings/config.json), not runtime state. Loading theme from state file was causing rig config to be ignored, which is why the beads rig kept using mad-max names instead of minerals.
This commit is contained in:
@@ -156,13 +156,9 @@ func (p *NamePool) Load() error {
|
|||||||
return err
|
return err
|
||||||
}
|
}
|
||||||
|
|
||||||
// Load theme and custom names from disk (overrides constructor defaults)
|
// Note: Theme and CustomNames are NOT loaded from state file.
|
||||||
if loaded.Theme != "" {
|
// They are configuration (from settings/config.json), not runtime state.
|
||||||
p.Theme = loaded.Theme
|
// The state file only persists InUse, OverflowNext, and MaxSize.
|
||||||
}
|
|
||||||
if len(loaded.CustomNames) > 0 {
|
|
||||||
p.CustomNames = loaded.CustomNames
|
|
||||||
}
|
|
||||||
|
|
||||||
p.InUse = loaded.InUse
|
p.InUse = loaded.InUse
|
||||||
if p.InUse == nil {
|
if p.InUse == nil {
|
||||||
|
|||||||
Reference in New Issue
Block a user