First your script is very nice.
For idea, it would be a good idea if we can add optional parameter for batteries. Like "optional:input" Would show only energy input and same for output.

Thank you for your fast resond, as suggested, writing here down the idea :)
So yea, would be amazing if you could sizes of bars like wideBar and also font itself as especially using it on small girds and small LCD, lot of space on the screen can be wasted and depending on position can be hard to see exactly what's written. Didn't try scripting SE myself so not sure whats possible and what is not, but
Eg. using some new 'tag' like something, something, font: 2, text:
and depending on what is possible, it would set size of the font to 2 or it would make actual font 2 times bigger, same goes for bars, 'tag' called "imageSize" or "barSize" its important to make those seperate so you could change it how you need it to be :)

also like Nivvidiy said above, having access to those informations (at least in case of "optional" blocks) would be helpful, because even when you try using noHeadline text: - it completly removes % and still being able to use it in text, would be nice.

Sorry for question in here, but writing that had one more question, is it possible to resolve? problem/feature of using text on the end of line because of it taking everything that follows it? If there would be an option to change/finish the line you want to be written, would give lot of new possibilities as being able to mix up %tages with text lines etc :)

Still thank you for your work, took me few hours but made today new beast/miner and your scripts helped a lot in servicing that! <3

@StarAlone¹ (Starry-Kun)
The scaling idea would be possible, but it would completely screw up the formatting.
It would take some serious rework of the code to make it compatible to varying sizes of items.
Or you would have to use the 'Position' Tag every time you have used a not standard sized item.

By the way, there is already a way to put in text with custom able font sizes.
ShowStats
:gfxStart(50,50,2)
HELLO WORLD
gfxEnd

The thing about accessing information:
Have you tried the 'noNames' tag?
see here: https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=2080557454
It can be combined with the 'Text:' Tag.

About the end_text thing:
That would be quite easy to implement.
We just need to put in a new tag like 'EndText:'

Reminder collected from comments:
Individual color options differentiated by display (lcd) and container type.

Just one simple Idea if you're up for it. Enable a Block to display working or not working symbol. For Example an occupied Cryo chamber will have the same block icon, but with a gear and crank to symbolize in use. This can be used for pistons and and rotors.

Hey there :) really like the look of this script!
Any chance it could also be made to display room pressure?

@ShadeWing
Already implemented in the newest version of the script.To be correct, the oxygen pressure of Airvents can be displayed.
Sadly I have to wait for Coffee contacting me.
Only he can publish the updated version (by being the main author)

Would be really cool if you can share a list of what can or cannot be listed on a display.
I'd also love if we could access things like pistons, rotors, doors etc. To see if they're extended or closed etc

Currently Supported:
Shield Generator
Battery (Large Medium Small)
Reactor
Hydrogen Engine (Power Generator, not Thruster)
Cargo Container
Hydrogen Gas Tank
Oxygen Gas Tank
Connector
Ejector
Collector
Ship Drill
Jump Drive
Thruster (All types)
Solar Panel
Wind Turbine
Gas Generator (O2 and H2)
Ship Grinder
Ship Welder
Refinery
Assembler
Large Missile Turret
Large Gatling Turret
Large Interior Turret
Small Gatling Gun
Missile Launcher (Small, Large & Reloadable)
Space Projector

Supported in an not yet published Version: (only Coffee can publish it and I can't reach him)
Air Vent
Parachute

Any chance you could expand this awesome script to include Conveyor Sorters? Many weapons using DarkStar's WeaponCore, including my own mods, are based on Sorters which means I can't display their ammo inventory.

@Qarannia
You know, the sad thing is, that the newest version already supports sorters. But it is not public.
You know Coffee was the original author of FSD. I made a few code suggestions and was added as a coauthor. But coauthors can't publish new code revisions.
The script evolved over more than 130 revisions so far. (Not all were published.)
But I lost contact to Coffee in June '20. My guess is that he doesn't play Space Engineers anymore.
Since I'm just the Coauthor, the 15 latest versions never went public.

I have would have to publish an updated FSD as a new Workshop object.
But I did not had the courage yet. (It feels like stabbing Coffee in the back)
Right now im tinkering with some additional Display information.
Maybe I will publish FSD 2.0 when I'm happy with the current additions.

Would it be possible to add a time to fill/charge and time to empty/dead for batteries and hydrogen tanks? The base game tells you the flight time you have for batteries on the GUI but not for hydrogen tanks, and it's not possible to get that time on an LCD screen. Would be super useful. Thanks!

@hurraybies
Well the task at hand is twofold.

First is to generate the value you want have displayed.
(And I already have a good idea how I could do what you want.)

Second is to make the value user accessible. (Giving the user a command to use)
And here lies the problem.

To understand it, I have to explain the origins FSD.
It was first created by a user named "Coffee" as a kind of easy to use fill rate gauge for blocks with inventories.
You named a block or a group of blocks, and FSD did display how full they were.
Later he added a keyword to instruct FSD to use an alternative (optional) value for some blocks.
Like the power load of a reactor.

But FSD acted always like this: It picks a single block, read a single value from it,( maybe sum this value up with the same kind of value from similar blocks) and display it.

With the evolution of FSD it gained a bunch of new options.
But it is still block based.

So back to the problem.
How could you command FSD to show the current O2 draw, or how long the current H2 storage will last.
These are not values you can pinpoint to a single block. They are a complex functions sourced from a group of values of different block types.
How do you address that?
Special keywords? For just this single kind of value combination?
This would somewhat betray and contradict FSDs origins.
It is more or less still a fancy fill gauge.

It is the same with many other values of interest.
Like Speed, distance, atmospheric altitude etc.
Easy to calculate in a script, but impossible to make accessible with the usual FSD command syntax.

So there is no easy way to get it.
BUT...
In it's current development version FSD gained some potent functions.
Like access to internal values, doing math with it, conditional execution(if-then) etc.
Enabling crafty users to circumvent the limitations of FSD syntax limitations.
But this will be not easy to use. It is basically 'in-script' scripting.
Or to phrase it different:
Adding a programming language to a computer (FSD)
that is emulated on another computer (the PB)
that is emulated by another computer (your PC)
that is maybe also emulated in a form of a virtual machine by another computer.
8-I Brain-BSOD
(For the sake of sanity I will not take this further...)