Suggestion: Tags for uses in the Display Board

[speed] - return the speed ship is going
[shield%] - returns the percentage of shields
[power%] - returns the percentage of used power

[lastPilot] returns the name of who was in the core most recently? because if you leave the core, you are not flying it any-more :p
[shipname]
[playerpos] returns x, y, z - relative for player to the core.
[shippos] returns x, y, z - sector position of the ship.
[sector]
[solsys]
[home] returns your faction home if you factioned the ship.
...

+1, exept maybe use {} instead of [] as [] is more common than {}

matheod said:

+1, exept maybe use {} instead of [] as [] is more common than {}

Click to expand...

I have to press [AltGr]+[8,9] to access [ and ].
I have to press [AltGr]+[7,0] to access { and }.
Maybe just use %tag% for 0..100% and $tag$ for real values? They are both just [shift]+[4,5] and a lot easier to access than 2 different characters.
Especially hitting a key at right of [space] and [7] (which is almost straight above [space]'s centre) is already annoying while programming.

[turret=turretname]
[power/whatever]
[/turret=turretname]

Anything between those lines shows the stats of that particular turret.

Also, maybe Corehealth or Coretimer, but that has fringe uses.

[passlogic corehealth=0]
If a logic block is associated to the display it lets the logic know the core is overheating. The logic circuit can start a countdown to undock all escape craft in 60 seconds and fire all repulsors it's connected to. Maybe make all the lights onboard wink out and start some emergency lighting protocol. Activate AI on all fixed docks (cept the escape craft) and undock them all. I think ship core overheating is gonna eventually have a damage AoE. So jettisoning cargo and the like free of the doomed ship might be a good idea too.

I dunno. I'm just spitballing.

ToyotaSupra said:

[turret=turretname]
[power/whatever]
[/turret=turretname]

Anything between those lines shows the stats of that particular turret.

Also, maybe Corehealth or Coretimer, but that has fringe uses.

Click to expand...

5x4y_Mega-Dis-Cannon_v0-5_23804z2495240_turret_23405zu20439520
Display blocks have a very limited number of letters. And names change.
Maybe useful with wild-cards...

Maybe just let it be a slave to a rail object and it displays the Entity Name?

iirc schema said something about LUA control. Anyway, yeah, this is going to get some love. it's in the Q&A video on twitch is you want to look it up.

[rotation angle] (available when linked to a turret or rotator block) (It might be fun to see which way a turret has turned. I'm not sure which direction will be zero degrees. Should probably be set to the arrow direction when docking.)
[activecount] (available when linked to one or more logic blocks. Can be used as a counter, or to monitor an in-game computer, or to monitor anything else logic-wise.)
[displayonactive text="text here"] (available when linked to exactly one logic block. Can be used to display "lobby" or "elevator available" or "landing gear down", etc.)
[displayoninactive text="text here"] (available when linked to exactly one logic block. Displays the text when the attached logic sends a false signal.)
[activecrewcount] (counts how many people are piloting/sitting/gravity/aligned/otherwise "on" an entity)
[activenpccount] (same as above, but doesn't count players, only npc's)
[aitype] (linked to a turret docker or to a bobby AI directly; entity ai type: "ship" or "turret")
[aiactive] (same as above, but tells whether ai is "on" or "off")
[aitarget] (same as above, but tells whether ai targets "targeted", "enemy", "astronauts", "missiles", etc.)
[systemhp] (entity system hp)
[armorhp] (entity armor hp)
[distance] (available when linked to a dock or rail; gives the linear distance to the docked entity. Useful for monitoring the location of something, like an elevator or docked ship being moved into or out-of a docking bay.)

Edit:
Anything that returns a number should be usable in a special math call.
Example:
To count the number of players on an entity, not NPCs (technically, this should probably be an additional display tag, but humor me here):
math([activecrewcount]-[activenpccount])

There should also be keywords to replace text depending on logic.
Example:
if([activecount]>0)then([displayonactive])else("Waiting...")

As long as there is a visual-update-LOD optimisation, NP+like.