Skip to content

VH Accelerator 1.0.10 — JEI Cache Correctness Pass

Choose a tag to compare

View all tags
@HoYin1600p HoYin1600p released this 20 Aug 14:18
· 26 commits to master since this release
v1.0.10
e0353e5

VH Accelerator 1.0.10 — JEI Cache Correctness Pass

Released August 20, 2026.

VH Accelerator 1.0.10 hardens the JEI login pipeline after investigating a
case where ordinary crafting-table recipes could be absent from JEI until it
was rebuilt. This release preserves the warm-login performance work while
ensuring cached data cannot own live JEI category decisions or be replaced by
an incomplete late registration batch.

Download

Install the non-sources release artifact:

VH-Accelerator-1.0.10.jar

Detailed changelog since 1.0.9

Fixed

  • Prevented JEI 9 and JEI 10 category handlers from being called concurrently
    during vanilla recipe validation. Structural input validation remains
    parallel, but JEI-owned category classification now runs on the calling
    thread where JEI expects it.
  • Stopped persisting category handled/unhandled decisions. Every login
    reclassifies validated recipes against the live JEI runtime, preventing a
    stale or incomplete category decision from hiding an ordinary recipe on a
    later connection.
  • Split persistent recipe-index data into independent category and batch
    records. A smaller late crafting batch can no longer overwrite the complete
    crafting index prepared earlier in the same login.
  • Invalidated the older recipe-validation and recipe-index cache formats so
    unsafe data created by earlier builds cannot survive this update.

Cache identity and invalidation

  • Recipe-index cache identity is now derived from synchronized recipe
    semantics instead of raw payload layout or unrelated local state.
  • The semantic fingerprint includes recipe identifiers, serializers, recipe
    classes, special/group properties, result stacks, ordered ingredient slots,
    ingredient candidates, and canonical NBT.
  • Ingredient candidates are sorted and deduplicated before hashing. Harmless
    packet, map, or tag iteration-order changes therefore reuse the same cache,
    while actual recipe, tag, server-config, mod-file, server, or JEI-generation
    changes still invalidate it.
  • Cached index plans contain identifiers only. Live recipe objects and JEI
    category ownership are resolved again on every login.
  • If synchronized recipe semantics cannot be captured safely, persistent
    recipe-index reuse is disabled for that connection instead of falling back
    to a weaker fingerprint.

Performance and cleanup

  • Retained bounded parallel structural validation and the existing persistent
    JEI index speedup; only JEI-owned classification returns to the client
    thread.
  • The optional persistent vanilla recipe-validation cache remains disabled by
    default after testing showed that resolving its large manifest could cost
    more than fresh bounded validation.
  • Disabled validation-cache preloading now starts no background reader or
    cache work.
  • Removed redundant raw recipe-payload hashing, temporary fingerprint
    diagnostics, and the obsolete fallback implementation.

Compatibility

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

  • The release build validates against all eight Vault/JEI profiles currently
    maintained by the project:

    • 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 final development build was exercised in the Remastered client with cold
and warm logins. The warm run restored the full persistent index batches while
keeping the normal Vault Recycler crafting-table recipe visible:

  • 16,197 crafting index plans restored in 76 ms
  • 4,636 stonecutting index plans restored in 17 ms
  • 270 furnace index plans restored in less than 1 ms
  • a later 714-recipe crafting batch built independently in 16 ms
  • bounded fresh crafting validation completed in 49 ms
  • no fatal VH Accelerator or JEI errors were reported

Exact timings vary by hardware, mod list, disk cache state, network latency,
and server load. The important verification result is that complete cached
batches were restored without losing the ordinary crafting recipe.

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

Upgrade

  1. Stop Minecraft.
  2. Remove the older VH Accelerator jar from the instance's mods directory.
  3. Place VH-Accelerator-1.0.10.jar in the mods directory.
  4. Launch normally. VHA will reject the older JEI cache formats and rebuild
    compatible data automatically; manual cache deletion is not required.

If JEI is already in a bad state during a live session, /vha reload_jei
remains available as a recovery command. Version 1.0.10 is intended to prevent
the cache-related cause rather than require users to run that command during
normal play.

Assets 3
Loading