RC1 opened the near-final lane for Java 26.3 / Wilderness Bound: if nothing critical surfaced, this line was meant to become the ship version. Short fix list, combat-adjacent, exactly what you want before campers flood in. Soft drops still need honest melee grammar.
Fixed in RC1
- Weapons with disable_blocking_for_seconds work again vs blocks_attacks items
- Axes disable shields properly again
- match_block loot predicate no longer always requires a block entity
- Ender-pearl peek-through-blocks angle closed
Why PvP people cared
Axe-vs-shield is foundational Minecraft melee grammar. If disable behavior drifts in a pre-release, every duel spreadsheet lies. Pearl peek exploits are the other classic: tiny angle, huge information cheat. RC1 reading as “restore honesty” was a good omen for the drop.
Even if your Realm plans zero PvP, these fixes still matter. Shield disable shows up in mob pressure and mansion panic. Pearl peek honesty matters for any competitive or semi-competitive server culture that hates free wall hacks. Loot predicate correctness matters the moment someone ships a datapack camp or adventure map on top of Wilderness Bound.
Tester checklist
- Throwaway profile only
- Reproduce axe shield-disable once with your usual kit
- Poke one loot-predicate case if you datapack
- Keep main survival on stable until retail
- Note anything weird in pearl angles and file clean steps
Where RC1 sits in the polish trilogy
- RC1 — combat / shield / predicate / pearl honesty
- RC2 — folder-open freeze
- RC3 — VSync lies, pack saves, sprint-attack feel
Read as a sequence, not three isolated blog posts. Wilderness Bound’s cozy fantasy needed a clean runway: no broken melee assumptions, no UI freezes, no display toggles gaslighting streamers. RC1 was the first-final energy beat that made the later surgical fixes possible.
Failure modes
- Migrating hardcore into RC1 because the forest looks done
- Skipping combat checks because “we only camp”
- Assuming datapack worlds are fine without a predicate poke
- Treating pearl peeks as content instead of a bug to confirm closed
- Hosting public duel nights on an RC without a rollback plan
Why campers should still read combat RCs
Because the same build that ships poplars also ships the melee rules your Realm quietly depends on. Pillager raids, mansion panic, and accidental friend duels all inherit axe-shield honesty. A cozy drop with dishonest combat feels broken in ways players blame on “vibes” instead of patch notes.
Datapack creators get a quieter win from the match_block predicate fix. Adventure maps and custom camp loot tables hate silent always-true/always-false conditions. If you planned Wilderness Bound content packs, RC1 was permission to trust the loot plumbing again — after you retest your own cases.
Pearl peeks deserve one deliberate check too. You do not need a full exploit museum — just confirm the old “see through that corner” habit no longer pays out. Honesty bugs are easy to assume fixed and annoying to rediscover on a public server night.
Keep the soundtrack utilitarian while you test — short combat beds, not full autumn road-trip mixes. Save the campfire playlist for the retail nights RC1 was protecting.
RC1 was the first-final energy beat. RC2/RC3 cleaned freezes and display sync afterward. Together they are why Wilderness Bound could launch without feeling like a snapshot wearing a fake mustache.
Cozy drops still need honest combat grammar — RC1 was that reminder.
PixelCraftMusic
