Skip to content

fix(autostore): preserve default and explicit per-item modes - #633

Merged
Siroshun09 merged 4 commits into
mainfrom
codex/v6-autostore-defaults
Oct 4, 2026
Merged

Siroshun09 merged 4 commits into
mainfrom
codex/v6-autostore-defaults

Conversation

@Siroshun09

@Siroshun09 Siroshun09 commented Oct 4, 2026 •

Copy link
Copy Markdown
Member

New players now retain the default all-item mode when their saved settings are empty. Persist an explicit all-mode flag so disabling all-item mode with no selected items survives saving, reloading, and export.

Addresses F07. Regression tests cover new-player defaults, empty per-item settings, export, and selected-item reloads.

Legacy empty-data decision: CustomDataManager.loadData returns an empty node for both missing data and a persisted empty node. Earlier serializers used that same representation for disabled per-item mode with no selected items. YAML and SQLite delete empty custom data when saving, so checking persisted keys cannot recover the original mode either. Empty data intentionally uses the new disabled/all-item defaults. It stays disabled, but enabling it later affects all items. This PR records the decision; to retain disabled per-item mode, run /box autostore item all off followed by /box autostore off. A regression test covers a persisted legacy empty node; new saves persist all-mode explicitly.

Validation: the Java 25 Gradle build and tests passed in GitHub Actions. README has no changes relative to the base branch.

@Siroshun09
Siroshun09 merged commit b04f119 into main Oct 4, 2026
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant