From the browser into the game

Writing in the browser is comfortable, but the code has to run on the chip in your base. In between sit a computer, the clipboard and a folder on your hard drive.

The editor in the game#

• Build a computer and insert the IC Editor Motherboard. Only then does the computer become a code editor.
• Computer and IC housing must be on the same data network, and both need power.
• An IC10 chip must sit in the housing. On the screen you select the housing, type the code or insert it with Paste, and transfer it to the chip.
• On the move there is the laptop: a portable IC editor. It needs a battery, an IC Editor Motherboard in the motherboard slot and the chip directly in its chip slot.

The library#

Saved scripts live as files on your computer: Documents\My Games\Stationeers\scripts\<title>\instruction.xml. The library is just storage. A script cannot include another one, every program stands on its own.

The IC10 coder in the browser#

• The checker marks things while you type: red for errors, yellow for warnings.
• In the simulator the code runs with test devices, tick by tick.
• Export offers “Copy code” for Paste in the game, “Save .ic10” as a file and “instruction.xml” for the scripts folder. Once the file is there, you find the script in the game's library.
• Import reads an .ic10, .txt or instruction.xml file back in.
• The game version strips comments and blank lines, adjusts line jumps and opens the result as a new file.

A routine that works#

1. Write in the IC10 coder until the checker reports nothing.
2. Run it in the simulator with test values.
3. “Copy code”, Paste in the game, transfer it to the chip.
4. Check the housing for a reported error.

# test run: Kelvin to degrees Celsius
move r0 293.15
sub r1 r0 273.15

In the simulator you see 20 in r1 after one tick. That is how you check every calculation before it goes into the game.