BitsRecovery spamming "Non-metal voxel type: 2" on every hammer strike with iron blooms (1.22.2)

[ADNA001]

BitsRecovery spamming "Non-metal voxel type: 2" on every hammer strike with iron blooms (1.22.2)

Mod Version

smithingplus@1.9.0-rc.1

Game Version

v1.22.2 (Stable)

Platform

Linux — Kubuntu 26.04 LTS, Kernel 7.0.0-15-generic, Wayland, KDE Plasma 6.6.4

SP/MP

Singleplayer

---

Description

During any smithing session involving iron blooms on the anvil, the BitsRecovery system fires on every single hammer strike, logging Non-metal voxel type: 2 continuously. This causes progressive memory accumulation that results in severe lag and eventually forces the player to exit the game. The issue is specific to iron blooms — the slag voxels (voxel type 2) are being processed by BitsRecovery on each strike instead of being ignored.

This was not present in 1.8.4 on VS 1.21.6, where the same workflow (forge → anvil → repeat) ran without any issues for 16+ hour sessions.

Steps to Reproduce

1. Load a singleplayer world with smithingplus@1.9.0-rc.1 on VS 1.22.2
2. Heat an iron bloom in a forge
3. Place it on an anvil
4. Begin hammering to remove slag voxels
5. Open client-debug.log — observe hundreds of [BitsRecovery] Non-metal voxel type: 2 entries, one per hammer strike
6. After 20-30 minutes of this workflow, the game becomes unplayable due to progressive lag

Evidence from client-debug.log

The following pattern repeats hundreds of times per session, once per hammer strike:

[smithingplus] [BitsRecovery] Non-metal voxel type: 2
[smithingplus] [BitsRecovery] Non-metal voxel type: 2
[smithingplus] [BitsRecovery] Non-metal voxel type: 2

In a 25-minute session of normal iron bloom processing, 362 instances of this log line were recorded.

Additionally, the BitsRecovery system appears to be counting slag hits toward split calculations, which is incorrect:

[smithingplus] [BitsRecovery] Split count below 1 (0.4761905), not recovering bits
[smithingplus] [BitsRecovery] Split count below 1 (0.952381), not recovering bits
[smithingplus] [BitsRecovery] Attempting to recover bits from 1x Item Id 3026, Code game:ironbloom
[smithingplus] [BitsRecovery] ModifyBrokenCount: game:ingot-iron by 1x Item Id 3026, Code game:ironbloom

Expected behavior

BitsRecovery should skip voxel type 2 (slag) silently without logging or processing it, since slag is not metal and should not be part of bit recovery calculations.

Additional context

• Also present in client-debug.log from previous sessions — this is consistent and reproducible every session
• xSkills fork (xskillsfork@1.0.29) is also installed and has its own metallurgy skill with metal recovery — possible interaction between both systems on the same anvil events, but the spam originates from SmithingPlus regardless
• Hardware: AMD Ryzen 5 5600G, AMD Radeon RX 6650 XT, 32 GiB RAM
• Other mods loaded: overhaullib@2.0.3, attributerenderinglibrary@3.1.1, commonlibforked@2.8.1, xskillsfork@1.0.29, toolsmithfork@1.2.20, among others