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
The LSC currently just displays a running message and nothing more. It would be great to be able to view important information such as battery storage, time to empty/fill on just clicking into the machine.
Your Goal
It has felt like the LSC is rather clunky when needing to use a scanner or a nuclear information block just to view what is vital information. No other mutliblock in gregtech seems to work like this either since they all show the recipe time and even recently the output in seconds.
Your Vision
Would just standardise the mutliblock information output.
Final Checklist
I have searched this issue tracker and there is nothing similar already. Posting on a closed issue saying I like this change please reconsider adding it will prompt us to investigate and reopen it once we confirm your report.
I understand this change request may not attract enough attention and thus not be implemented.
I understand this change request may be rejected due to other community members think it's inappropriate.
I believe this feature would make the pack better.
The text was updated successfully, but these errors were encountered:
Your GTNH Discord Username
Reflex18#9829
Your Pack Version
Nightly 687
Your Proposal
The LSC currently just displays a running message and nothing more. It would be great to be able to view important information such as battery storage, time to empty/fill on just clicking into the machine.
Your Goal
It has felt like the LSC is rather clunky when needing to use a scanner or a nuclear information block just to view what is vital information. No other mutliblock in gregtech seems to work like this either since they all show the recipe time and even recently the output in seconds.
Your Vision
Would just standardise the mutliblock information output.
Final Checklist
The text was updated successfully, but these errors were encountered: