Idea: Add a Checkbox to the IC-Housing/Code/Watever can be associated with IC10-Code
To allow it to also write Read-Only Properties.
This way we can write our own "Simulation" of the environment as an extra IC10-Code.
Additionally this Code could also allow to execute more than 128 Lines/have more than 128 Lines.
But this would only be secondary, as we could just add more "simulation Housings".
This, together with the Share-Links, could allow someone to create a predefined environment, in which others could test their own code.
Examples:
A basic Airlock which adds/Subtracts Pressure based on the Vent-"On"/"Mode"-State. (two Vents, a GasSensor and two Doors)
Maybe every x Idle Ticks it could simulate door-Button presses.
A Plant simulation, which counts the time the GrowLight is on/off and simulates the SolarSensor.
Based on "if the Plant would be alive" it could also set the ON-State of a Lamp or such, which could be somewhat easy to see.
Idea: Add a Checkbox to the IC-Housing/Code/Watever can be associated with IC10-Code To allow it to also write Read-Only Properties. This way we can write our own "Simulation" of the environment as an extra IC10-Code.
Additionally this Code could also allow to execute more than 128 Lines/have more than 128 Lines. But this would only be secondary, as we could just add more "simulation Housings".
This, together with the Share-Links, could allow someone to create a predefined environment, in which others could test their own code. Examples:
A basic Airlock which adds/Subtracts Pressure based on the Vent-"On"/"Mode"-State. (two Vents, a GasSensor and two Doors) Maybe every x Idle Ticks it could simulate door-Button presses.
A Plant simulation, which counts the time the GrowLight is on/off and simulates the SolarSensor. Based on "if the Plant would be alive" it could also set the ON-State of a Lamp or such, which could be somewhat easy to see.