Skip to content

Rewild block by block: fresh terrain, with every placed block kept (0.3.0) - #4

Merged
mgilardi merged 2 commits into
mainfrom
rewild-redesign
Nov 12, 2026
Merged

mgilardi merged 2 commits into
mainfrom
rewild-redesign

Conversation

@mgilardi

Copy link
Copy Markdown
Contributor

The redesign the owner approved on 2026-11-12: everything rewilds except what's kept.

  • A mined-out, abandoned chunk is rebuilt from a fresh copy of the seed, block by block. Every player-placed block, filled container, dirt path (keep-blocks), kept area, and the block holding each up stays exactly as it was.
  • Player builds no longer keep a whole chunk. Claims, spawn, respawn points, named pets, nearby players, strongholds and /rewild protect still do.
  • /rewild plugins: nothing resets until every installed plugin has an answer; a respected plugin that isn't running stops resets.
  • /rewild keep / unkeep (with plugin:<Name>), --json on keep list and plugins; KeepProvider.areas().
  • Rewild's own tracking now records every placed block, so CoreProtect isn't used. Chunks tracked by 0.2.x stay unknown.
  • /wr and wildernessregen.admin removed, as announced for the release after 0.2.x.

Tested: 82 unit tests. Bot acceptance on throwaway Paper 26.3 build 249 and 26.2: 113 checks each. Provider test on 26.3: 9 checks. The first 26.3 run caught two save-format bugs in the merge (plain states read as one; a palette list mixing shapes); both fixed with unit tests, and the NBT writer now refuses a mixed list.

Not tested: a real game client; 26.1.2; scale on a long-played world; real plugins other than the stand-in reporting areas.

🤖 Generated with Claude Code

mgilardi and others added 2 commits November 12, 2026 11:51
The owner's redesign (approved 2026-11-12): everything rewilds except
what's kept. A chunk that's mined out and abandoned is rebuilt from a
fresh copy of the seed, block by block, and every player-placed block,
filled container, dirt path, keep-blocks type and kept area stays in
place with the block holding it up. Player builds no longer keep a whole
chunk; claims, spawn, respawn points, pets and nearby players still do.

Nothing resets until an admin has answered for every installed plugin
with /rewild plugins. Respected plugins report through KeepProvider (now
with block areas) or /rewild keep. Rewild's own tracking finds placed
blocks, so CoreProtect isn't needed. Chunks tracked by 0.2.x stay
unknown. /wr and the old permission are removed, as announced.

Tested: 82 unit tests; the bot acceptance suite on throwaway Paper 26.3
(build 249) and 26.2 servers, 113 checks each; the provider test on 26.3,
9 checks. The first 26.3 run found two save-format bugs in the merge,
fixed here with tests. Not seen in a real client; not run on 26.1.2.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
LanternGraves 0.1.2 answers Rewild through a proxy that refuses any
method it doesn't know, including areas(), added in 0.3.0. Rewild took
that as a provider failure and would have reset nothing on any server
running LanternGraves. A refusal of areas() now means no areas; any
other failure still stops resets.

Tested with the real LanternGraves 0.1.2 jar on a throwaway Paper 26.3
server: a grave keeps its chunk and a scan still proposes a run.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@mgilardi
mgilardi merged commit 432f9eb into main Nov 12, 2026
2 checks passed
@mgilardi
mgilardi deleted the rewild-redesign branch November 12, 2026 18:56
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