Stormworks Microcontroller framework
A framework for building microcontrollers in Stormworks: Build and Rescue using python scripts.
Features
- Modular design: Easily create and manage multiple microcontroller scripts.
- Latency optimization: Arithmetic functions are collapsed into function blocks in order to reduce latency.
- Auto layout: Automatically arrange function blocks for better readability.
- Integration with
tumflfor lua verification and minification. - Implicit constant number creation.
Getting started
Installation
Install the package using pip
pip install sw_mc_builder
Install using prebuilt binaries
Copy the latest release for your platform from the releases page and add it to your PATH.
Usage
After installing, use the sw_mc_builder module/executable to create microcontrollers.
sw_mc_builder init test_mc.py
Afterwards, you can define a microcontroller in test_mc.py.
from sw_mc_builder import *
input1 = comp.input(SignalType.Number, "Input 1")
input2 = comp.input(SignalType.Number, "Input 2")
added = input1 + input2 * 2
highest = input1.max(input2)
mc = Microcontroller("Example MC")
mc.place_input(input1)
mc.place_input(input2)
mc.place_output(added, "Added")
mc.place_output(highest, "Highest")
if __name__ == "__main__":
handle_mcs(mc)
And finally, run the script to generate the microcontroller (-m).
sw_mc_builder run test_mc.py -m
Design
There are two predominant design patterns used in this framework:
Python operators
from sw_mc_builder import *
input1 = comp.input(SignalType.Number, "Input 1")
input2 = comp.input(SignalType.Number, "Input 2")
added = input1 + input2
maxed = (added * input2).max(1)
Each operation is represented as a python expression. This makes it very easy to write and read code, but latency is harder to reason about, as some operations can result in multiple components.
Component functions
from sw_mc_builder import *
input1 = comp.input(SignalType.Number, "Input 1")
input2 = comp.input(SignalType.Number, "Input 2")
added = comp.add(input1, input2)
multiplied = comp.mul(added, input2)
maxed = comp.function("max(x,y)", multiplied, 1)
Each function represents exactly one component. This makes latency very easy to reason about, as each function has a fixed latency of one tick.
[!INFO] It is discouraged to use numerical or boolean function blocks. In part due to the poor readability, but also because some parts of the optimizer work better, if there are no function blocks.
Caveats of using python operators
and: Use&instead. Keep in mind that&has a different operator precedence thanand.or: Use|instead. Keep in mind that|has a different operator precedence thanor.not: Use~instead. Keep in mind that~has a different operator precedence thannot.int: Use<Wire>.int()instead. Will convert a boolean to a number (0 or 1).__getindex__: (<Wire>[index]): will always return a number. If you want to get a boolean, use<Wire>.get_bool(index)instead.__setindex__: (<Wire>[index] = value): This will create a new composite write for each write.
Functions other than python operators
The Wire class has a few functions that are possible with function blocks.
max(other): Maximum of two wires.min(other): Minimum of two wires.clamp(min, max): Clamp the wire between min and max.lerp(start, end): Linear interpolation between two wires.sin(): Sine of the wire (in radians).cos(): Cosine of the wire (in radians).tan(): Tangent of the wire (in radians).asin(): Arcsine of the wire (in radians).acos(): Arccosine of the wire (in radians).atan(): Arctangent of the wire (in radians).atan2(other): Arctangent of the wire and another wire (in radians).sqrt(): Square root of the wire.ceil(): Ceiling of the wire.floor(): Floor of the wire.round(ndigits): Round the wire.sgn(): Sign of the wire.switch(on_wire, off_wire): Switch between two wires based on the boolean value of the wire.
Working principles
Microcontroller handler
The handle_mcs function is the entity that will bring your microcontrollers to life.
It manages the actual generation (including optimization and layout) and placement of microcontrollers.
It can replace existing microcontrollers in vehicles, or simply make them available ingame.
It can handle multiple microcontrollers at once.
Command line arguments
-mor--microcontroller: Export generated microcontrollers to the games microcontrollers directory.-vor--vehicle: Replace microcontrollers in vehicles in the games vehicles directory. Will reserve parameter settings.-sor--select: Only process microcontrollers with the given, comma separated, names.
Recursive definitions
There is a special component, a Placeholder, which can be used to create recursive definitions.
A Placeholder should be resolved before submitting the microcontroller to handle_mcs,
otherwise an warning will be issued.
from sw_mc_builder import *
counter = comp.placeholder(SignalType.Number)
counter.replace_producer(counter + 1)
Input and output management
Inputs will usually be the first thing to be defined in a microcontroller. They produce Wire objects that can be used in the microcontroller.
If an input is used in any calculation that is present in an output, wi has to be placed in the microcontroller.
Outputs are simply defined by placing them in a microcontroller.
If inputs or outputs are outside of the boundaries of the microcontroller, a warning will be generated, and the microcontroller expanded.
If x and y are none in a input or output definition, the IO will be autoplaced.
from sw_mc_builder import *
input1 = comp.input(SignalType.Number, "Input 1")
input2 = comp.input(SignalType.Number, "Input 2")
# Program logic
added = input1 + input2 * 2
mc = Microcontroller("Example MC")
mc.place_input(input1, 0, 0)
mc.place_input(input2, 0, 1)
mc.place_output(added, "Added", x=1, y=0)
if __name__ == "__main__":
handle_mcs(mc)
Optimizer
All arithmetic operations are collapsed into a single function block in order to reduce latency. This can be disabled per node or per mc.
from sw_mc_builder import *
input1 = comp.input(SignalType.Number, "Input 1")
# Delay signal by one tick, disabling optimization for this node
delayed = comp.function("x", input1).stop_optimization()
# Disable optimization for the entire microcontroller
mc = Microcontroller("name")
mc.stop_optimization()
Microcontroller thumbnails
Microcontroller thumbnails can either be included as a .png file using mc.add_image_from_file(Path("path/to/thumbnail.png")),
or be written as a list of lists of booleans using mc.add_image_from_list(image_data).
Note: Images will automatically be resized to 16x16 pixels and converted to black and white.
Metadata
Release files for sw-mc-builder 0.1.10
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| sw_mc_builder-0.1.10.tar.gz | 30.2 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| sw_mc_builder-0.1.10-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 60.7 kB
Release files / sw_mc_builder-0.1.10.tar.gz
| Download URL | sw_mc_builder-0.1.10.tar.gz |
|---|---|
| Size | 30.2 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
10535e6cbb09493e0c6826242a32fdaa151c30460a3a30b24de650900fbd53a8
|
|
BLAKE2b-256 checksum How to use checksums |
28aad65fd790bbea338f0125bbe77d1144b9b262bc6f9a6661065df70b042cff
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Release files / sw_mc_builder-0.1.10-py3-none-any.whl
| Download URL | sw_mc_builder-0.1.10-py3-none-any.whl |
|---|---|
| Size | 30.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
e30263ccea9f276f04239c652088c0350e8ee7ab16a087c4641fcb18f8f3215a
|
|
BLAKE2b-256 checksum How to use checksums |
d04abc5ff337506000e3e3fa18e9fd421d71675280b7432abd95649eec97237d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.9.25
|
Security for sw-mc-builder 0.1.10
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.