Skip to content

VH Accelerator 1.0.7 - Client Launch Efficiency Pass

Choose a tag to compare

View all tags
@HoYin1600p HoYin1600p released this 31 Jul 02:23
· 48 commits to master since this release
v1.0.7
96da7b9

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.

Assets 3
Loading