Skip to content

VH Accelerator 1.0.6 - Wold's Compatibility Pass

Choose a tag to compare

@HoYin1600p HoYin1600p released this 30 Jul 21:04
· 58 commits to master since this release

VH Accelerator 1.0.6 — Wold's Compatibility Pass

Release date: July 30, 2026

VH Accelerator 1.0.6 is the Wold's Compatibility pass. It extends the same
client jar to Wold's Vaults 0.32.2, removes several large-pack launch
bottlenecks discovered there, and tightens cache and texture-safety boundaries
without making Wold's-only mods mandatory.

Download

Install the non-sources artifact:

VH-Accelerator-1.0.6.jar

Do not install the -sources.jar as a mod.

Compatibility

Component Verified baseline
Minecraft 1.18.2
Forge 40.3.11+ in the Forge 40.x line
Wold's Vaults Pack 0.32.2
The Vault in Wold's 3.21.5.6573
Vault Hunters Remastered 20.0.3-remastered, .6872, and .6883
Vault Hunters official 3.21.5.6882 and 3.21.6.6884
Custom MVP 3.21.62
JEI 9.7.2.1001, 10.2.1.1006, and 10.2.1.1009

These are compatibility baselines, not hard dependencies. Optional
integrations activate only when their target mod and validated class layout
are present.

Highlights

  • Wold's Vaults now participates in the unified compatibility build and
    repeated runtime launch testing.
  • ConnectedTexturesMod model-bake graph work is reused across model aliases
    that point to the same live unbaked-model object.
  • Compatible Mekanism, Cable Tiers, Cloud Storage, and MEGA Cells callbacks
    use a launch-scoped namespace index instead of repeatedly scanning the full
    baked-model registry.
  • Complex voxel-shape coordinate merges use an equivalent flat-array
    implementation and automatically yield when Lithium or Canary owns that
    optimization.
  • EveryCompat retains every live generated resource while skipping its
    optional on-disk debug resource mirror on validated versions.

Cache stability

  • Startup timing history, Reforgium renderer timestamps, and FTB sidebar state
    no longer invalidate model caches because those files do not alter model
    resources.
  • Short configuration-write bursts are allowed to settle before the initial
    asset fingerprint is accepted.
  • Resource packs, mod jars, relevant configuration, and pack order remain part
    of cache validation. Real asset changes still rebuild safely.
  • The cache schema is unchanged. An existing installation may perform one
    automatic rebuild if its effective fingerprint changes; no manual cache
    deletion is required.

Safety and compatibility corrections

  • JER menu preloading no longer begins when KubeJS is present because KubeJS
    loot-table scripts require an active server context. JER follows its normal
    login-time initialization in that combination.
  • CTM's custom-renderer mapping is preserved, and unsupported CTM layouts fall
    back to the original CTM handler.
  • Model-bake indexes preserve callback order and all live model-map mutations.
    They change only which known namespace keys a validated callback visits.
  • Baked models, dynamic model state, textures, and live generated resources
    are never persisted by the new paths.
  • A debug-only post-stitch audit checks fragile container, workstation, Curios,
    Comforts, Vault, and EveryCompat sprite groups without changing atlas
    contents.

Configuration

Three guarded options are new and enabled by default:

Option Behavior
optimizeVoxelShapeMerging Uses the equivalent flat-array coordinate merger and yields to Lithium or Canary.
memoizeCtmModelBakeTraversal Reuses CTM graph results for identical live unbaked-model objects on the validated CTM build.
disableEveryCompatDebugResourceDump Skips only EveryCompat's optional disk mirror; live resources remain enabled.

All detailed diagnostics still require diagnostics.debug=true, which remains
off by default. Timer defaults and /vha commands are unchanged.

Upgrade

  1. Stop Minecraft.
  2. Disable or remove the previous VH Accelerator jar.
  3. Place VH-Accelerator-1.0.6.jar in the mods directory.
  4. Keep only one active VH Accelerator jar.

No configuration reset is required.

Verification

  • Clean build, unit tests, mixin-layout checks, and unified-jar verification.
  • Compile verification across all seven Vault and JEI profiles.
  • Repeated optimized and Compare Mode Wold's Vaults launches.
  • Log review for JER/KubeJS work, CTM model wrapping, Forge model callbacks,
    cache reuse, and post-menu work.
  • Client texture and model inspection, including dynamic and placeholder
    sprites that previously exposed unsafe atlas behavior.
  • Smoke testing with Remastered and custom MVP client profiles.

See the full changelog,
configuration and commands, and
testing guide.