VH Accelerator 1.0.13

1.0.13

Changed

• Update notices now default to showing critical releases only.
• Added the updates.updateTypes config option with CRITICAL and ALL
  choices.
• Added /vha updates critical and /vha updates all; changes apply
  immediately to both menu and chat notices.

VH Accelerator 1.0.12

VH Accelerator 1.0.12 - Update Notification Pass

Released August 27, 2026.

VH Accelerator 1.0.12 adds a small, asynchronous update-notification system
and simplifies the default timing display. Update checks do not wait on
Forge's global version checker, never block launch or world entry, and can be
disabled immediately by the player.

Download

Install the non-sources release artifact:

VH-Accelerator-1.0.12.jar

Added

• Added a reusable GitHub-backed update manifest reader.
• Outdated versions display a coordinated notice on the main menu. Multiple
  supported HoYin1600p mods sort their rows deterministically so notices do not
  overlap.
• Eligible client launches display a rate-limited clickable CurseForge link
  after reaching a playable world.
• Critical notices appear after every five eligible launches; normal notices
  appear after every ten.
• Added updates.checkForUpdates, enabled by default.
• Added /vha updates on|off|status. Turning it off cancels an active request
  and hides both menu and chat notices immediately.
• The bare /vha updates form reports the current state, and /vha includes
  update checks in its combined status summary.

Changed

• Reduced the permanent main-menu timer to launch time only.
• Routine login, transfer, post-login, and disconnect messages now default to
  off. Existing user configuration remains respected.
• Reminder cadence is updated in memory after a successful manifest check and
  the first playable frame, but its small persistent state write waits ten
  client ticks.
• Update reminder state is kept separately in
  config/vhaccelerator-update-notice-state.json; no world or server file is
  modified.

Reliability and privacy

• The manifest request is asynchronous with connection and request timeouts.
• HTTP failures, malformed JSON, abrupt disconnects, and oversized manifests
  fail closed without blocking the client.
• Non-200 responses, incomplete Minecraft promotion data, corrupt local state,
  and an unwritable state path are also nonfatal. They suppress or restart the
  reminder schedule without affecting launch or world entry.
• The download link is the mod's fixed HTTPS CurseForge project URL; remote
  manifest text cannot replace it.
• The manifest endpoint must be raw GitHub HTTPS, the response is bounded to
  262,144 characters, and remote messages are normalized and length-limited.
• When checkForUpdates is false, VHA performs no update request.

Launch counting

A client JVM advances the reminder schedule at most once, and only if its
manifest check confirms an available update and it reaches a playable world.
Later world joins, dimension changes, and server transfers in that JVM do not
count, regardless of the transfer mechanism. A due reminder waits for a
playable world before appearing in chat and can appear only once per JVM.

The once-per-JVM claim replaces connection-screen and proxy-transfer
classification. It therefore behaves consistently across command-based and
proxy-based server clusters without requiring network-specific hooks.

Compatibility impact

• The notifier is client-only and does not require VHA on the remote server.
• No existing optimization, cache fingerprint, JEI integration, Compare Mode,
  or diagnostic command was removed.
• Existing client configuration remains respected. New installations default
  routine timing chat to off and update checks to on.
• Forge's built-in update checker may be disabled by a modpack without
  disabling VHA's bounded asynchronous check.

Verification

• Clean Forge 1.18.2 build and reobfuscation.
• All eight maintained Vault/JEI compile profiles.
• Unified JEI 9/10 jar and mixin initialization-safety checks.
• Unit coverage for parsing, version comparison, per-JVM reminder cadence,
  transfer exclusion, delayed persistence, corrupt state recovery, HTTP
  failures, timeouts, malformed responses, oversized responses, state-write
  failure, and abrupt connection closure.
• Live Remastered launch, main-menu notice, single-player first-frame notice,
  clickable CurseForge message, runtime off/on commands, fifth-launch critical
  cadence, same-JVM rejoin exclusion, and clean shutdown.

Upgrade

1. Stop Minecraft.
2. Remove the older VH Accelerator jar.
3. Place VH-Accelerator-1.0.12.jar in the instance's mods directory.
4. Launch normally. Existing optimization and diagnostic settings are kept.

No cache reset is required.

VH Accelerator 1.0.11 - Targeted JEI Repair Pass

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.

VH Accelerator 1.0.10 — JEI Cache Correctness Pass

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.

VH Accelerator 1.0.9 - JEI Recovery Pass

VH Accelerator 1.0.9 — JEI Recovery Pass

Release date: August 14, 2026

VH Accelerator 1.0.9 adds a safe in-world JEI recovery command for cases where
Minecraft still has a recipe but JEI's visible recipe or ingredient list is
incomplete. It also adds compile and packaging verification for Wolds Vaults
0.33.0.

Download

Install the non-sources artifact:

VH-Accelerator-1.0.9.jar

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

Changelog since 1.0.8

• Added /vha reload_jei, a client-side recovery command that rebuilds JEI
  from the live synchronized recipe and tag state without disconnecting.
• Added Wolds Vaults 0.33.0 to the mandatory compatibility build using Vault
  3.21.6.6884 and JEI 10.2.1.1006.

Added

• Added the client-side /vha reload_jei command.
• The command uses JEI's native stop/start lifecycle to rebuild its runtime
  from the recipes and tags already synchronized to the client.
• The recovery happens without disconnecting from the current world or server.
• Chat and log messages report when the rebuild starts, whether it succeeds,
  and how long it took.

Recovery safety

• VHA's persistent vanilla ingredient cache and persistent recipe-index plans
  are bypassed for the recovery pass.
• Parallel vanilla recipe validation, JEI search-index construction, and
  JEITweaker matching are also bypassed for that pass.
• Stale asynchronous work from the previous JEI runtime is invalidated before
  the rebuild begins.
• Normal configured optimizations resume after the recovery finishes.
• The command is client-only and requires an active world or server connection.

Compatibility

Component	Verified baseline
Minecraft	1.18.2
Forge	40.3.11+ in the Forge 40.x line
Environment	Client
Wolds Vaults	Packs 0.32.2 and 0.33.0; Vault 3.21.5.6573 and 3.21.6.6884
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

The Wolds Vaults 0.33.0 profile is now part of the mandatory compile and
universal-jar compatibility checks using Vault 3.21.6.6884 and JEI
10.2.1.1006.

Verification

• The clean build, unit-test suite, all eight Vault/JEI compatibility profiles,
  mixin initialization checks, and universal JEI 9/10 jar checks passed.
• A live CMA Asgard singleplayer test rebuilt JEI successfully in 5.084 seconds.
• The JEI item grid rendered after recovery.
• Five Vault Recycler recipe matches and one Vault Salvager recipe match were
  present both before and after the rebuild.
• No VHA exception or recovery failure occurred.

Usage

When an entry is missing only from JEI, run:

/vha reload_jei

The client may pause briefly while JEI rebuilds. If the entry remains absent,
retain logs/latest.log before restarting for diagnosis.

Upgrade

1. Stop Minecraft.
2. Remove or disable the previous VH Accelerator jar.
3. Place VH-Accelerator-1.0.9.jar in the mods directory.
4. Keep only one active VH Accelerator jar.

No configuration reset or manual cache deletion is required.

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

VH Accelerator 1.0.8 - Startup Reliability Pass

VH Accelerator 1.0.8 — Startup Reliability Pass

Release date: July 31, 2026

VH Accelerator 1.0.8 fixes a load-order-dependent startup crash reported on a
stock Vault Hunters client, extends the Vault Sigil placeholder correction to
Sophisticated Backpacks settings screens, and hardens every configured mixin
against the same static-initialization failure class.

Download

Install the non-sources artifact:

VH-Accelerator-1.0.8.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
Environment	Client
Wolds Vaults	Pack 0.32.2 / Vault 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 tested compile and compatibility baselines rather than hard
dependencies. Optional integrations activate only when their target mod and
validated class layout are present.

Startup crash fix

• Fixed a DataFixerBuilder.build() startup crash that could occur when
  Minecraft invoked VH Accelerator's DataFixer redirect during the target
  class's own static initialization.
• The no-warm-up executor is now created inside the redirect invocation, so it
  cannot be observed before initialization regardless of transformation or
  class-loading order.
• The optimization remains active. Minecraft's DataFixer and its on-demand
  migration behavior are preserved; this does not disable the affected
  module to avoid the crash.
• Compare Mode continues to use Minecraft's original executor and behavior.

Sophisticated Backpacks rendering

• Remembered Vault Sigils without their original model NBT now render Vault's
  neutral lower-alpha Sigil placeholder in the dedicated Sophisticated
  Backpacks settings screen.
• The same safe placeholder path is shared with the normal backpack inventory
  screen.
• Sigils carrying their dynamic model NBT and all unrelated remembered items
  continue through their existing render paths.

Initialization hardening

• Audited all 97 configured mixins for initialized static state and early
  target-class execution.
• Removed class initializers from every configured mixin. Registry validation
  and model-preparation worker state now live in ordinary holder classes whose
  initialization is guaranteed by the JVM before use.
• Changed the voxel-shape optimization decision to use a zero-safe uncaptured
  state, preventing an unusually early call from permanently selecting the
  wrong launch behavior.
• Changed staged Vault group timing to track token validity explicitly rather
  than depending on a non-default numeric sentinel.
• Added a mandatory build check that fails and names the class if a configured
  mixin ever emits a static initializer again.

Verification

• Full build and unit-test suite completed successfully.
• Universal release-jar contents and optional-mod isolation checks passed.
• Compile verification passed against all seven Vault/JEI compatibility
  profiles.
• Compiled-bytecode inspection confirmed that none of the 97 configured
  mixins contains a class initializer.
• The reported crash trace resolves to the corrected DataFixer path; the
  earlier Iceberg/Vault screen-overwrite warning in that log is unrelated.

Upgrade

1. Stop Minecraft.
2. Remove or disable the previous VH Accelerator jar.
3. Place VH-Accelerator-1.0.8.jar in the mods directory.
4. Keep only one active VH Accelerator jar.

No configuration reset or manual cache deletion is required.

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

VH Accelerator 1.0.7 - Client Launch Efficiency Pass

VH Accelerator 1.0.7 — Client Launch Efficiency Pass

Release date: July 30, 2026

VH Accelerator 1.0.7 removes three more sources of client-launch overhead
without widening the live-state threading boundary. It reduces speculative
DataFixerUpper work, replaces an expensive Vault loot setup path with an
equivalent indexed implementation, and can learn FerriteCore's temporary table
capacity for later launches.

Download

Install the non-sources artifact:

VH-Accelerator-1.0.7.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
Environment	Client
Wolds Vaults	Pack 0.32.2 / Vault 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 tested compatibility baselines rather than hard dependencies.
Optional integrations activate only when their target mod and validated class
layout are present.

Client launch improvements

• Minecraft's DataFixer remains fully available for on-demand migration of old
  client data, but its speculative all-rules background warm-up no longer
  competes with startup. Compare Mode retains the original warm-up path.
• Vault Hunters' tiered-loot cumulative distribution uses hash-based grouping
  instead of repeated linear bucket searches. The same permutations,
  heuristic ordering, probabilities, packed keys, and cumulative values are
  retained.
• When FerriteCore is installed, VH Accelerator records only the completed
  launch's temporary baked-quad entry count. Later launches use that learned
  capacity to avoid repeatedly growing and rehashing a multi-million-entry
  table.

No baked model, quad, texture, or other FerriteCore-owned data is persisted.
An absent or incompatible FerriteCore leaves its original path unchanged.

Configuration

Two guarded client options are new and enabled by default:

Option	Behavior
preSizeFerriteCoreQuadCache	Learns and reuses only FerriteCore's temporary table capacity when FerriteCore is present.
optimizeVaultLootCdf	Uses the equivalent hash-bucket implementation for Vault tiered-loot setup.

DataFixer rule warm-up suppression follows the client optimization master
switch and Compare Mode.

Verification

• Clean build, unit tests, mixin-layout checks, and unified-jar verification.
• Compile verification across all seven Vault and three JEI baselines.
• Exact-output randomized and edge-case tests for Vault tiered-loot cumulative
  distributions.
• Repeated client launch testing across official, custom, and Wolds-based
  profiles.
• Five consecutive Wolds launches completed without an Accelerator error,
  mixin failure, or new error signature.
• All 124 protected fragile block-atlas sprites passed the texture-safety
  audit on every Wolds launch.
• FerriteCore learned and safely reused an approximately three-million-entry
  table capacity on subsequent large-pack launches.

Upgrade

1. Stop Minecraft.
2. Remove or disable the previous VH Accelerator jar.
3. Place VH-Accelerator-1.0.7.jar in the mods directory.
4. Keep only one active VH Accelerator jar.

No configuration reset or manual cache deletion is required. The first
FerriteCore-enabled launch learns capacity; later launches can reuse it.

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

VH Accelerator 1.0.6 - Wold's Compatibility Pass

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.

VH Accelerator 1.0.5

VH Accelerator 1.0.5

Release date: July 29, 2026

VH Accelerator 1.0.5 restores dynamic textures that some Forge 1.18.2 mods
register while Minecraft builds its block texture atlas.

Download

Install the non-sources artifact:

VH-Accelerator-1.0.5.jar

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

Fixed

• Comforts sleeping bags no longer render with missing textures.
• Empty Curios slots and Vault workstation slots now display their intended
  placeholder icons.
• Other event-added block-atlas textures, including Sophisticated container
  placeholders, retain their normal registration when the persistent model
  material cache is restored.

Upgrade

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

No configuration reset or cache deletion is required.

Compatibility

This patch retains the Minecraft 1.18.2, Forge 40.3.11+, Vault Hunters, and JEI
compatibility baselines from 1.0.4.

Verification

• Built the unified jar against all four supported Vault and JEI profiles.
• Confirmed the affected mods register their sprites through identity-based
  Forge texture-stitch listeners.
• Confirmed restored block-atlas identifiers now use Minecraft's canonical
  atlas object.

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

VH Accelerator 1.0.4

VH Accelerator 1.0.4

Release date: July 29, 2026

VH Accelerator 1.0.4 fixes remembered Vault Sigils displaying as
missing-texture squares in empty Sophisticated Storage slots.

Download

Install the non-sources artifact:

VH-Accelerator-1.0.4.jar

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

Fixed

• Empty memory slots containing a remembered Vault Sigil now display Vault's
  neutral Sigil placeholder instead of Minecraft's missing-model texture.
• Sophisticated Storage's normal dimmed remembered-slot overlay is preserved.
• Sigils with their model data intact continue through Vault's normal dynamic
  renderer, and other remembered items are unaffected.

Upgrade

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

No configuration reset or cache deletion is required.

Compatibility

The compatibility correction activates only when both Vault Hunters and
Sophisticated Core are installed. This patch retains the Minecraft 1.18.2,
Forge 40.3.11+, Vault Hunters, and JEI compatibility baselines from 1.0.3.

Verification

• Built the unified jar against all four supported Vault and JEI profiles.
• Verified the corrected jar in the VaultCrafters test instance.
• Confirmed the remembered Sigil placeholder renders correctly.
• Verified populated Sigils and unrelated remembered items retain their
  original rendering paths.

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