All in title.
At least, if it possible.
Why: There is situations, there one block can be affected by multiple scripts. And all of them can want to read configuration from Custom Data.
Example:
Airvent in pressurised hangar. It can be used by 3 scripts:
- Hangar script
- Airlock script
- Ship status script
Possible solution:
Store configuration for your script in single line. Be tolerant to unrecognized strings.
A little suggestion to community about Custom Data field: do not use it in exclusive way
At least, if it possible.
Why: There is situations, there one block can be affected by multiple scripts. And all of them can want to read configuration from Custom Data.
Example:
Airvent in pressurised hangar. It can be used by 3 scripts:
- Hangar script
- Airlock script
- Ship status script
Possible solution:
Store configuration for your script in single line. Be tolerant to unrecognized strings.
Code:
HangarScript hangar:h1 AirlockScript:name=al1;type=outsideCheck...