Thank you for your fine work on the script.

I just overhauled the whole script to make it a lot easier for me to apply changes and add features.
This means i will look into adding thrusters and gyroscopes as block categories now.
Also i'll have to include prototech blocks but since i haven't played the game myself since the update, i will have to check the blocks out before.

Also in the past i worked on a script that will disable thrusters automatically while flying at the speed limit to save fuel. My prototype works stable so far, so i'll try to get a first version of that to the workshop soon. I plan on upgrading it to something like a "copilot" later that gives you some information about your fuel status travel distances and so on.

Your idea sounds great. I will look into it as soon as i have more time to spare. I'm afraid this won't happen before August but after that I should be able to add these features to the script

I would love to see thrusters and gyros added or included into their own categories. Some ideas here for you: For thrusters: thrust totals for each of the 6 directions, max acceleration possible in each direction, amount of thrusters that get damaged, max power or max hydrogen usage of the thrusters, cumulative total of hydrogen or energy consumed, be able to calculate for either the max thrust possible if all thrusters are on and functional, or the current max thrust if thrusters are damaged or offline.

For gyros; roll, pitch, yaw max/current rotational acceleration, max/cumulative power consumption, gyros damaged count, be able to see what the max value and current values for these are based on how many gyros get damaged or go offline, how many gyros are in override or normal operation, total force of override gyros, total force of non-override gyros.

Keep up the good work love to see what you will do next for the community

I just overhauled the settings in the Custom Data of the Programmable Block. They are much more accessible. Also i changed the setup description above. Now it is very clear and easy how to set the script up.

bro wtf.. its so easy to use!!! much thanks

I'm sorry to hear that. I thought that "Battery LCD: 'your text'" and adding 'your text' to the LCD's name isn't complicated. This shouldn't take you more than 10 seconds per block category.
What what be an easier setup in your opinion if i may ask?

Bro, I'm not gunna lie, the lack of example or direction to name the LCDs is so convoluted that it's honestly easier to look for a better script. Sorry.
"very easy setup; no scripting knowledge needed"
I have scripting knowledge and this is still too much for me.

I updated the script in order to enter your settings in the custom data box of the Programmable Block instead of in the script itself. This should make it far more accessible to people without coding knowledge

At the top of the script right below the README-part, there is a section called "Script Settings". There are values called "string ...LCD". On the right side behind the "=", inside the "", there is a default tag which the LCD name has to include. You can also change this tag to your liking.
Every "string ...LCD" value reflects one LCD category.

If you have an idea how to simplify this process let me know. What what be the easiest way you can imagine to set your own LCD name tags?
Would it be easier to make the settings in the Custom Data box of the programmable block instead of the script itself?

I'm squirrel brained and am unsure what im supposed to name the LCD's to get them to reflect what i want displayed?