Describe the content or mechanics you are proposing.
Add a new property (say, a "tag") to all blocks. The value of the tag would be shown when the mouse is over the block, in the same way the message block shows the text. Tags would be formatted in the same way as the message blocks's texts, but might support shorter length (say, 50-100 characters).
Tags would be stored in schematics.
The tag might be settable in two ways (even implementing just one of them would be good enough):
By setting a property using Logic, e.g. control @tag switch1 "Pause processing"
By editing the tag in the user interface the way message block text can be edited.
Tags wouldn't support print/printflush, so that message blocks wouldn't become obsolete.
Tags should not be sensable (could be a write-only property inside Logic), to prevent a possibility of transferring strings between processors.
Describe how you think this content will improve the game. If you're proposing new content, mention how it may add more gameplay options or how it will fill a new niche.
Tags would have two primary uses:
To identify a switch, or another block, in larger schematics. It would describe what the switch is supposed to do, or what input/output is expected at given points to the schematics. For some small schematics consisting of just a processor and maybe a switch, being able to see what the schematics actually is without having to open up the page and look at the code would be great.
If settable by a processor, it could be used to display some very simple state information. For more complicated outputs, print/printflush would still be required, therefore not making message blocks obsolete.
Before making this issue, check the boxes below to confirm that you have acknowledged them.
[X] I have checked the Trello to make sure my suggestion isn't planned or implemented in a development version.
[X] I am familiar with all the content already in the game or have glanced at the wiki to make sure my suggestion doesn't exist in the game yet.
[X] I have read README.md to make sure my idea is not listed under the "A few things you shouldn't suggest" category.
Describe the content or mechanics you are proposing.
Add a new property (say, a "tag") to all blocks. The value of the tag would be shown when the mouse is over the block, in the same way the message block shows the text. Tags would be formatted in the same way as the message blocks's texts, but might support shorter length (say, 50-100 characters).
Tags would be stored in schematics.
The tag might be settable in two ways (even implementing just one of them would be good enough):
control @tag switch1 "Pause processing"Tags wouldn't support print/printflush, so that message blocks wouldn't become obsolete.
Tags should not be sensable (could be a write-only property inside Logic), to prevent a possibility of transferring strings between processors.
Describe how you think this content will improve the game. If you're proposing new content, mention how it may add more gameplay options or how it will fill a new niche.
Tags would have two primary uses:
Before making this issue, check the boxes below to confirm that you have acknowledged them.