Перейти к содержимому
Mineforgian

Veinminer

Veinminer is a configurable mining mod that lets you break entire veins with a single block break. It keeps the grind down while giving server owners clear controls, limits, and permissions.

Загрузки
419K
Подписчики
118
Обновлён
7 июля 2026 г.
Лицензия
All-Rights-Reserved

Опубликован 7 сентября 2024 г.

Исходный код

⛏ Veinminer

Veinminer is a configurable mining mod that lets players break connected ore and log veins with one normal block break. It keeps the grind down while giving server owners clear controls, limits, and permissions.

No /veinminer setup command is required. Install the mod, hold Shift while mining a supported block, and Veinminer works immediately.

⚙️ Key Features

  • 🧱 Vein Mining — mines connected supported blocks with safe block caps.
  • 🛠️ Activation Choices — Shift/sneak by default, optional client hotkey, hold or toggle mode per player.
  • 🙌 Empty-Hand Support — server owners can allow hand as a tool entry.
  • 🧰 Flexible Block Lists — global block and tool lists for server control.
  • 🪓 Per-Tool Rules — optional advanced per-tool block lists.
  • ⚡ Durability Safety — optional guard to avoid breaking tools.
  • 🔁 Cooldown & Limits — optional cooldown, exhaustion, and max-block controls.
  • ✴️ Particles/Outline — per-player outline particles with color and duration controls.
  • 🔐 LuckPerms Toggle — optional integration for permission-managed servers.
  • 🧪 Advanced Test Command — /vmadvanced test when advanced mode is enabled.
  • 🔄 Live Reloads — /veinminer reload or /vmadmin reload reloads configs from disk.

Works server-side out of the box. Optional client mod adds the hotkey, default V.

🔧 Configuration & Commands

Command quick reference

Player Commands

Command Description
/veinminer Show quick help.
/veinminer help [topic] Help for toggle, reload, activation, togglemessages, or particles.
/veinminer toggle Toggle Veinminer for yourself.
/veinminer activation keybind Switch between Shift and the optional client keybind.
/veinminer activation mode hold|toggle Set your activation mode.
/veinminer togglemessages permission|disabled|cooldown|durability Toggle your own feedback messages.
/veinminer particles toggle Toggle your own outline particles.
/veinminer particles setcolor <red> <green> <blue> Set your own outline particle color.
/veinminer particles setduration <ticks> Set your own outline particle duration.
/veinminer reload Reload configs from disk. Requires admin/manage permission.

Admin Commands

Command Description
/vmadmin blocks add|remove|list|clear <id|#tag> Manage global block lists.
/vmadmin tools add|remove|list|clear <id|#tag|hand> Manage allowed tools.
/vmadmin settings blocklistmode whitelist|blacklist Set global block list mode.
/vmadmin settings maxblocks <value> Set max blocks per activation.
/vmadmin settings cooldown enable|disable|set <seconds> Configure cooldown.
/vmadmin settings exhaustion enable|disable|scale <value> Configure exhaustion cost.
/vmadmin settings luckperms enable|disable Toggle LuckPerms integration.
/vmadmin reload Reload configs from disk.
/vmadmin confirm / /vmadmin cancel Confirm or cancel pending destructive admin actions.

Advanced Commands

Advanced commands are only registered when advanced.enabled = true in GeneralConfig.toml.

Command Description
/vmadvanced blockpertool ... Manage per-tool block lists.
/vmadvanced settings blockpertool Toggle per-tool block list mode.
/vmadvanced test Run the advanced feature test harness.
/vmadvanced confirm / /vmadvanced cancel Confirm or cancel pending destructive advanced actions.

📁 Config Files

Written to config/Veinminer/ (TOML) on first run.

Config file overview

GeneralConfig.toml

  • basic.enabled true
  • basic.activation_key SHIFT
  • basic.require_correct_tool true
  • basic.check_tool_durability true, basic.durability_cap 1, basic.durability_mode ABSOLUTE
  • visual.show_particles true, visual.show_chat_feedback true
  • advanced.enabled false, advanced.debug_logging false
  • advanced.block_limits.max_blocks 64
  • advanced.cooldown.enabled false
  • advanced.exhaustion.enabled false

ToolsList.toml

  • Allowed tools, including optional hand support.

BlocksList.toml

  • Global block list for supported ores, logs, tags, or custom entries.

BlockPerToolList.toml

  • Per-tool block lists when advanced per-tool mode is enabled.

🛡️ Permissions

Permission nodes

General

  • veinminer.use
  • veinminer.reload
  • veinminer.settings.manage
  • veinminer.*

Blocks

  • veinminer.blocks.manage
  • veinminer.blocks.add
  • veinminer.blocks.remove
  • veinminer.blocks.list
  • veinminer.blocks.*

Tools

  • veinminer.tools.manage
  • veinminer.tools.add
  • veinminer.tools.remove
  • veinminer.tools.list
  • veinminer.tools.*

Per-Tool

  • veinminer.blockpertool.manage
  • veinminer.blockpertool.blocks.add|remove|list
  • veinminer.blockpertool.tools.add|remove|list
  • veinminer.blockpertool.blocks.*
  • veinminer.blockpertool.tools.*

Particles

  • veinminer.particles.manage
  • veinminer.particles.enable
  • veinminer.particles.disable
  • veinminer.particles.setcolor
  • veinminer.particles.setduration

🧱 Compatibility

  • ✅ Fabric: Minecraft 1.20 through 26.2.
  • ✅ NeoForge: Minecraft 1.21 through 26.2.
  • ✅ Works on dedicated servers and single-player integrated servers.
  • ❌ No Forge builds are currently planned.

🖥️ Client Optional

Installing the client build enables the hotkey and sends key state to the server. Default key: V. Without the client, Shift/sneak activation remains available for a vanilla-only server-side experience.

📥 Installation

  1. Download the latest build for your loader and Minecraft version.
  2. Drop the jar in /mods.
  3. Restart the server or client.
  4. Play normally. Edit configs or enable advanced mode only if you need admin controls.

💬 Support

Discord: https://discord.gg/43nu6wSWRC

🧰 Other Projects

Ченджлог

3.1.3+26.2Релиз26.2 · 7 июля 2026 г.

Unreleased

Added

  • Added Fabric build support for Minecraft 26.1, 26.1.1, 26.1.2, and 26.2.
  • Added NeoForge build support for Minecraft 26.1, 26.1.1, 26.1.2, and 26.2.
  • Added build/upload metadata entries for the new 26.x Minecraft version format.

Changed

  • Version target normalization now resolves underscore-separated targets such as 26_1, 26_1_1, and 26_2 to dotted Minecraft versions.
  • Fabric 26.x uses a Mojang-named source port because Fabric Yarn and Fabric Intermediary mappings are not published for the new 26.x version format.
  • Fabric 26.x client keybind networking and server outline particles are ported to the available Mojang-named API surface.
  • Fabric 26.x metadata now depends on the current Fabric API mod id, fabric-api.
  • NeoForge 26.x uses version-specific block-break event bridges for the 26.1/26.1.1 and 26.1.2/26.2 event API split.

Validation

  • Verified current Fabric API coordinates exist for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Verified Fabric Yarn and Fabric Intermediary mappings are not published for 26.x, and Mojang 26.2 metadata does not publish client/server mapping downloads.
  • Fabric 26.x buildAllSupported passed for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Smoke-launched the built Fabric 26.2 jar on a real Fabric server with Fabric API 0.154.0+26.2; Veinminer initialized and the server reached Done.
  • NeoForge 26.x buildAllSupported passed for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Smoke-launched the built NeoForge 26.2 jar on a server; Veinminer was discovered, common setup completed, and the server reached Done.

3.1.3

Supported Builds

  • Built and packaged Fabric jars for Minecraft 1.20 through 1.21.11.
  • Built and packaged NeoForge jars for Minecraft 1.21 through 1.21.11.
  • Aligned release identity on 3.1.3 across 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 setup from the documented normal flow; normal users can install the mod and mine supported blocks immediately.
  • Reworked the command layout:
    • /veinminer now owns normal player-facing controls such as toggle, activation mode, message preferences, and particle preferences.
    • /vmadmin now owns always-registered admin/server controls for blocks, tools, settings, reload, confirm, and cancel.
    • /vmadvanced remains hidden unless advanced.enabled = true and 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.11 launch 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.10 and 1.21.11 launch 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 = true startup failures caused by the /vmadvanced test harness 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, and 1.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, and 1.21.11.
  • Runtime smoke testing confirmed advanced.enabled = true no longer blocks world load or command registration across the tested Fabric and NeoForge release matrix.
3.1.3+26.1.2Релиз26.1.2 · 7 июля 2026 г.

Unreleased

Added

  • Added Fabric build support for Minecraft 26.1, 26.1.1, 26.1.2, and 26.2.
  • Added NeoForge build support for Minecraft 26.1, 26.1.1, 26.1.2, and 26.2.
  • Added build/upload metadata entries for the new 26.x Minecraft version format.

Changed

  • Version target normalization now resolves underscore-separated targets such as 26_1, 26_1_1, and 26_2 to dotted Minecraft versions.
  • Fabric 26.x uses a Mojang-named source port because Fabric Yarn and Fabric Intermediary mappings are not published for the new 26.x version format.
  • Fabric 26.x client keybind networking and server outline particles are ported to the available Mojang-named API surface.
  • Fabric 26.x metadata now depends on the current Fabric API mod id, fabric-api.
  • NeoForge 26.x uses version-specific block-break event bridges for the 26.1/26.1.1 and 26.1.2/26.2 event API split.

Validation

  • Verified current Fabric API coordinates exist for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Verified Fabric Yarn and Fabric Intermediary mappings are not published for 26.x, and Mojang 26.2 metadata does not publish client/server mapping downloads.
  • Fabric 26.x buildAllSupported passed for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Smoke-launched the built Fabric 26.2 jar on a real Fabric server with Fabric API 0.154.0+26.2; Veinminer initialized and the server reached Done.
  • NeoForge 26.x buildAllSupported passed for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Smoke-launched the built NeoForge 26.2 jar on a server; Veinminer was discovered, common setup completed, and the server reached Done.

3.1.3

Supported Builds

  • Built and packaged Fabric jars for Minecraft 1.20 through 1.21.11.
  • Built and packaged NeoForge jars for Minecraft 1.21 through 1.21.11.
  • Aligned release identity on 3.1.3 across 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 setup from the documented normal flow; normal users can install the mod and mine supported blocks immediately.
  • Reworked the command layout:
    • /veinminer now owns normal player-facing controls such as toggle, activation mode, message preferences, and particle preferences.
    • /vmadmin now owns always-registered admin/server controls for blocks, tools, settings, reload, confirm, and cancel.
    • /vmadvanced remains hidden unless advanced.enabled = true and 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.11 launch 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.10 and 1.21.11 launch 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 = true startup failures caused by the /vmadvanced test harness 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, and 1.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, and 1.21.11.
  • Runtime smoke testing confirmed advanced.enabled = true no longer blocks world load or command registration across the tested Fabric and NeoForge release matrix.
3.1.3+26.1.1Релиз26.1.1 · 7 июля 2026 г.

Unreleased

Added

  • Added Fabric build support for Minecraft 26.1, 26.1.1, 26.1.2, and 26.2.
  • Added NeoForge build support for Minecraft 26.1, 26.1.1, 26.1.2, and 26.2.
  • Added build/upload metadata entries for the new 26.x Minecraft version format.

Changed

  • Version target normalization now resolves underscore-separated targets such as 26_1, 26_1_1, and 26_2 to dotted Minecraft versions.
  • Fabric 26.x uses a Mojang-named source port because Fabric Yarn and Fabric Intermediary mappings are not published for the new 26.x version format.
  • Fabric 26.x client keybind networking and server outline particles are ported to the available Mojang-named API surface.
  • Fabric 26.x metadata now depends on the current Fabric API mod id, fabric-api.
  • NeoForge 26.x uses version-specific block-break event bridges for the 26.1/26.1.1 and 26.1.2/26.2 event API split.

Validation

  • Verified current Fabric API coordinates exist for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Verified Fabric Yarn and Fabric Intermediary mappings are not published for 26.x, and Mojang 26.2 metadata does not publish client/server mapping downloads.
  • Fabric 26.x buildAllSupported passed for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Smoke-launched the built Fabric 26.2 jar on a real Fabric server with Fabric API 0.154.0+26.2; Veinminer initialized and the server reached Done.
  • NeoForge 26.x buildAllSupported passed for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Smoke-launched the built NeoForge 26.2 jar on a server; Veinminer was discovered, common setup completed, and the server reached Done.

3.1.3

Supported Builds

  • Built and packaged Fabric jars for Minecraft 1.20 through 1.21.11.
  • Built and packaged NeoForge jars for Minecraft 1.21 through 1.21.11.
  • Aligned release identity on 3.1.3 across 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 setup from the documented normal flow; normal users can install the mod and mine supported blocks immediately.
  • Reworked the command layout:
    • /veinminer now owns normal player-facing controls such as toggle, activation mode, message preferences, and particle preferences.
    • /vmadmin now owns always-registered admin/server controls for blocks, tools, settings, reload, confirm, and cancel.
    • /vmadvanced remains hidden unless advanced.enabled = true and 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.11 launch 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.10 and 1.21.11 launch 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 = true startup failures caused by the /vmadvanced test harness 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, and 1.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, and 1.21.11.
  • Runtime smoke testing confirmed advanced.enabled = true no longer blocks world load or command registration across the tested Fabric and NeoForge release matrix.
3.1.3+26.1Релиз26.1 · 7 июля 2026 г.

Unreleased

Added

  • Added Fabric build support for Minecraft 26.1, 26.1.1, 26.1.2, and 26.2.
  • Added NeoForge build support for Minecraft 26.1, 26.1.1, 26.1.2, and 26.2.
  • Added build/upload metadata entries for the new 26.x Minecraft version format.

Changed

  • Version target normalization now resolves underscore-separated targets such as 26_1, 26_1_1, and 26_2 to dotted Minecraft versions.
  • Fabric 26.x uses a Mojang-named source port because Fabric Yarn and Fabric Intermediary mappings are not published for the new 26.x version format.
  • Fabric 26.x client keybind networking and server outline particles are ported to the available Mojang-named API surface.
  • Fabric 26.x metadata now depends on the current Fabric API mod id, fabric-api.
  • NeoForge 26.x uses version-specific block-break event bridges for the 26.1/26.1.1 and 26.1.2/26.2 event API split.

Validation

  • Verified current Fabric API coordinates exist for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Verified Fabric Yarn and Fabric Intermediary mappings are not published for 26.x, and Mojang 26.2 metadata does not publish client/server mapping downloads.
  • Fabric 26.x buildAllSupported passed for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Smoke-launched the built Fabric 26.2 jar on a real Fabric server with Fabric API 0.154.0+26.2; Veinminer initialized and the server reached Done.
  • NeoForge 26.x buildAllSupported passed for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Smoke-launched the built NeoForge 26.2 jar on a server; Veinminer was discovered, common setup completed, and the server reached Done.

3.1.3

Supported Builds

  • Built and packaged Fabric jars for Minecraft 1.20 through 1.21.11.
  • Built and packaged NeoForge jars for Minecraft 1.21 through 1.21.11.
  • Aligned release identity on 3.1.3 across 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 setup from the documented normal flow; normal users can install the mod and mine supported blocks immediately.
  • Reworked the command layout:
    • /veinminer now owns normal player-facing controls such as toggle, activation mode, message preferences, and particle preferences.
    • /vmadmin now owns always-registered admin/server controls for blocks, tools, settings, reload, confirm, and cancel.
    • /vmadvanced remains hidden unless advanced.enabled = true and 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.11 launch 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.10 and 1.21.11 launch 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 = true startup failures caused by the /vmadvanced test harness 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, and 1.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, and 1.21.11.
  • Runtime smoke testing confirmed advanced.enabled = true no longer blocks world load or command registration across the tested Fabric and NeoForge release matrix.
3.1.3+1.21.11Релиз1.21.11 · 7 июля 2026 г.

Unreleased

Added

  • Added Fabric build support for Minecraft 26.1, 26.1.1, 26.1.2, and 26.2.
  • Added NeoForge build support for Minecraft 26.1, 26.1.1, 26.1.2, and 26.2.
  • Added build/upload metadata entries for the new 26.x Minecraft version format.

Changed

  • Version target normalization now resolves underscore-separated targets such as 26_1, 26_1_1, and 26_2 to dotted Minecraft versions.
  • Fabric 26.x uses a Mojang-named source port because Fabric Yarn and Fabric Intermediary mappings are not published for the new 26.x version format.
  • Fabric 26.x client keybind networking and server outline particles are ported to the available Mojang-named API surface.
  • Fabric 26.x metadata now depends on the current Fabric API mod id, fabric-api.
  • NeoForge 26.x uses version-specific block-break event bridges for the 26.1/26.1.1 and 26.1.2/26.2 event API split.

Validation

  • Verified current Fabric API coordinates exist for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Verified Fabric Yarn and Fabric Intermediary mappings are not published for 26.x, and Mojang 26.2 metadata does not publish client/server mapping downloads.
  • Fabric 26.x buildAllSupported passed for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Smoke-launched the built Fabric 26.2 jar on a real Fabric server with Fabric API 0.154.0+26.2; Veinminer initialized and the server reached Done.
  • NeoForge 26.x buildAllSupported passed for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Smoke-launched the built NeoForge 26.2 jar on a server; Veinminer was discovered, common setup completed, and the server reached Done.

3.1.3

Supported Builds

  • Built and packaged Fabric jars for Minecraft 1.20 through 1.21.11.
  • Built and packaged NeoForge jars for Minecraft 1.21 through 1.21.11.
  • Aligned release identity on 3.1.3 across 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 setup from the documented normal flow; normal users can install the mod and mine supported blocks immediately.
  • Reworked the command layout:
    • /veinminer now owns normal player-facing controls such as toggle, activation mode, message preferences, and particle preferences.
    • /vmadmin now owns always-registered admin/server controls for blocks, tools, settings, reload, confirm, and cancel.
    • /vmadvanced remains hidden unless advanced.enabled = true and 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.11 launch 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.10 and 1.21.11 launch 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 = true startup failures caused by the /vmadvanced test harness 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, and 1.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, and 1.21.11.
  • Runtime smoke testing confirmed advanced.enabled = true no longer blocks world load or command registration across the tested Fabric and NeoForge release matrix.
3.1.3+1.21.10Релиз1.21.10 · 7 июля 2026 г.

Unreleased

Added

  • Added Fabric build support for Minecraft 26.1, 26.1.1, 26.1.2, and 26.2.
  • Added NeoForge build support for Minecraft 26.1, 26.1.1, 26.1.2, and 26.2.
  • Added build/upload metadata entries for the new 26.x Minecraft version format.

Changed

  • Version target normalization now resolves underscore-separated targets such as 26_1, 26_1_1, and 26_2 to dotted Minecraft versions.
  • Fabric 26.x uses a Mojang-named source port because Fabric Yarn and Fabric Intermediary mappings are not published for the new 26.x version format.
  • Fabric 26.x client keybind networking and server outline particles are ported to the available Mojang-named API surface.
  • Fabric 26.x metadata now depends on the current Fabric API mod id, fabric-api.
  • NeoForge 26.x uses version-specific block-break event bridges for the 26.1/26.1.1 and 26.1.2/26.2 event API split.

Validation

  • Verified current Fabric API coordinates exist for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Verified Fabric Yarn and Fabric Intermediary mappings are not published for 26.x, and Mojang 26.2 metadata does not publish client/server mapping downloads.
  • Fabric 26.x buildAllSupported passed for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Smoke-launched the built Fabric 26.2 jar on a real Fabric server with Fabric API 0.154.0+26.2; Veinminer initialized and the server reached Done.
  • NeoForge 26.x buildAllSupported passed for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Smoke-launched the built NeoForge 26.2 jar on a server; Veinminer was discovered, common setup completed, and the server reached Done.

3.1.3

Supported Builds

  • Built and packaged Fabric jars for Minecraft 1.20 through 1.21.11.
  • Built and packaged NeoForge jars for Minecraft 1.21 through 1.21.11.
  • Aligned release identity on 3.1.3 across 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 setup from the documented normal flow; normal users can install the mod and mine supported blocks immediately.
  • Reworked the command layout:
    • /veinminer now owns normal player-facing controls such as toggle, activation mode, message preferences, and particle preferences.
    • /vmadmin now owns always-registered admin/server controls for blocks, tools, settings, reload, confirm, and cancel.
    • /vmadvanced remains hidden unless advanced.enabled = true and 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.11 launch 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.10 and 1.21.11 launch 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 = true startup failures caused by the /vmadvanced test harness 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, and 1.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, and 1.21.11.
  • Runtime smoke testing confirmed advanced.enabled = true no longer blocks world load or command registration across the tested Fabric and NeoForge release matrix.
3.1.3+1.21.9Релиз1.21.9 · 7 июля 2026 г.

Unreleased

Added

  • Added Fabric build support for Minecraft 26.1, 26.1.1, 26.1.2, and 26.2.
  • Added NeoForge build support for Minecraft 26.1, 26.1.1, 26.1.2, and 26.2.
  • Added build/upload metadata entries for the new 26.x Minecraft version format.

Changed

  • Version target normalization now resolves underscore-separated targets such as 26_1, 26_1_1, and 26_2 to dotted Minecraft versions.
  • Fabric 26.x uses a Mojang-named source port because Fabric Yarn and Fabric Intermediary mappings are not published for the new 26.x version format.
  • Fabric 26.x client keybind networking and server outline particles are ported to the available Mojang-named API surface.
  • Fabric 26.x metadata now depends on the current Fabric API mod id, fabric-api.
  • NeoForge 26.x uses version-specific block-break event bridges for the 26.1/26.1.1 and 26.1.2/26.2 event API split.

Validation

  • Verified current Fabric API coordinates exist for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Verified Fabric Yarn and Fabric Intermediary mappings are not published for 26.x, and Mojang 26.2 metadata does not publish client/server mapping downloads.
  • Fabric 26.x buildAllSupported passed for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Smoke-launched the built Fabric 26.2 jar on a real Fabric server with Fabric API 0.154.0+26.2; Veinminer initialized and the server reached Done.
  • NeoForge 26.x buildAllSupported passed for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Smoke-launched the built NeoForge 26.2 jar on a server; Veinminer was discovered, common setup completed, and the server reached Done.

3.1.3

Supported Builds

  • Built and packaged Fabric jars for Minecraft 1.20 through 1.21.11.
  • Built and packaged NeoForge jars for Minecraft 1.21 through 1.21.11.
  • Aligned release identity on 3.1.3 across 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 setup from the documented normal flow; normal users can install the mod and mine supported blocks immediately.
  • Reworked the command layout:
    • /veinminer now owns normal player-facing controls such as toggle, activation mode, message preferences, and particle preferences.
    • /vmadmin now owns always-registered admin/server controls for blocks, tools, settings, reload, confirm, and cancel.
    • /vmadvanced remains hidden unless advanced.enabled = true and 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.11 launch 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.10 and 1.21.11 launch 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 = true startup failures caused by the /vmadvanced test harness 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, and 1.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, and 1.21.11.
  • Runtime smoke testing confirmed advanced.enabled = true no longer blocks world load or command registration across the tested Fabric and NeoForge release matrix.
3.1.3+1.21.8Релиз1.21.8 · 7 июля 2026 г.

Unreleased

Added

  • Added Fabric build support for Minecraft 26.1, 26.1.1, 26.1.2, and 26.2.
  • Added NeoForge build support for Minecraft 26.1, 26.1.1, 26.1.2, and 26.2.
  • Added build/upload metadata entries for the new 26.x Minecraft version format.

Changed

  • Version target normalization now resolves underscore-separated targets such as 26_1, 26_1_1, and 26_2 to dotted Minecraft versions.
  • Fabric 26.x uses a Mojang-named source port because Fabric Yarn and Fabric Intermediary mappings are not published for the new 26.x version format.
  • Fabric 26.x client keybind networking and server outline particles are ported to the available Mojang-named API surface.
  • Fabric 26.x metadata now depends on the current Fabric API mod id, fabric-api.
  • NeoForge 26.x uses version-specific block-break event bridges for the 26.1/26.1.1 and 26.1.2/26.2 event API split.

Validation

  • Verified current Fabric API coordinates exist for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Verified Fabric Yarn and Fabric Intermediary mappings are not published for 26.x, and Mojang 26.2 metadata does not publish client/server mapping downloads.
  • Fabric 26.x buildAllSupported passed for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Smoke-launched the built Fabric 26.2 jar on a real Fabric server with Fabric API 0.154.0+26.2; Veinminer initialized and the server reached Done.
  • NeoForge 26.x buildAllSupported passed for 26.1, 26.1.1, 26.1.2, and 26.2.
  • Smoke-launched the built NeoForge 26.2 jar on a server; Veinminer was discovered, common setup completed, and the server reached Done.

3.1.3

Supported Builds

  • Built and packaged Fabric jars for Minecraft 1.20 through 1.21.11.
  • Built and packaged NeoForge jars for Minecraft 1.21 through 1.21.11.
  • Aligned release identity on 3.1.3 across 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 setup from the documented normal flow; normal users can install the mod and mine supported blocks immediately.
  • Reworked the command layout:
    • /veinminer now owns normal player-facing controls such as toggle, activation mode, message preferences, and particle preferences.
    • /vmadmin now owns always-registered admin/server controls for blocks, tools, settings, reload, confirm, and cancel.
    • /vmadvanced remains hidden unless advanced.enabled = true and 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.11 launch 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.10 and 1.21.11 launch 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 = true startup failures caused by the /vmadvanced test harness 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, and 1.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, and 1.21.11.
  • Runtime smoke testing confirmed advanced.enabled = true no longer blocks world load or command registration across the tested Fabric and NeoForge release matrix.

Комментарии

Загружаем…