Skip to content

VH Accelerator 1.0.11 - Targeted JEI Repair Pass

Choose a tag to compare

View all tags
@HoYin1600p HoYin1600p released this 27 Aug 01:58
· 21 commits to master since this release
v1.0.11
543b22c

VH Accelerator 1.0.11 - Targeted JEI Repair Pass

Released August 26, 2026.

VH Accelerator 1.0.11 fixes a remaining intermittent path where a recipe could
be present in the synchronized recipe manager but absent from JEI until
/vha reload_jei was run. Persistent JEI index reuse remains enabled; VHA now
checks each cached plan against the live JEI lifecycle and repairs only the
affected recipe.

Download

Install the non-sources release artifact:

VH-Accelerator-1.0.11.jar

Detailed changelog since 1.0.10

Fixed

  • Re-runs JEI category ownership against the live runtime whenever a
    persistent recipe-index plan is restored. A category decision captured in a
    previous lifecycle can no longer hide a currently handled recipe.
  • Rebuilds a recipe that the live category handles but the compatible cached
    batch does not contain, without discarding the other validated plans in that
    category.
  • Compares the live recipe-result UID with the cached output UID for ordinary
    single-output recipes. A changed subtype or output mapping rebuilds only
    that recipe plan.
  • Rebinds Sophisticated Storage chest, barrel, and limited-barrel outputs when
    the only UID difference is Minecraft's transient WoodType object identity.
    Other NBT or output differences continue to invalidate and rebuild the plan.
  • Preserves category-owned multi-output plans when a recipe's single default
    result does not represent every output variant published by JEI.

Diagnostics

  • Added /vha jei_audit on|off|status.
  • The audit is disabled by default and is independent of the broader debug
    profiler.
  • When enabled, VHA logs the recipe ID, repair reason, changed ingredient
    roles, and cached-versus-live output UIDs for every targeted repair.
  • /vha now reports the JEI audit state with Compare Mode, timers, and debug.

Cache and performance behavior

  • Advanced the persistent JEI recipe-index format to version 4. Indexes from
    older releases are rejected and rebuilt automatically; users do not need to
    delete cache files.
  • Kept the persistent recipe-index optimization enabled. Warm restores perform
    bounded live ownership and singleton-output validation instead of forcing
    JEI to rebuild every multi-role ingredient index.
  • A failed or changed recipe is rebuilt individually. Valid plans in the same
    category remain reusable.

Compatibility

  • The corrections apply to both isolated compatibility modules in the
    universal jar: JEI 9 and JEI 10.

  • The maintained compatibility matrix remains:

    • Vault Hunters Remastered 20.0.3-remastered, .6872, and .6883
    • Vault Hunters official 3.21.5.6882 and 3.21.6.6884
    • Wolds Vaults 0.32.2/Vault 3.21.5.6573
    • Wolds Vaults 0.33.0/Vault 3.21.6.6884
    • custom MVP Vault 3.21.62
    • JEI 9.7.2.1001, 10.2.1.1006, and 10.2.1.1009

Runtime verification

The release candidate was exercised through full cold and warm client launches
in the Remastered compatibility profile. Both launches reached the CMA test
world without a VHA error, mixin failure, JEI reconciliation failure, or crash.

On the warm launch:

  • 14,046 of 14,047 cached crafting plans were restored and one live plan
    was rebuilt in 113 ms.
  • all 5,863 stonecutting plans were restored in 26 ms.
  • all 279 furnace plans were restored in 1 ms.
  • 57 Sophisticated Storage output plans were rebound to their current
    runtime-only WoodType identities.
  • server/world transfer completed in 7.29 seconds; post-login work completed
    in 2.63 seconds on the test system.

Exact timings vary with hardware, pack contents, cache state, network latency,
and server load. The relevant acceptance result is that the persistent index
was reused while changed live identities were repaired before publication.

The clean release build also runs the unit-test suite, mixin initialization
safety checks, unified JEI 9/10 packaging checks, and all eight maintained
Vault/JEI compatibility profiles.

Upgrade

  1. Stop Minecraft.
  2. Remove the older VH Accelerator jar from the instance's mods directory.
  3. Place VH-Accelerator-1.0.11.jar in the mods directory.
  4. Launch normally. VHA rebuilds the older recipe-index format automatically.

/vha reload_jei remains available as a manual recovery tool for recipe-list
problems caused by other mods or a live session that was already incomplete.
The new targeted repair path runs automatically during normal cached logins.

Assets 3
Loading