Currently, when I use a BADChest’s position as a reference for calculating or marking specific coordinates, there are cases where the Offset tool’s values do not match the BADChest’s actual operating range. I believe this occurs because the BADChest entity is a 1×1 entity, which results in fractional position values at its placement point. This fractional positioning seems to cause inconsistencies in the calculations.To resolve this, it would be helpful to make the BADChest’s positional reference more consistent. I have two suggestions:

1. Increase the BADChest entity size to 2×2. This would ensure its position always resolves to integer coordinates.

2. Apply math.floor to the BADChest position during calculations to remove decimal values and make its behavior more predictable.

Could you review this issue?

The math.floor function is already applied to the coordinates of the building, which is selected as the reference point.

Make sure that the numbers are copied correctly and there are no other signal sources.

By the way, in the last update I forgot to add in description that the Offset tool can write a last measurement in c-comb by selecting it with RMB.

Could you also check whether the Offset Tool is applying the same logic?
The core issue is that the values shown by the BADChest and the Offset Tool do not match.

The BADChest and the Offset Tool cannot share a common code because they work in opposite directions. I have done my best to ensure that the Offset Tool produces the correct result. (my test environment is a field of chests that I deconstruct through the BADChest and undo manually)
There might be inaccuracies when using the "Center" option (another reason why I don't like this option).

Can you describe to me a situation where the BADChest and the Offset Tool produce different results? The only thing that should be enough for me is the values of the signals that you transmit in the BADChest.

I'm currently developing the Planet Linox mod, and I've encountered an issue.

However, the mod does not yet have an English translation, so it's difficult for me to provide the details right now.

I will contact you again once an English translation becomes available.

Well… Planet Linox now officially supports English, but rather than checking for such errors directly, it might be better to provide a way to intuitively visualize the operating range of the BADChest.

Would it be possible to display the operating range using the BADChest’s position and the X, Y, W, H values entered here? That would be a great help.

Search for logging in the mod option (for the map).