- Joined
- Nov 14, 2013
- Messages
- 4,150
- Reaction score
- 1,330
Not really sure how to begin this post, so I'll just get straight to the point. The idea is, there would be a new block (here referred to rather awkwardly as a Status Block) that is toggleable on and off. It has three text fields:
Armour Plate Status:
[ArmPlate]
If I wanted, I could also use a clock and stuff to check if the armour is still alive... In this case, I would remove the ON text from the first status block, then have two separate status blocks, both with only on-state text hooked up to some other logic so that they would read "ACTIVE" or "COMPROMISED". Then I could write:
Armour Plate Status:
[ArmPlate][ArmDpl][ArmDed]
And since the three only come up when their logic blocks are set up right, it'll only show one readout. It would appear like this:
Stowed:
Armour Plate Status:
READY FOR DEPLOYMENT
Deployed:
Armour Plate Status:
ACTIVE
Broken/detached/bugged:
Armour Plate Status:
COMPROMISED
...Ideally, it would be possible to even put a variable inside the format line. So, I could have a status block named StatColour with ON-state as #FF0000 and OFF-state as #FFFFFF, and then another named AlertStatus with ON-state as "RED" and OFF-state as "N/A" and then do this:
<style>c=[StatColour]</style>
ALERT STATUS [AlertStatus]
And then when the status block is turned on, the text turns red - possibly for a red-alert function or some such thing:
Alert off:
ALERT STATUS N/A
Alert on:
ALERT STATUS RED
- One line to name the block, which would become the label you use to refer to the block when you put it into display blocks. For instance, if you named a status block "Derp" you would put [Derp] into the display block.
- One text box for the text that a status block would output when it is on.
- One text box for the text that a status block would output when it's off.
(One field could also be left blank, for reasons I'll explain below.)
Armour Plate Status:
[ArmPlate]
If I wanted, I could also use a clock and stuff to check if the armour is still alive... In this case, I would remove the ON text from the first status block, then have two separate status blocks, both with only on-state text hooked up to some other logic so that they would read "ACTIVE" or "COMPROMISED". Then I could write:
Armour Plate Status:
[ArmPlate][ArmDpl][ArmDed]
And since the three only come up when their logic blocks are set up right, it'll only show one readout. It would appear like this:
Stowed:
Armour Plate Status:
READY FOR DEPLOYMENT
Deployed:
Armour Plate Status:
ACTIVE
Broken/detached/bugged:
Armour Plate Status:
COMPROMISED
...Ideally, it would be possible to even put a variable inside the format line. So, I could have a status block named StatColour with ON-state as #FF0000 and OFF-state as #FFFFFF, and then another named AlertStatus with ON-state as "RED" and OFF-state as "N/A" and then do this:
<style>c=[StatColour]</style>
ALERT STATUS [AlertStatus]
And then when the status block is turned on, the text turns red - possibly for a red-alert function or some such thing:
Alert off:
ALERT STATUS N/A
Alert on:
ALERT STATUS RED
). With mine, you'd just need one new block for each boolean state, and if you wanted something other than binary on/off states you'd just need one status block per state.
