You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using the "counter" hopper feature and the /counter command for reporting, it outputs as following (example):
[CHAT] Items for red (14,93 min), total: 16438, (66075,0/h):[X]
[CHAT] - Gravel: 3040, 12219,7/h
[CHAT] - Blackstone: 3004, 12075,0/h
The comma is used as a list object separator aswell as a decimal separator within the same line, which makes exporting/transforming to csv and similar formats more difficult.
I'd expect something like this (decimal separated by Full spot/period)
[CHAT] Items for red (14.93 min), total: 16438, (66075.0/h):[X]
[CHAT] - Gravel: 3040, 12219.7/h
[CHAT] - Blackstone: 3004, 12075.0/h
or alternatively (list-separated via semicolon):
[CHAT] Items for red (14,93 min); total: 16438; (66075,0/h):[X]
[CHAT] - Gravel: 3040; 12219,7/h
[CHAT] - Blackstone: 3004; 12075,0/h
This behaviour may be the case with other features of this mod. I just noticed it in the counter feature tho.
The text was updated successfully, but these errors were encountered:
When using the "counter" hopper feature and the /counter command for reporting, it outputs as following (example):
The comma is used as a list object separator aswell as a decimal separator within the same line, which makes exporting/transforming to csv and similar formats more difficult.
I'd expect something like this (decimal separated by Full spot/period)
or alternatively (list-separated via semicolon):
This behaviour may be the case with other features of this mod. I just noticed it in the counter feature tho.
The text was updated successfully, but these errors were encountered: