HyToolVariants

[0.0.1BETA] — 2026-03

First public beta — initial CurseForge release; everything below is new functionality for this build (no prior published version).

Added

• HyToolVariants — Server plugin that rolls random stat variants on tools (pickaxes, hatchets, shovels, hoes, shears), with per-item persistent BSON metadata. Rolls draw from the default variant pool below (and optional tool special effects such as Vein Mining).
• ECS block-break pipeline — BreakBlockEvent handled via an entity system for reliable player/world resolution (vein-style tooling).
• Vein Mining — Connected ore-only breaking with configurable globs/tiers; optional debug logging for troubleshooting.
• Night Vision (tools) — While holding a tool with the Night Vision roll: PostFx bloom, optional player dynamic light, configurable nightVisionThreshold (default 0.0), nightVisionLightRadius including -1 for max-radius / torch-style behavior, and periodic refresh with network-entity resolution for light updates.
• Tooltips — DynamicTooltipsLib integration when installed (rating, multipliers, etc.); weapon-era variant ids blacklisted in defaults so combat-only lines (e.g. Stun) do not appear on tools.
• Commands & UI — /htv config menu, /htv reload, reroll/apply/dump; debug mode and timestamped logs under mods/HyToolVariants/Logs/.
• Optional integrations — RPGLeveling: Exp Boost can award block-break XP when that mod is present. HyArmourVariants / HyWeaponVariants: optional yield so another mod can own combat pipelines when installed.
• Design — Tool-focused build: combat on-hit systems and weapon-centric variants are off/blacklisted by default. BSON meta root may use legacy hyweaponvariants for compatibility with earlier experiments.

Default variant pool (variantPool)

Default config.json5 entries — each roll picks stat ids with weights; variantCount is 0–3 stats per tool. category limits which tool types can receive that stat.

Tool special effects (default)

Separate from multId multipliers: stored as tool special effect metadata (see toolSpecialEffects in config / defaults in code).

Config files & layout

All paths are relative to the server working directory (typically the folder that contains mods/).

Packaged in the mod JAR (not edited on disk unless you unpack the jar):

• Default HyToolVariants/config.json5 (and fallback HyToolVariants/config/HyToolVariants.json5) — seeds the live config when none exists.
• Common/UI/Custom/HyToolVariants/HwvConfig.ui — layout for the in-game config page (asset pack).

Legacy locations (migrated automatically into mods/HyToolVariants/ when the new file does not exist yet):

• mods/HyToolVariants_HyToolVariants/config.json5
• Plugin data directory: config/HyToolVariants.json5, or HyToolVariants/config.json5, or mods/HyToolVariants/config/HyToolVariants.json5

Metadata: item variant data is stored under the BSON key set by metaRoot in config (default hyweaponvariants for save compatibility).

Commands

Players only; the command is not intended for the console in this build.

Permissions

Strings are defined in code as hyweaponvariants.command.<node> (legacy prefix retained for LuckPerms / existing grants).

Without a permission plugin (no Player.hasPermission(String)): help-level checks allow everyone. Nodes that modify server config, open the menu, change held items, or dump debug (reload, menu, reroll, apply, dump, edit) fall back to operator via isOp() when that method exists; otherwise they are denied.