Logic World Wiki - User contributions [en]

Blotter File Format/v7

2025-10-13T00:57:01Z

Felipe: add choices section

The Blotter File Format, successor to the format known as ".tung files", is a system for storing the components and wires of a Logic World world. It is used for both full world saves as well as partial worlds (the data structure used by Subassemblies), but there are slight differences between the two.

= File types =

* '''World files:'''
** Represent a full, playable world space
** May have zero or more root components at different positions/rotations in the world
** Use <code>.logicworld</code> file extension
** All circuit states are stored contiguously, from circuit state 0 through the highest state.
* '''PartialWorld files:'''
** Represent a substructure within a playable world space; can be loaded and added to a world with each root at an arbitrary position/rotation
** Must have at least one root component
** Use <code>.partialworld</code> file extension
** Has a list of circuit state indexes that are On. All indexes not listed here are inferred as being Off.

== File structure ==

* [[#Header|Header]] (16 bytes)
* '''Save info'''
** [[#Save_Format_Version|Save Format Version]] (1 byte)
** [[#Game_version|Game version]] (16 bytes)
** [[#Save_type|Save type]] (1 byte)
** [[#Component_and_wire_counts|Number of components and wires]] (8 bytes)
** [[#Mod_versions|Mod versions]] (4+ bytes, dependent on the number of mods in the save)
** [[#Component_IDs_Map|Component IDs Map]] (4+ bytes, dependent on the number of loaded component IDs)
* '''Object data'''
** [[#Components_data|Components data]] (0+ bytes, dependent on the number of components)
** [[#Wires_data|Wires data]] (0+ bytes, dependent on the number of wires)
** [[#Circuit_states|Circuit states]] (4+ bytes, variable, has a different format for Worlds and PartialWorlds)
* [[#Footer|Footer]] (16 bytes)

The "Save Info" data is at the beginning of the file so that it is easy to extract as metadata. This is done by the game itself in a few places, as well as logicworld.net when uploading a save there.

== Header and footer ==

=== Header ===
The first 16 bytes of every Blotter file are <code>4C-6F-67-69-63-20-57-6F-72-6C-64-20-73-61-76-65</code>, which is UTF-8 for “Logic World save”.

=== Footer ===
The final 16 bytes of every Blotter file are <code>72-65-64-73-74-6F-6E-65-20-73-75-78-20-6C-6F-6C</code> , which is UTF-8 for “redstone sux lol”.

The header and footer exist to protect against save corruption. If the file does not have them, we know that something is wrong with the file.

== Save Format Version ==
One byte specifies the save format version. Currently this is <code>07</code>.

== Game version ==
16 bytes store the game [[#version|version]] that this save was created in.

== Save type ==
There are two types of file that use the Blotter format, Worlds and PartialWorlds. One byte specifies which type of file this is.
{| class="wikitable"
!Byte
!Meaning
|-
|<code>00</code>
|Unknown/error
|-
|<code>01</code>
|World
|-
|<code>02</code>
|PartialWorld
|-
|<code>03</code> - <code>FF</code>
|Reserved for future use
|}

== Component and wire counts ==
Here there are two [[#int|ints]]. The first specifies the number of components in the save, the second specifies the number of wires.

== Mod versions ==
Mods will be included if components they provide are used in this save. This is so that if a later mod version has changes, older save files can be converted.

* An [[#int|int]] for the number of mod versions stored in this file
* For each mod version:
** A [[#string|string]] for the text ID of the mod
** A [[#version|version]] for the version of the mod that this save was created with

== Component IDs Map ==
When humans add component types to Logic World, they use text IDs like <code>MHG.CircuitBoard</code>. To make save files and network packets small in size, the game internally uses numeric IDs to reference component types. The relationship between text IDs and numeric IDs is not deterministic or consistent between different save files, so the map from text IDs to numeric IDs must be stored with the save.

First we write an [[#int|int]] for the number of component IDs in this file.

One by one the mappings are written to the file:

* A 2-byte unsigned integer for the numeric ID of the component
* A [[#string|string]] for the text ID of the component

== Components data ==
One by one, every component is listed in the file. The first component must be a root component -- i.e. have an address of <code>C-0</code> for its parent -- and every subsequent component must have a parent that was listed before it.

It is explicitly okay to have a World file with no components in it (i.e. an empty world). However, a PartialWorld file must have at least one component.

Each component is written like so:

* The [[#component_address|component address]] of this component
* The [[#component_address|component address]] of the component's parent
* 2 bytes for the numeric ID of the component's type (see [[#Component_IDs_Map|Component IDs Map]])
* Three [[#int|ints]] for the local fixed position of the component; <code>x y z</code>
** One unit in the fixed position corresponds to a distance of 0.001 game units, or 1mm
* Four [[#float|floats]] for the local rotation of the component as a quaternion; <code>x y z w</code>
* Information about the component's inputs:
** An [[#int|int]] for the number of inputs the component has
** For each input:
*** An [[#int|int]] for the input's circuit state ID
* Information about the component's outputs:
** An [[#int|int]] for the number of outputs the component has
** For each output:
*** An [[#int|int]] for the output's circuit state ID
* The component's custom data:
** An [[#int|int]] for the number of bytes in the custom data
*** If the component has no custom data, <code>-1</code> may be written instead of <code>0</code>
** All the bytes of the custom data, in order

== Wires data ==
One by one, every wire is listed in the file.

* The [[#peg_address|peg address]] of the wire's first point
* The [[#peg_address|peg address]] of the wire's second point
* An [[#int|int]] for the wire's circuit state ID
* A [[#float|float]] for the wire's rotation, relative to the default rotation it would have

We do not need to save wire addresses; nothing in the save file needs to reference them, and there is no need for them to be consistent between save loads. Instead, wire addresses are dynamically assigned when the save is loaded.

== Circuit states ==
We've saved the circuit state IDs of all the pegs and wires in the save. Now we need to save the values of those state IDs, so states can be looked up.

A state is either on or off. At runtime, the game stores all circuit states from zero through the highest state in a contiguous block of memory.

=== World files ===
Worlds are large, and generally use most circuit states, starting from state 0. All circuit states are listed.

* First an [[#int|int]] for the number of bytes in this sequence
* Then, that number of bytes. Each bit represents the value of the next circuit state; each byte contains 8 states.
** If, when saving the game, the number of circuit states is not divisible by 8, the last byte will be padded.

=== PartialWorld files ===
PartialWorlds represent a subset of a World. Most of the circuit states in a world will be irrelevant to a particular PartialWorld, so it would be silly and wasteful to save all of them with every PartialWorld.
Instead, we save a list of circuit state IDs which are both used in this PartialWorld and have a state of on. All unlisted state IDs are assumed to be in the off state.

* First an [[#int|int]] for the number of ints in this sequence
* Then, that number of ints. Each int signifies a state ID with a value of on.

== Sub-standards ==

==== '''Int''' (4 bytes) ====
32 bit signed integers, little endian.

==== '''Float''' (4 bytes) ====
32 bit floating point values, little endian.

==== '''Boolean''' (1 byte) ====
An entire byte that is either <code>00</code> for false or <code>01</code> for true.

==== '''String''' (4+ bytes) ====
An int for the number of bytes in the string, followed by that number of bytes, representing that string in UTF-8.

==== '''Version''' (16 bytes) ====
Versions contain four numbers (i.e. 1.0.3.1069). These four numbers are written to the file in order, each as a 4-byte int. Thus, 4x4 bytes = 16 bytes for this. Note: if any of these four numbers are missing, they will be saved as <code>-1</code>. So if your mod defines its version as <code>1.2</code>, the four numbers will be <code>1</code>, <code>2</code>, <code>-1</code>, <code>-1</code>. This is not our fault, it's just how System.Version works.

==== '''Component Address''' (4 bytes) ====
Component Addresses are written as 32 bit unsigned integers, little endian.

==== '''Peg Address''' (9 bytes) ====

* One byte to indicate the peg type:

{| class="wikitable"
!Byte
!Meaning
|-
|<code>00</code>
|Undefined
|-
|<code>01</code>
|Input peg
|-
|<code>02</code>
|Output peg
|-
|<code>03</code> - <code>FF</code>
|Reserved for future use
|}
Any value other than <code>01</code> or <code>02</code> is invalid.

* A component address for the component of the peg
* An int for the zero-based index of the peg (i.e. is it the 0th input, the 1st input, etc)

== A note on seemingly-bizarre design choices ==
This file structure is not the most efficient, most beautiful, or most logical way to lay out the data. The primary purpose of the design of the Blotter format is that it is easy to integrate them with the game code. Therefore, the format uses the exact same data structures used by the game. This makes it fast and simple to convert the game state to a save file and vice versa, but since these data structures are optimized for runtime, the files do look a little weird.

* '''"Why are circuit states stored so weirdly? Why not directly save the state of an input/output, instead of a reference to a state index?"'''
** This is how the game stores circuit states at runtime, for performance and for ease of synchronization between the client and server. Storing it this way in the file makes for easy interoperability with the runtime game code, and allows us to use the same component/wire data structures in the saves and in the game.
* '''"Must all the circuit states be stored? Surely you only need the states of the inputs or outputs, and everything else (including the wires) can be inferred from those."'''
** This is true for the server, but the client has no ability to run a simulation and infer other states. However, the client needs to know all the states so that it can render a PartialWorld correctly before it is placed and added to the server's world/simulation. Storing all the states is also just simpler, and requires fewer steps when loading a save.
* '''"Why in god's name are all the integers signed when come on they really should be unsigned?"'''
** Logic World is written in C#. The .NET runtime has a few weird quirks, and one of those quirks is that most integers are signed, even things that can never be below zero like array lengths and indexes. Since this file format is designed for maximum interoperability with the code, this quirk is copied, and we use signed ints a lot.

2025-09-10T21:02:35Z

Felipe: add nowrap class

.lw-infobox {
background-color: var(--background-color-interactive-subtle,#f8f9fa);
color: var(--color-base,#202122);
border: 1px solid var(--border-color-subtle,#c8ccd1);
}

.tabber .wikitable {
margin-top: 0;
}

/* CSS variables for the binary signal graph */
body {
--signal-border: 3px solid rgb(239, 53, 53);
--tick-marker-border: 1px solid var(--border-color-base);
}

/* === Navbox styles === */
.mw-parser-output .navbox {
border:1px solid #aaa;
box-sizing:border-box;
width:100%;
margin:auto;
clear:both;
font-size:88%;
text-align:center;
padding:1px
}
.mw-parser-output .navbox-inner,
.mw-parser-output .navbox-subgroup {
width:100%
}
.mw-parser-output .navbox+.navbox-styles+.navbox {
margin-top:-1px
}
.mw-parser-output .navbox th,
.mw-parser-output .navbox-title,
.mw-parser-output .navbox-abovebelow {
text-align:center;
padding-left:1em;
padding-right:1em
}
.mw-parser-output th.navbox-group {
white-space:nowrap;
text-align:right
}
.mw-parser-output .navbox,
.mw-parser-output .navbox-subgroup {
background:#fdfdfd
}
.mw-parser-output .navbox-list {
border-color:#fdfdfd
}
.mw-parser-output .navbox th,
.mw-parser-output .navbox-title {
background:#eaeeff
}
.mw-parser-output .navbox-abovebelow,
.mw-parser-output th.navbox-group,
.mw-parser-output .navbox-subgroup .navbox-title {
background:#ddddff
}
.mw-parser-output .navbox-subgroup .navbox-group,
.mw-parser-output .navbox-subgroup .navbox-abovebelow {
background:#e6e6ff
}
.mw-parser-output .navbox-even {
background:#f7f7f7
}
.mw-parser-output .navbox-odd {
background:transparent
}
.mw-parser-output th.navbox-title1 {
border-left:2px solid #fdfdfd;
width:100%
}
.mw-parser-output td.navbox-list1 {
text-align:left;
border-left-width:2px;
border-left-style:solid
}
.mw-parser-output .navbox .hlist td dl,
.mw-parser-output .navbox .hlist td ol,
.mw-parser-output .navbox .hlist td ul,
.mw-parser-output .navbox td.hlist dl,
.mw-parser-output .navbox td.hlist ol,
.mw-parser-output .navbox td.hlist ul {
padding:0.125em 0
}
.mw-parser-output .navbox .hlist dd,
.mw-parser-output .navbox .hlist dt,
.mw-parser-output .navbox .hlist li {
white-space:nowrap
}
.mw-parser-output .navbox .hlist dd dl,
.mw-parser-output .navbox .hlist dt dl,
.mw-parser-output .navbox .hlist li ol,
.mw-parser-output .navbox .hlist li ul {
white-space:normal
}
.mw-parser-output ol+.navbox-styles+.navbox,
.mw-parser-output ul+.navbox-styles+.navbox {
margin-top:0.5em
}
@media screen {
html.skin-theme-clientpref-night .mw-parser-output th.navbox-title {
background-color:#345
}
html.skin-theme-clientpref-night .mw-parser-output th.navbox-group {
background-color:#567
}
html.skin-theme-clientpref-night .mw-parser-output td.navbox-abovebelow,
html.skin-theme-clientpref-night .mw-parser-output th.navbox-group,
html.skin-theme-clientpref-night .mw-parser-output td.navbox-subgroup td.navbox-title {
background-color:#456
}
html.skin-theme-clientpref-night .mw-parser-output td.navbox-even {
background-color:#000
}
html.skin-theme-clientpref-night .mw-parser-output td.navbox-odd {
background-color:#123
}
html.skin-theme-clientpref-night .mw-parser-output .navbox,
html.skin-theme-clientpref-night .mw-parser-output .navbox-subgroup,
html.skin-theme-clientpref-night .mw-parser-output .navbox-list {
background-color:#111111
}
html.skin-theme-clientpref-night .mw-parser-output tr+tr>.navbox-abovebelow,
html.skin-theme-clientpref-night .mw-parser-output tr+tr>.navbox-group,
html.skin-theme-clientpref-night .mw-parser-output tr+tr>.navbox-image,
html.skin-theme-clientpref-night .mw-parser-output tr+tr>.navbox-list {
border-top:2px solid #111111
}
}
@media screen and (prefers-color-scheme:dark) {
html.skin-theme-clientpref-os .mw-parser-output th.navbox-title {
background-color:#345
}
html.skin-theme-clientpref-os .mw-parser-output th.navbox-group {
background-color:#567
}
html.skin-theme-clientpref-os .mw-parser-output td.navbox-abovebelow,
html.skin-theme-clientpref-os .mw-parser-output th.navbox-group,
html.skin-theme-clientpref-os .mw-parser-output td.navbox-subgroup td.navbox-title {
background-color:#456
}
html.skin-theme-clientpref-os .mw-parser-output td.navbox-even {
background-color:#000
}
html.skin-theme-clientpref-os .mw-parser-output td.navbox-odd {
background-color:#123
}
html.skin-theme-clientpref-os .mw-parser-output .navbox,
html.skin-theme-clientpref-os .mw-parser-output .navbox-subgroup,
html.skin-theme-clientpref-os .mw-parser-output .navbox-list {
background-color:#111111
}
html.skin-theme-clientpref-os .mw-parser-output tr+tr>.navbox-abovebelow,
html.skin-theme-clientpref-os .mw-parser-output tr+tr>.navbox-group,
html.skin-theme-clientpref-os .mw-parser-output tr+tr>.navbox-image,
html.skin-theme-clientpref-os .mw-parser-output tr+tr>.navbox-list {
border-top:2px solid #111111
}
}
/* === End of Navbox styles === */

@media screen {
kbd.key {
background-color: var(--background-color-neutral-subtle,#f8f9fa);
color: var(--color-emphasized,#101418);
border: 2.5px outset var(--border-color-muted,#dadde3);
border-radius: 2px;
padding: 1px 4px;
}
}

.nowrap {
white-space: nowrap;
}

MediaWiki:Common.css

2025-09-10T21:00:39Z

Felipe: add key styles

Tick

2025-09-10T20:51:22Z

Felipe: use keys template

{{stub}}

A '''tick''' refers to one step of the game's logic simulation.

Most [[component|components]] take one tick to update the state of their output after their input changes state. Thus, on some ticks, the state of a component's outputs will be "wrong" compared to the state of its inputs.
{{Todo|Add more general information about timing}}[[File:And gate activation delay.png|thumb|A demonstration of two AND gates being activated. The top AND gate has both its inputs active, but its output is not yet active because a delay of 1 tick has not yet passed. The bottom AND gate has had both its inputs active for at least 1 tick, and its output is therefore active.]]

[[File:XOR gate activation delay.png|thumb|A demonstration of two XOR gates being activated. The top XOR gate has one of its inputs active, but its output is not yet active because a delay of 1 tick has not yet passed. The bottom XOR gate has had one of its inputs active for at least 1 tick, and its output is therefore active.]]

== Simulation Speed ==
While every components state is calculated and updated at each tick, the number of ticks that occur in a second can be adjusted from as low as 1 tick per second (tps) all the way up to 10,000 tps.

Adjustments can be made by opening up the simulation controls menu. By default, this is the {{keys|F9}} button.

Additionally, the simulation can be paused entirely, and stepped 1 tick at a time from the control menu. Useful for debugging circuits that don't behave like you'd expect.

You can also pause/resume the simulation or step the simulation using hotkeys on your keyboard.

By default, this is {{keys|F10}} to pause/resume the simulation, and {{keys|shift+F10}} to step the simulation when paused.
{{Todo|Add screenshots of the simulation controls menu}}

Template:Keys

2025-09-10T20:49:51Z

Felipe: Created page with "<includeonly>{{#invoke: keys | keys }}</includeonly>"

<includeonly>{{#invoke: keys | keys }}</includeonly>

Module:Keys/Symbols

2025-09-10T20:48:48Z

Felipe: Created page with "-- taken from https://minecraft.wiki/w/Module:Keys/Symbols return { ['caps lock'] = '⮸ Caps Lock', ['control'] = 'Ctrl', ['shift'] = '⇧ Shift', ['lshift'] = '⇧ Left Shift', ['rshift'] = '⇧ Right Shift', ['enter'] = '↵ Enter', ['return'] = '↵ Return', ['cmd'] = '⌘ Cmd', ['command'] = '⌘ Command', ['opt'] = '⌥ Opt', ['option'] = '⌥ Option', ['tab'] = 'Tab ↹', ['backspace'] = '← Backspace', ['win'] = '⊞ Win', ['super'] = '⊞ Super'..."

-- taken from https://minecraft.wiki/w/Module:Keys/Symbols

return {
['caps lock'] = '⮸ Caps Lock',
['control'] = 'Ctrl',
['shift'] = '⇧ Shift',
['lshift'] = '⇧ Left Shift',
['rshift'] = '⇧ Right Shift',
['enter'] = '↵ Enter',
['return'] = '↵ Return',
['cmd'] = '⌘ Cmd',
['command'] = '⌘ Command',
['opt'] = '⌥ Opt',
['option'] = '⌥ Option',
['tab'] = 'Tab ↹',
['backspace'] = '← Backspace',
['win'] = '⊞ Win',
['super'] = '⊞ Super',
['menu'] = '≣ Menu',
['windows'] = '⊞ Windows',
['up'] = '↑',
['down'] = '↓',
['left'] = '←',
['right'] = '→',
['page up'] = '⇞ Page Up',
['page down'] = '⇟ Page Down',

-- Left & right analog sticks
['l-up'] = 'L↑',
['l up'] = 'L↑',
['l-down'] = 'L↓',
['l down'] = 'L↓',
['l-left'] = 'L←',
['l left'] = 'L←',
['l-right'] = 'L→',
['l right'] = 'L→',
['l-ne'] = 'L↗',
['l ne'] = 'L↗',
['l-se'] = 'L↘',
['l se'] = 'L↘',
['l-nw'] = 'L↖',
['l nw'] = 'L↖',
['l-sw'] = 'L↙',
['l sw'] = 'L↙',

['r-up'] = 'R↑',
['r up'] = 'R↑',
['r-down'] = 'R↓',
['r down'] = 'R↓',
['r-left'] = 'R←',
['r left'] = 'R←',
['r-right'] = 'R→',
['r right'] = 'R→',
['r-ne'] = 'R↗',
['r ne'] = 'R↗',
['r-se'] = 'R↘',
['r se'] = 'R↘',
['r-nw'] = 'R↖',
['r nw'] = 'R↖',
['r-sw'] = 'R↙',
['r sw'] = 'R↙',

-- PlayStation
['ps x'] = '×',
['ex'] = '×',
['ps c'] = '○',
['circle'] = '○',
['ps s'] = '□',
['square'] = '□',
['ps t'] = '△',
['triangle'] = '△',

-- Nintendo 64 & GameCube
['c-up'] = 'C↑',
['c up'] = 'C↑',
['c-down'] = 'C↓',
['c down'] = 'C↓',
['c-left'] = 'C←',
['c left'] = 'C←',
['c-right'] = 'C→',
['c right'] = 'C→',
['c-ne'] = 'C↗',
['c ne'] = 'C↗',
['c-se'] = 'C↘',
['c se'] = 'C↘',
['c-nw'] = 'C↖',
['c nw'] = 'C↖',
['c-sw'] = 'C↙',
['c sw'] = 'C↙',

-- Xbox Controller
['xb-a'] = 'Ⓐ',
['xb-b'] = 'Ⓑ',
['xb-x'] = 'Ⓧ',
['xb-y'] = 'Ⓨ',
['xb-lb'] = '╼',
['xb-rb'] = '╾',
['xb-lt'] = '⟅',
['xb-rt'] = '⟆',
['xb-back'] = '◀',
['xb-start'] = '▶'
}

Module:Keys

2025-09-10T20:48:22Z

Felipe: Created page with "-- taken from https://minecraft.wiki/w/Module:Keys local p = {} p.keys = function( f ) local args = f if f == mw.getCurrentFrame() then args = f:getParent().args end local keys = {} for _, key in ipairs( args ) do key = mw.text.trim( key ) if key ~= '+' and key:find( '%+' ) then local comboKeys = {} for comboKey in mw.text.gsplit( key, '%s*%+%s*' ) do table.insert( comboKeys, p.key( comboKey ) ) end table.insert( keys, table.concat( comboKey..."

-- taken from https://minecraft.wiki/w/Module:Keys

local p = {}
p.keys = function( f )
local args = f
if f == mw.getCurrentFrame() then
args = f:getParent().args
end
local keys = {}

for _, key in ipairs( args ) do
key = mw.text.trim( key )
if key ~= '+' and key:find( '%+' ) then
local comboKeys = {}
for comboKey in mw.text.gsplit( key, '%s*%+%s*' ) do
table.insert( comboKeys, p.key( comboKey ) )
end
table.insert( keys, table.concat( comboKeys, ' + ' ) )
else
table.insert( keys, p.key( key ) )
end
end

return table.concat( keys )
end

p.key = function( key )
if key == '' then
return ''
end

local symbols = mw.loadData( 'Module:Keys/Symbols' )
return '<kbd class="key nowrap">' .. ( symbols[key:lower()] or key ) .. '</kbd>'
end
return p

Buffer

2025-09-10T10:07:48Z

Felipe: add fast buffer on see also section

{{Infobox component
| title = Buffer
| id = MHG.BufferWithOutput
| caption = Buffer
| configurable = 0
| io.minInputs = 1
| io.maxInputs = 1
| io.outputs = 1
| io.propagationDelay = 1
}}

The '''Buffer''' is a [[component]] used for [[digital logic]]. It has one input and one output, and the output is updated to propagate the same state of the input. Buffers are useful for preventing back-propagation of signals, because signals can only propagate from the input to the output, not in the other direction.

== Behavior ==
The Buffer simply passes on the state of its input to its output.

{{Truth table auto
| inputs=1
| outputs=1
| caption=Buffer Truth Table
| expr1=a
}}

The Buffer takes one [[tick]] to update the state of its output after a change to the state of its input.

== Placement ==

The Buffer can be placed in the center of a [[Circuit Board]] square or on top of a [[Mount]], and can be fine-rotated.

{{todo|image of different ways Buffer can be placed}}

== See also ==

* [[Fast Buffer]]

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Circuitry components]]

Delayer

2025-09-10T10:06:44Z

Felipe: fix typo

{{Infobox component
| title = Delayer
| id = MHG.Delayer
| caption = Delayer set to 10 ticks of delay
| configurable = 1
| io.minInputs = 1
| io.maxInputs = 1
| io.outputs = 1
}}

The '''Delayer''' is a [[component]] used for [[digital logic]]. It propagates signals from its input to its output, similar to a [[Buffer]], but the signal takes more time to propagate. The signal is ''delayed'', if you will.

Delayers are useful for building [[clock]] circuits.

== Behavior ==

The output of a Delayer will change to reflect the state of the input, as long as the input remains stable at that state for the configured delay length.

{{Truth table
| inputs=Input
| outputs=Output (eventually)
| caption=Fast Buffer Truth Table
| 0 0
| 1 1
}}

{{todo|add more details about the tick-by-tick behavior when the input changes state faster than the delay length}}

== Configurability ==

The length of the delay can be configured by [[editing]] the component. The default delay is 10 ticks, the minimum is 2 ticks and the maximum is 30 ticks.

== Placement ==

The Delayer can be placed in the center of a [[Circuit Board]] square or on top of a [[Mount]], and can be fine-rotated.

== Tips ==

* If you need to delay for longer than 30 ticks, you can chain multiple Delayers together.
* If you need to delay for only 1 tick, you can use a [[Buffer]] instead.

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Circuitry components]]

Template:Truth table auto

2025-09-09T19:00:33Z

Felipe:

<noinclude>
<templatedata>
{
"params": {
"caption": {
"description": "Title to show above the table",
"type": "line"
},
"inputs": {
"description": "Number of inputs or list of input names",
"example": "\"3\", \"A B C\"",
"type": "line",
"required": true
},
"outputs": {
"description": "Number of outputs or list of output names",
"example": "\"2\", \"X Y\"",
"type": "line",
"required": true
},
"expr1": {
"description": "Expression for output #1",
"example": "(a & b) + c ^ d",
"type": "line"
},
"expr2": {
"description": "Expression for output #2",
"example": "(a & b) + c ^ d",
"type": "line"
},
"expr3": {
"description": "Expression for output #3",
"example": "(a & b) + c ^ d",
"type": "line"
},
"expr4": {
"description": "Expression for output #4",
"example": "(a & b) + c ^ d",
"type": "line"
},
"expr5": {
"description": "Expression for output #5",
"example": "(a & b) + c ^ d",
"type": "line"
},
"expr6": {
"description": "Expression for output #6",
"example": "(a & b) + c ^ d",
"type": "line"
}
},
"description": "Renders a truth table with any number of inputs and outputs.\n\nIMPORTANT: Make sure to use \"+\" instead of \"|\" as the OR operator. Wikitest parses the \"|\" as a property separator unless you instead use \"{{!}}\", but the plus sign is better for readability.",
"paramOrder": [
"caption",
"inputs",
"outputs",
"expr1",
"expr2",
"expr3",
"expr4",
"expr5",
"expr6"
],
"format": "block"
}
</templatedata>
</noinclude><includeonly>{{#invoke:LogicUtils|truth_table_auto}}</includeonly>

Template:Truth table auto

2025-09-09T18:59:16Z

Felipe:

<noinclude>
<templatedata>
{
"params": {
"caption": {
"description": "Title to show above the table",
"type": "line"
},
"inputs": {
"description": "Number of inputs or list of input names",
"example": "\"3\", \"A B C\"",
"type": "line",
"required": true
},
"outputs": {
"description": "Number of outputs or list of output names",
"example": "\"2\", \"X Y\"",
"type": "line",
"required": true
},
"expr1": {
"description": "Expression for output #1",
"example": "(a & b) + c ^ d",
"type": "line"
},
"expr2": {
"description": "Expression for output #2",
"example": "(a & b) + c ^ d",
"type": "line"
},
"expr3": {
"description": "Expression for output #3",
"example": "(a & b) + c ^ d",
"type": "line"
},
"expr4": {
"description": "Expression for output #4",
"example": "(a & b) + c ^ d",
"type": "line"
},
"expr5": {
"description": "Expression for output #5",
"example": "(a & b) + c ^ d",
"type": "line"
},
"expr6": {
"description": "Expression for output #6",
"example": "(a & b) + c ^ d",
"type": "line"
}
},
"description": "Renders a truth table with any number of inputs and outputs",
"paramOrder": [
"caption",
"inputs",
"outputs",
"expr1",
"expr2",
"expr3",
"expr4",
"expr5",
"expr6"
],
"format": "block"
}
</templatedata>
</noinclude><includeonly>{{#invoke:LogicUtils|truth_table_auto}}</includeonly>

User:Felipe/sandbox

2025-09-09T18:58:22Z

Felipe:

{{Binary signal
| signals=Input A, Input B, Output
| signal1=0111?0011100011100011100011100011100011100011100011100
| signal2=00?100001100001100001100001100001100001100001100001100
| signal3=0001100??110000110000110000110000110000110000110000110
}}

{{Truth table auto
| inputs=3
| outputs=1
| expr1=a + b + c
}}

Module:LogicUtils

2025-09-09T18:57:45Z

Felipe: support math style binary operators

local p = {}

local bit32 = require( 'bit32' )

function parse_io(kind, row, str)
local count = tonumber(str)
local names = {}

if count == nil then
-- str is a list of IO names
names = mw.text.split(str, ",")
else
-- str is a number
if count == 1 then
names[1] = kind
else
for i=1,count do
names[i] = string.format("%s %i", kind, i)
end
end
end

for i, v in ipairs(names) do
row:tag('th')
:wikitext(v)
end

return #names
end

local function isBinOp(c)
return c == "&" or c == "|" or c == "^" or c == "+" or c == "*"
end

local function letterToCell(c)
return c:lower():byte() - 96
end

local function eval(expr, values)
local stack = {}

for _, c in pairs(expr) do
if isBinOp(c) then
local v = table.remove(stack)
if v == nil then error("Invalid expression: missing operand") end
local v2 = table.remove(stack)
if v2 == nil then error("Invalid expression: missing operand") end

if c == "&" or c == "*" then
table.insert(stack, v and v2)
elseif c == "|" or c == "+" then
table.insert(stack, v or v2)
elseif c == "^" then
table.insert(stack, v ~= v2)
end
elseif c == "!" then
local v = table.remove(stack)
if v == nil then error("Invalid expression: missing operand after '!'") end
table.insert(stack, not v)
else
local index = letterToCell(c) -- 'a' = 1, 'b' = 2, etc.
if index then
if values[index] == nil and not ignoreMissing then error("Value for variable '" .. c .. "' not provided") end

table.insert(stack, values[index] or false)
else
error("Invalid character in expression: " .. c)
end
end
end

return stack[1]
end

local function evalAll(expr, num_vars, callback)
local totalCombinations = 2 ^ num_vars

for i = 0, totalCombinations - 1 do
local values = {}
for j = 1, num_vars do
values[j] = bit32.band(i, bit32.lshift(1, num_vars - j)) ~= 0
end

local result = eval(expr, values)
callback(values, result)
end
end

local function algebraicToRPN(input)
local output = {}
local opstack = {}

input:gsub("[^%s]", function(c)
if isBinOp(c) then
while opstack[#opstack] == "!" do
table.insert(output, table.remove(opstack))
end

table.insert(opstack, c)
elseif c == "!" or c == "(" then
table.insert(opstack, c)
elseif c == ")" then
while #opstack > 0 do
local op = table.remove(opstack)
if op == "(" then
break
end
table.insert(output, op)
end
else
table.insert(output, c)
end
end)

-- Drain the operator stack to the output
while #opstack > 0 do table.insert(output, table.remove(opstack)) end

return output
end

local function renderCell(row, value)
local style = "color:white; text-align:center;"
if value == false or value == "0" then
row:tag('td')
:attr('style', 'background-color:#1f1e1e;'..style)
:wikitext("0")
elseif value == true or value == "1" then
row:tag('td')
:attr('style', 'background-color:#fd140f;'..style)
:wikitext("1")
else
row:tag('td')
:cssText("text-align:center")
:wikitext(value)
end
end

p.truth_table = function(frame, args)
local args = args or frame:getParent().args

local tbl = mw.html.create('table')
:addClass('wikitable')

if args.caption ~= nil then
tbl:tag('caption')
:wikitext(args.caption)
end

local header = tbl:tag('tr')
local nInputs = parse_io("Input", header, args.inputs)
local nOutputs = parse_io("Output", header, args.outputs)

local i = 1
while args[i] ~= nil do
local row = tbl:tag('tr')

for token in string.gmatch(args[i], "[^%s]+") do
renderCell(row, token)
end

i = i + 1
end

return tostring(tbl)
end

p.truth_table_auto = function(frame, args)
local args = args or frame:getParent().args

local tbl = mw.html.create('table')
:addClass('wikitable')

if args.caption ~= nil then
tbl:tag('caption')
:wikitext(args.caption)
end

local header = tbl:tag('tr')
local nInputs = parse_io("Input", header, args.inputs)
local nOutputs = parse_io("Output", header, args.outputs)

local exprs = {}
for i = 1,nOutputs do
local exprStr = args["expr"..i]
if exprStr == nil then error("Missing expression for output " .. i) end
table.insert(exprs, algebraicToRPN(exprStr))
end

local totalCombinations = 2 ^ nInputs
local values = {}

for i = 0,totalCombinations - 1 do
local row = tbl:tag('tr')

for j = 1, nInputs do
values[j] = bit32.band(i, bit32.lshift(1, nInputs - j)) ~= 0
renderCell(row, values[j])
end

for _, expr in pairs(exprs) do
renderCell(row, eval(expr, values))
end
end

return tostring(tbl)
end

local function renderBinaryGraphHeader(tbl, tickCount)
local row = tbl:tag('tr')
row:tag('td')
row:tag('td')

for i = 0, tickCount do
row:tag('td')
:addClass('signal-header-cell')
:wikitext(tostring(i))
end
end

local function renderBinaryGraphSpacerRow(tbl, tickCount)
local row = tbl:tag('tr')
:addClass("signal-spacer-row")
row:tag('td')
row:tag('td')

for i = 1, tickCount do
row:tag('td')
:addClass('signal-spacer-row-cell')
end
end

local function renderBinaryGraphSignalRow(tbl, signal)
local row = tbl:tag('tr')
:addClass("signal-row")
row:tag("td")
:wikitext(signal.name)

row:tag("td")
:addClass("signal-spacer")

local prevValue = nil
for _, v in pairs(signal.values) do
if v == "nil" then v = nil end

local cell = row:tag("td")
:addClass("signal-value-cell")

if v == 1 then
cell:addClass("signal-on-top")
elseif v == 0 then
cell:addClass("signal-on-bottom")
end

if prevValue ~= nil and v ~= nil and v ~= prevValue then
cell:addClass("signal-on-left")
end

prevValue = v
end
end

local function renderBinaryGraph(parent, signals)
local tickCount = #signals[1].values

local tbl = parent:tag('table')

renderBinaryGraphHeader(tbl, tickCount)

renderBinaryGraphSpacerRow(tbl, tickCount)
for _, signal in pairs(signals) do
renderBinaryGraphSignalRow(tbl, signal)
renderBinaryGraphSpacerRow(tbl, tickCount)
end
end

p.binary_signal_graph = function(frame, args)
local args = args or frame:getParent().args

local signalNames = mw.text.split(args.signals, ",")
local signals = {}

local container = mw.html.create('div')
:addClass('signal-graph-table')

for i = 1,#signalNames do
local str = args["signal"..i]
local values = {}

for token in string.gmatch(str, "[01?]") do
if token == "?" then
table.insert(values, "nil") -- lua tables can't store nil
else
table.insert(values, tonumber(token))
end
end

table.insert(signals, { name = mw.text.trim(signalNames[i]), values = values })
end

renderBinaryGraph(container, signals)

return tostring(container)
end

return p

User:Felipe/sandbox

2025-09-09T18:52:49Z

Felipe:

Module:LogicUtils

2025-09-09T18:51:25Z

Felipe: properly support multiple outputs

local p = {}

local bit32 = require( 'bit32' )

function parse_io(kind, row, str)
local count = tonumber(str)
local names = {}

if count == nil then
-- str is a list of IO names
names = mw.text.split(str, ",")
else
-- str is a number
if count == 1 then
names[1] = kind
else
for i=1,count do
names[i] = string.format("%s %i", kind, i)
end
end
end

for i, v in ipairs(names) do
row:tag('th')
:wikitext(v)
end

return #names
end

local function isBinOp(c)
return c == "&" or c == "|" or c == "^"
end

local function letterToCell(c)
return c:lower():byte() - 96
end

local function eval(expr, values)
local stack = {}

for _, c in pairs(expr) do
if isBinOp(c) then
local v = table.remove(stack)
if v == nil then error("Invalid expression: missing operand") end
local v2 = table.remove(stack)
if v2 == nil then error("Invalid expression: missing operand") end

if c == "&" then
table.insert(stack, v and v2)
elseif c == "|" then
table.insert(stack, v or v2)
elseif c == "^" then
table.insert(stack, v ~= v2)
end
elseif c == "!" then
local v = table.remove(stack)
if v == nil then error("Invalid expression: missing operand after '!'") end
table.insert(stack, not v)
else
local index = letterToCell(c) -- 'a' = 1, 'b' = 2, etc.
if index then
if values[index] == nil and not ignoreMissing then error("Value for variable '" .. c .. "' not provided") end

table.insert(stack, values[index] or false)
else
error("Invalid character in expression: " .. c)
end
end
end

return stack[1]
end

local function evalAll(expr, num_vars, callback)
local totalCombinations = 2 ^ num_vars

for i = 0, totalCombinations - 1 do
local values = {}
for j = 1, num_vars do
values[j] = bit32.band(i, bit32.lshift(1, num_vars - j)) ~= 0
end

local result = eval(expr, values)
callback(values, result)
end
end

local function algebraicToRPN(input)
local output = {}
local opstack = {}

input:gsub("[^%s]", function(c)
if isBinOp(c) then
while opstack[#opstack] == "!" do
table.insert(output, table.remove(opstack))
end

table.insert(opstack, c)
elseif c == "!" or c == "(" then
table.insert(opstack, c)
elseif c == ")" then
while #opstack > 0 do
local op = table.remove(opstack)
if op == "(" then
break
end
table.insert(output, op)
end
else
table.insert(output, c)
end
end)

-- Drain the operator stack to the output
while #opstack > 0 do table.insert(output, table.remove(opstack)) end

return output
end

local function renderCell(row, value)
local style = "color:white; text-align:center;"
if value == false or value == "0" then
row:tag('td')
:attr('style', 'background-color:#1f1e1e;'..style)
:wikitext("0")
elseif value == true or value == "1" then
row:tag('td')
:attr('style', 'background-color:#fd140f;'..style)
:wikitext("1")
else
row:tag('td')
:cssText("text-align:center")
:wikitext(value)
end
end

p.truth_table = function(frame, args)
local args = args or frame:getParent().args

local tbl = mw.html.create('table')
:addClass('wikitable')

if args.caption ~= nil then
tbl:tag('caption')
:wikitext(args.caption)
end

local header = tbl:tag('tr')
local nInputs = parse_io("Input", header, args.inputs)
local nOutputs = parse_io("Output", header, args.outputs)

local i = 1
while args[i] ~= nil do
local row = tbl:tag('tr')

for token in string.gmatch(args[i], "[^%s]+") do
renderCell(row, token)
end

i = i + 1
end

return tostring(tbl)
end

p.truth_table_auto = function(frame, args)
local args = args or frame:getParent().args

local tbl = mw.html.create('table')
:addClass('wikitable')

if args.caption ~= nil then
tbl:tag('caption')
:wikitext(args.caption)
end

local header = tbl:tag('tr')
local nInputs = parse_io("Input", header, args.inputs)
local nOutputs = parse_io("Output", header, args.outputs)

local exprs = {}
for i = 1,nOutputs do
local exprStr = args["expr"..i]
if exprStr == nil then error("Missing expression for output " .. i) end
table.insert(exprs, algebraicToRPN(exprStr))
end

local totalCombinations = 2 ^ nInputs
local values = {}

for i = 0,totalCombinations - 1 do
local row = tbl:tag('tr')

for j = 1, nInputs do
values[j] = bit32.band(i, bit32.lshift(1, nInputs - j)) ~= 0
renderCell(row, values[j])
end

for _, expr in pairs(exprs) do
renderCell(row, eval(expr, values))
end
end

return tostring(tbl)
end

local function renderBinaryGraphHeader(tbl, tickCount)
local row = tbl:tag('tr')
row:tag('td')
row:tag('td')

for i = 0, tickCount do
row:tag('td')
:addClass('signal-header-cell')
:wikitext(tostring(i))
end
end

local function renderBinaryGraphSpacerRow(tbl, tickCount)
local row = tbl:tag('tr')
:addClass("signal-spacer-row")
row:tag('td')
row:tag('td')

for i = 1, tickCount do
row:tag('td')
:addClass('signal-spacer-row-cell')
end
end

local function renderBinaryGraphSignalRow(tbl, signal)
local row = tbl:tag('tr')
:addClass("signal-row")
row:tag("td")
:wikitext(signal.name)

row:tag("td")
:addClass("signal-spacer")

mw.log(mw.dumpObject(signal))

local prevValue = nil
for _, v in pairs(signal.values) do
if v == "nil" then v = nil end

local cell = row:tag("td")
:addClass("signal-value-cell")

if v == 1 then
cell:addClass("signal-on-top")
elseif v == 0 then
cell:addClass("signal-on-bottom")
end

if prevValue ~= nil and v ~= nil and v ~= prevValue then
cell:addClass("signal-on-left")
end

prevValue = v
end
end

local function renderBinaryGraph(parent, signals)
local tickCount = #signals[1].values

local tbl = parent:tag('table')

renderBinaryGraphHeader(tbl, tickCount)

renderBinaryGraphSpacerRow(tbl, tickCount)
for _, signal in pairs(signals) do
renderBinaryGraphSignalRow(tbl, signal)
renderBinaryGraphSpacerRow(tbl, tickCount)
end
end

p.binary_signal_graph = function(frame, args)
local args = args or frame:getParent().args

local signalNames = mw.text.split(args.signals, ",")
local signals = {}

local container = mw.html.create('div')
:addClass('signal-graph-table')

for i = 1,#signalNames do
local str = args["signal"..i]
local values = {}

for token in string.gmatch(str, "[01?]") do
if token == "?" then
table.insert(values, "nil") -- lua tables can't store nil
else
table.insert(values, tonumber(token))
end
end

table.insert(signals, { name = mw.text.trim(signalNames[i]), values = values })
end

renderBinaryGraph(container, signals)

return tostring(container)
end

return p

User:Felipe/sandbox

2025-09-09T18:41:18Z

Felipe:

Talk:Decoder

2025-09-09T18:40:06Z

Felipe: /* Spacing */ Reply

== Spacing ==

I'm not a fan of the spacing after the Behavior section, it doesn't look great on mobile. Is there another way of doing it? [[User:Felipe|Felipe]] ([[User talk:Felipe|talk]]) 18:23, 9 September 2025 (UTC)

:i changed it, hopefully it's better [[User:DjSapsan|DjSapsan]] ([[User talk:DjSapsan|talk]]) 18:38, 9 September 2025 (UTC)
::Yup, looks good on mobile now [[User:Felipe|Felipe]] ([[User talk:Felipe|talk]]) 18:40, 9 September 2025 (UTC)

Talk:Decoder

2025-09-09T18:23:12Z

Felipe: /* Spacing */ new section

Decoder

2025-09-09T18:21:36Z

Felipe: improve "see also" formatting

; '''Decoder'''
: In ''Logic World'', a '''Decoder''' is a circuit that takes a binary input and activates one specific output bit corresponding to that input value.
: It is commonly used to select one element out of many, for example a cell in memory.
: See also [[Encoder]], which performs the reverse operation.
:[[File:4bit-decoder.png|thumb|right|4-bit decoder. Input on the left is 1110. The 14th output bit on the right is activated.]]

== Behavior ==

The Decoder's output is always a single bit that corresponds to the input value, effectively translating a binary value into a [[wikipedia:Unary_numeral_system|unary]] value.

== Construction ==

A Decoder is one of the simplest circuits to build.
First, determine how many bits you need.
The number of output bits from input bits is given by:

:<math>o = 2^i</math>

And vice versa:

:<math>i = \log_2(o)</math>

So, if you want 256 outputs, you will need a decoder with 8 input bits.
Each output has a specific pattern of {{on}} and {{off}} bits coming from the input. Here are the steps to build it:

* Place a row of input items.
* Connect each input bit to a NOT gate to get its inverted value. And add a Buffer to pass the non-inverted value and match the delay with the NOT gate.
* Place a row of NOT gates to serve as the outputs.
* Go through each output NOT gate and connect them to the corresponding inputs (normal or inverted) to match its binary value. For example, the output corresponding to number 12 (binary 1100) should receive the following binary values:
** 1st bit – normal
** 2nd bit – normal
** 3rd bit – inverted
** 4th bit – inverted
:and so on for each value.

You can design a decoder in different ways. If you are building one for the first time, you may want to explicitly place each wire and gate to match the real electronic analog or to be visually understandable.

When you become more experienced, you can skip unnecessary details and make it as simple as the screenshot above demonstrates. This design, optimized for speed and size, uses the trick of connecting wires from '''output''' pins directly to the required items, avoiding additional buffers and wire routing. In the screenshot below you can see the side view how to make it compact.

[[File:Decoder-side.png|thumb|center|alt=Side view of the decoder|Side view of the decoder]]

== Speed ==

The compact design above computes the output in 2 ticks.

== See also ==
* [[Encoder]]
* [[Lookup Table]]

Component

2025-09-09T11:47:49Z

Felipe: add components category in see also section

{{stub}}

'''Components''' are the items used to build things in Logic World.

== See also ==

* [[:Category:Components]]

Circuit

2025-09-09T11:46:39Z

Felipe: use singular link

{{stub}}

A '''circuit''' is a collection of multiple [[component]]s and wires. There are many kinds of useful circuits, which this page will tell you about once it's been edited a bunch more.

Logic World

2025-09-09T11:46:22Z

Felipe: use singular link

{{Stub}}
[[File:Logic World Steam banner.jpg|thumb|Logic World]]
'''Logic World''' is a first-person sandbox simulation video game developed by [[Mouse Hat Games]] for Linux, MacOS, and Windows. The game enables players to build [[digital logic]] machines out of various [[component]]s. Logic World can be played in singleplayer or [[multiplayer]].

Category:Miscellaneous components

2025-09-09T08:04:44Z

Felipe: add to the components category

Category for components that don't fit into the other categories.

[[Category:Components]]

Template:Truth table auto

2025-09-08T22:56:08Z

Felipe: fix empty space above table

<noinclude>
<templatedata>
{
"params": {
"caption": {
"description": "Title to show above the table",
"type": "line"
},
"inputs": {
"description": "Number of inputs or list of input names",
"example": "\"3\", \"A B C\"",
"type": "line",
"required": true
},
"outputs": {
"description": "Number of outputs or list of output names",
"example": "\"2\", \"X Y\"",
"type": "line",
"required": true
},
"expr1": {
"description": "Expression for output #1",
"example": "(a & b) | c ^ d",
"type": "line"
},
"expr2": {
"description": "Expression for output #2",
"example": "(a & b) | c ^ d",
"type": "line"
},
"expr3": {
"description": "Expression for output #3",
"example": "(a & b) | c ^ d",
"type": "line"
},
"expr4": {
"description": "Expression for output #4",
"example": "(a & b) | c ^ d",
"type": "line"
},
"expr5": {
"description": "Expression for output #5",
"example": "(a & b) | c ^ d",
"type": "line"
},
"expr6": {
"description": "Expression for output #6",
"example": "(a & b) | c ^ d",
"type": "line"
}
},
"description": "Renders a truth table with any number of inputs and outputs",
"paramOrder": [
"caption",
"inputs",
"outputs",
"expr1",
"expr2",
"expr3",
"expr4",
"expr5",
"expr6"
],
"format": "block"
}
</templatedata>
</noinclude><includeonly>{{#invoke:LogicUtils|truth_table_auto}}</includeonly>

Template:Navbox

2025-09-08T22:54:29Z

Felipe: add "navigation" header

== Navigation ==

{{#invoke:Navbox|navbox}}

Oracle

2025-09-08T22:08:06Z

Felipe: use on and off templates

{{Infobox component
| title=Oracle
| caption=Oracle
| id=MHG.Randomizer
| io.propagationDelay=1
| io.maxInputs=1
| io.minInputs=1
| io.outputs=1
}}
The Oracle is a digital component which will output a random state ({{on}} or {{off}}) on the rising edge of the input.

The Oracle will demonstrate the following behavior:
{{Truth table
| inputs=Enable
| outputs=1
| caption=Oracle Truth Table
| 0 0
| 1 1/0
}}

== Timing ==
The Oracle has a latency of 1 tick, so in the instance of the enable pin goes {{on}}, the output will be in a random state of either {{off}} or {{on}}. The same is for when the enable pin goes {{off}}, the output will be set to {{off}} one tick later.

== Configurability ==
This component cannot be configured in the edit menu.

[[Category:Vanilla components]]
[[Category:Circuitry components]]

2025-09-08T16:57:17Z

Felipe: Created page with "{{Binary signal | signals=Input A, Input B, Output | signal1=011100 | signal2=001100 | signal3=000110 }}"

{{Binary signal
| signals=Input A, Input B, Output
| signal1=011100
| signal2=001100
| signal3=000110
}}

MediaWiki:Common.css

2025-09-08T16:55:57Z

Felipe:

Template:Binary signal/styles.css

2025-09-08T16:55:30Z

Felipe: Undo revision 478 by Felipe (talk)

.signal-graph-table {
border-collapse: collapse;
}

.signal-graph-table td.signal-header-cell {
text-align: center;
transform: translateX(-50%);
}

.signal-graph-table tr.signal-spacer-row {
height: 1rem;
border: none;
}
.signal-graph-table tr.signal-spacer-row td.signal-spacer-row-cell {
border-left: var(--tick-marker-border);
border-right: var(--tick-marker-border);
}

.signal-graph-table tr.signal-row {
height: 2rem;
}
.signal-graph-table tr.signal-row td:first-of-type {
width: auto;
padding: 0 0.5rem;
font-weight: bold;
}
.signal-graph-table tr.signal-row td.signal-spacer {
border: none;
width: .5rem;
}

.signal-graph-table td.signal-value-cell {
width: 3rem;
text-align: center;
}
.signal-graph-table td.signal-value-cell.signal-on-top {
border-top: var(--signal-border);
}
.signal-graph-table td.signal-value-cell.signal-on-bottom {
border-bottom: var(--signal-border);
}
.signal-graph-table td.signal-value-cell.signal-on-left {
border-left: var(--signal-border);
}

.signal-graph-table td.signal-value-cell {
border-right: var(--tick-marker-border);
}
.signal-graph-table td.signal-value-cell:not(.signal-on-left) {
border-left: var(--tick-marker-border);
}

Template:Binary signal/styles.css

2025-09-08T16:51:02Z

Felipe: use border color for tick markers

.signal-graph-table {
border-collapse: collapse;
}

.signal-graph-table td.signal-header-cell {
text-align: center;
transform: translateX(-50%);
}

.signal-graph-table tr.signal-spacer-row {
height: 1rem;
border: none;
}
.signal-graph-table tr.signal-spacer-row td.signal-spacer-row-cell {
border-left: var(--border-color-base);
border-right: var(--border-color-base);
}

.signal-graph-table tr.signal-row {
height: 2rem;
}
.signal-graph-table tr.signal-row td:first-of-type {
width: auto;
padding: 0 0.5rem;
font-weight: bold;
}
.signal-graph-table tr.signal-row td.signal-spacer {
border: none;
width: .5rem;
}

.signal-graph-table td.signal-value-cell {
width: 3rem;
text-align: center;
}
.signal-graph-table td.signal-value-cell.signal-on-top {
border-top: var(--signal-border);
}
.signal-graph-table td.signal-value-cell.signal-on-bottom {
border-bottom: var(--signal-border);
}
.signal-graph-table td.signal-value-cell.signal-on-left {
border-left: var(--signal-border);
}

.signal-graph-table td.signal-value-cell {
border-right: var(--border-color-base);
}
.signal-graph-table td.signal-value-cell:not(.signal-on-left) {
border-left: var(--border-color-base);
}

Template:Binary signal

2025-09-08T16:49:40Z

Felipe: load styles

<includeonly><templatestyles src="Binary signal/styles.css" />{{#invoke:LogicUtils|binary_signal_graph}}</includeonly>

MediaWiki:Common.css

2025-09-08T16:48:59Z

Felipe: add binary signal graph variables

.lw-infobox {
background-color: var(--background-color-interactive-subtle,#f8f9fa);
color: var(--color-base,#202122);
border: 1px solid var(--border-color-subtle,#c8ccd1);
}

.tabber .wikitable {
margin-top: 0;
}

/* CSS variables for the binary signal graph */
body {
--signal-border: 3px solid rgb(239, 53, 53);
--tick-marker-border: 1px solid rgba(0, 0, 0, 0.59);
}

/* === Navbox styles === */
.mw-parser-output .navbox {
border:1px solid #aaa;
box-sizing:border-box;
width:100%;
margin:auto;
clear:both;
font-size:88%;
text-align:center;
padding:1px
}
.mw-parser-output .navbox-inner,
.mw-parser-output .navbox-subgroup {
width:100%
}
.mw-parser-output .navbox+.navbox-styles+.navbox {
margin-top:-1px
}
.mw-parser-output .navbox th,
.mw-parser-output .navbox-title,
.mw-parser-output .navbox-abovebelow {
text-align:center;
padding-left:1em;
padding-right:1em
}
.mw-parser-output th.navbox-group {
white-space:nowrap;
text-align:right
}
.mw-parser-output .navbox,
.mw-parser-output .navbox-subgroup {
background:#fdfdfd
}
.mw-parser-output .navbox-list {
border-color:#fdfdfd
}
.mw-parser-output .navbox th,
.mw-parser-output .navbox-title {
background:#eaeeff
}
.mw-parser-output .navbox-abovebelow,
.mw-parser-output th.navbox-group,
.mw-parser-output .navbox-subgroup .navbox-title {
background:#ddddff
}
.mw-parser-output .navbox-subgroup .navbox-group,
.mw-parser-output .navbox-subgroup .navbox-abovebelow {
background:#e6e6ff
}
.mw-parser-output .navbox-even {
background:#f7f7f7
}
.mw-parser-output .navbox-odd {
background:transparent
}
.mw-parser-output th.navbox-title1 {
border-left:2px solid #fdfdfd;
width:100%
}
.mw-parser-output td.navbox-list1 {
text-align:left;
border-left-width:2px;
border-left-style:solid
}
.mw-parser-output .navbox .hlist td dl,
.mw-parser-output .navbox .hlist td ol,
.mw-parser-output .navbox .hlist td ul,
.mw-parser-output .navbox td.hlist dl,
.mw-parser-output .navbox td.hlist ol,
.mw-parser-output .navbox td.hlist ul {
padding:0.125em 0
}
.mw-parser-output .navbox .hlist dd,
.mw-parser-output .navbox .hlist dt,
.mw-parser-output .navbox .hlist li {
white-space:nowrap
}
.mw-parser-output .navbox .hlist dd dl,
.mw-parser-output .navbox .hlist dt dl,
.mw-parser-output .navbox .hlist li ol,
.mw-parser-output .navbox .hlist li ul {
white-space:normal
}
.mw-parser-output ol+.navbox-styles+.navbox,
.mw-parser-output ul+.navbox-styles+.navbox {
margin-top:0.5em
}
@media screen {
html.skin-theme-clientpref-night .mw-parser-output th.navbox-title {
background-color:#345
}
html.skin-theme-clientpref-night .mw-parser-output th.navbox-group {
background-color:#567
}
html.skin-theme-clientpref-night .mw-parser-output td.navbox-abovebelow,
html.skin-theme-clientpref-night .mw-parser-output th.navbox-group,
html.skin-theme-clientpref-night .mw-parser-output td.navbox-subgroup td.navbox-title {
background-color:#456
}
html.skin-theme-clientpref-night .mw-parser-output td.navbox-even {
background-color:#000
}
html.skin-theme-clientpref-night .mw-parser-output td.navbox-odd {
background-color:#123
}
html.skin-theme-clientpref-night .mw-parser-output .navbox,
html.skin-theme-clientpref-night .mw-parser-output .navbox-subgroup,
html.skin-theme-clientpref-night .mw-parser-output .navbox-list {
background-color:#111111
}
html.skin-theme-clientpref-night .mw-parser-output tr+tr>.navbox-abovebelow,
html.skin-theme-clientpref-night .mw-parser-output tr+tr>.navbox-group,
html.skin-theme-clientpref-night .mw-parser-output tr+tr>.navbox-image,
html.skin-theme-clientpref-night .mw-parser-output tr+tr>.navbox-list {
border-top:2px solid #111111
}
}
@media screen and (prefers-color-scheme:dark) {
html.skin-theme-clientpref-os .mw-parser-output th.navbox-title {
background-color:#345
}
html.skin-theme-clientpref-os .mw-parser-output th.navbox-group {
background-color:#567
}
html.skin-theme-clientpref-os .mw-parser-output td.navbox-abovebelow,
html.skin-theme-clientpref-os .mw-parser-output th.navbox-group,
html.skin-theme-clientpref-os .mw-parser-output td.navbox-subgroup td.navbox-title {
background-color:#456
}
html.skin-theme-clientpref-os .mw-parser-output td.navbox-even {
background-color:#000
}
html.skin-theme-clientpref-os .mw-parser-output td.navbox-odd {
background-color:#123
}
html.skin-theme-clientpref-os .mw-parser-output .navbox,
html.skin-theme-clientpref-os .mw-parser-output .navbox-subgroup,
html.skin-theme-clientpref-os .mw-parser-output .navbox-list {
background-color:#111111
}
html.skin-theme-clientpref-os .mw-parser-output tr+tr>.navbox-abovebelow,
html.skin-theme-clientpref-os .mw-parser-output tr+tr>.navbox-group,
html.skin-theme-clientpref-os .mw-parser-output tr+tr>.navbox-image,
html.skin-theme-clientpref-os .mw-parser-output tr+tr>.navbox-list {
border-top:2px solid #111111
}
}
/* === End of Navbox styles === */