[1.21.1] Radius not working correctly

[thelapisfox]

Functional Storage Version:
1.5.5

Titanium Version:
4..0.40

I am playing Stoneblock 4, version 1.2.1, and I am running into what appears to be an unintended range cap with the Functional Storage Controller. I have not yet tested this outside of Stoneblock 4, so I am unsure whether this is pack-specific or a general issue.

No matter how many range upgrades are installed, I am unable to link any blocks beyond approximately 484 blocks from the controller. Below are the exact steps and observations from my testing.
(For reference: View Distance and Simulation Distance are both set to 32 chunks, and the controller chunk is force-loaded via FTB Chunks.)

• I placed a Storage Controller at X=2, Y=132, Z=5.
• I verified the base range (config value set to 8), and linking works correctly up to Z = -3.
• I added a single Netherite Upgrade to the controller.
• The maximum linking range extended to Z = -59, which is correct for a 64-block range.
• At this point, behavior becomes inconsistent.
• I added a second Netherite Upgrade to the controller.
• While holding the Linking Tool, I observed the visual outline of the controller’s range and moved outward to locate its boundary.
• As I approached Z ≈ -450, the green border wall became visible in the distance.
• When crossing Z = -465, the border vanished entirely and would not reappear unless I backtracked to approximately Z ≈ -389.
• Moving forward again slowly and using zoom, the visible border appears to be located around Z ≈ -505.
• I attempted to place and link a Controller Access Point at increasing distances.
• Linking fails repeatedly until reaching Z = -479, at which point the Controller Access Point successfully links.
• Any attempt to link beyond Z = -479 consistently fails.

I have checked server/world configs, defaultconfigs, datapacks, and KubeJS scripts, and I do not see anything in the modpack that would impose this limitation. I have also reviewed the Functional Storage source code and have not been able to identify a hard cap that would explain this behavior.

At this point, I am unsure whether this is an internal limitation or an unintended bug, and would appreciate clarification or guidance from the development team.

Expected Behavior:

• The controller’s effective linking range should continue to scale according to the configured range value and the installed range upgrades.
• With two Netherite Upgrades installed (each multiplying the range by 8), the controller should allow linking out to approximately 512 blocks from its position.
• The visual range outline shown while holding the Linking Tool should accurately reflect the maximum distance at which blocks can be linked and should remain visible as long as the player remains within that area.

Actual Behavior:

• Despite the visual range outline extending beyond 500 blocks, linking consistently fails beyond approximately 484 blocks.
• Controller Access Points can only be linked up to Z = -479 relative to the controller’s position.
• Any attempt to link blocks beyond this point fails, regardless of the number of installed range upgrades.
• The visual range outline disappears and reappears inconsistently at long distances, suggesting a mismatch between visual rendering and actual linking logic.

Suggestion:

Regarding the visual range outline, if it cannot reliably represent the true linking limit, a numeric indication could be provided instead, similar to how the Measurements mod displays distances on its rendered lines, either by showing the total effective range or the exact block number at which linking stops.