Skip to content
This repository was archived by the owner on Aug 8, 2026. It is now read-only.

︎︎⠀ - #106

Merged
tickwarden merged 1 commit into
mainfrom
devlop
Aug 7, 2026
Merged

︎︎⠀#106
tickwarden merged 1 commit into
mainfrom
devlop

Conversation

@tickwarden

Copy link
Copy Markdown
Collaborator

No description provided.

Force reload now routes through the existing dl_load:gate/* confirmation
system (same pattern as ban/kick/disable) instead of running
unconditionally — it discards live engine state, so it belongs in the
dangerous-action class the gate system already protects.

- dl_load:load/force: checks datalib:engine {sandbox:1b} and defers to
  gate/request when active; runs directly when gates are disabled
- add datalib:core/internal/load/force_apply — the actual re-init logic,
  extracted so gate/run_action can call it post-confirmation
- main.mcfunction: update stale "no confirmation gate" header comment
  and reload-warning message to reflect the gated force path
- initial load (main -> load/all) stays ungated on purpose, to avoid
  stalling server startup on a confirmation prompt

Removed dead code: datalib:config/load_cfg.mcfunction defined
load.timeout_seconds / load.sandbox_enabled scores and referenced a
dl_load:load/confirm function that never existed. Nothing called it and
nothing read the scores it set — an abandoned earlier attempt at a load
gate, superseded by the dl_load:gate/* system above.
@tickwarden
tickwarden merged commit 03a1639 into main Aug 7, 2026
2 checks passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant