Tags
Creators
Details
Licensed ARR
Published 2 years ago
Updated last month
All versions
3.1.3+26.2
Release
Veinminer 26.2 (fabric)last month 6,476
Compatibility
Minecraft: Java Edition
26.2
Platform
Fabric
Supported environments
Client-side
Server-side
Client and server
Changes
Unreleased
Added
- Added Fabric build support for Minecraft
26.1,26.1.1,26.1.2, and26.2. - Added NeoForge build support for Minecraft
26.1,26.1.1,26.1.2, and26.2. - Added build/upload metadata entries for the new
26.xMinecraft version format.
Changed
- Version target normalization now resolves underscore-separated targets such as
26_1,26_1_1, and26_2to dotted Minecraft versions. - Fabric
26.xuses a Mojang-named source port because Fabric Yarn and Fabric Intermediary mappings are not published for the new26.xversion format. - Fabric
26.xclient keybind networking and server outline particles are ported to the available Mojang-named API surface. - Fabric
26.xmetadata now depends on the current Fabric API mod id,fabric-api. - NeoForge
26.xuses version-specific block-break event bridges for the26.1/26.1.1and26.1.2/26.2event API split.
Validation
- Verified current Fabric API coordinates exist for
26.1,26.1.1,26.1.2, and26.2. - Verified Fabric Yarn and Fabric Intermediary mappings are not published for
26.x, and Mojang26.2metadata does not publish client/server mapping downloads. - Fabric
26.xbuildAllSupportedpassed for26.1,26.1.1,26.1.2, and26.2. - Smoke-launched the built Fabric
26.2jar on a real Fabric server with Fabric API0.154.0+26.2; Veinminer initialized and the server reachedDone. - NeoForge
26.xbuildAllSupportedpassed for26.1,26.1.1,26.1.2, and26.2. - Smoke-launched the built NeoForge
26.2jar on a server; Veinminer was discovered, common setup completed, and the server reachedDone.
3.1.3
Supported Builds
- Built and packaged Fabric jars for Minecraft
1.20through1.21.11. - Built and packaged NeoForge jars for Minecraft
1.21through1.21.11. - Aligned release identity on
3.1.3across Gradle metadata, generated jar names, and release documentation.
Changed
- Streamlined the default player flow: Veinminer now works out of the box with Shift/sneak activation and no setup wizard.
- Removed
/veinminer setupfrom the documented normal flow; normal users can install the mod and mine supported blocks immediately. - Reworked the command layout:
/veinminernow owns normal player-facing controls such as toggle, activation mode, message preferences, and particle preferences./vmadminnow owns always-registered admin/server controls for blocks, tools, settings, reload, confirm, and cancel./vmadvancedremains hidden unlessadvanced.enabled = trueand contains advanced-only block-per-tool and test tooling.
- Made particle preferences per-player instead of treating all particle toggle/color/duration changes as global server settings.
- Standardized per-player preference storage for both loaders around
config/Veinminer/Players/PlayerData.json. - Preserved transient activation state separately from saved preferences so toggle/key state cleanup does not erase persisted settings.
- Updated README, command documentation, publishing descriptions, and release checklist text to match the streamlined command flow.
Fixed
- Fixed Fabric per-player settings persistence by restoring JSON-backed player preference storage across supported Fabric versions.
- Fixed Fabric saved preferences being overwritten after single-player disconnect/server shutdown.
- Fixed Fabric
1.21.5-1.21.11launch crashes caused by player-data persistence mixin callback descriptors. - Fixed NeoForge new-player defaults so Veinminer, particles, red particle color, and message preferences start enabled as intended.
- Fixed NeoForge
1.21.10and1.21.11launch crashes caused by player-data persistence mixin callback descriptors. - Fixed NeoForge particle/message/Veinminer defaults appearing disabled or black on fresh profiles.
- Fixed
advanced.enabled = truestartup failures caused by the/vmadvanced testharness reflecting an outdated block-limit helper signature. - Historical: fixed setup wizard chat text not being clickable on Fabric
1.21.5-1.21.11. - Historical: fixed setup wizard chat text not being clickable on NeoForge
1.21.5-1.21.11.
Validation
- Full Fabric build matrix passed and produced 19 jars.
- Full NeoForge build matrix passed and produced 12 jars.
- Runtime smoke testing confirmed Fabric settings persistence and basic behaviour on
1.20.4,1.20.6,1.21.1,1.21.4,1.21.8,1.21.10, and1.21.11. - Runtime smoke testing confirmed NeoForge defaults, settings persistence, and clean launch on
1.21.1,1.21.4,1.21.8,1.21.10, and1.21.11. - Runtime smoke testing confirmed
advanced.enabled = trueno longer blocks world load or command registration across the tested Fabric and NeoForge release matrix.
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:MnavVAzj:3MAoLQbn"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:MnavVAzj:3MAoLQbn"
}

