Logic World Wiki - User contributions [en]

Template:ALU

2025-09-16T20:55:50Z

Jimmy: Remove stub template, whoops, didn't realize this was a template and not an article

; '''Arithmetic logic unit'''
: In ''Logic World'', an '''arithmetic logic unit''' ('''ALU''') is a component of a [[CPU|central processor]] that performs basic arithmetic and logic operations.
: By combining multiple operations, it is possible to perform any computation.

Template:ALU

2025-09-16T01:07:50Z

Jimmy: add stub template

{{stub}}

; '''Arithmetic logic unit'''
: In ''Logic World'', an '''arithmetic logic unit''' ('''ALU''') is a component of a [[CPU|central processor]] that performs basic arithmetic and logic operations.
: By combining multiple operations, it is possible to perform any computation.

Main Page

2025-09-11T20:18:00Z

Jimmy: Fix link after category rename

Welcome to the Logic World Wiki. This wiki is dedicated to anything and everything related to [[Logic World]], a video game where you can invent a new computer!

== Logic World Links ==

* [https://logic.world Logic World home page]
* [https://store.steampowered.com/app/1054340/Logic_World/ Logic World on Steam]
* [https://discord.gg/C5Qkk53 Logic World Discord]

== Wiki articles to check out ==

* [[Component]], the items used to build structures in Logic World
* [[Circuit]], a combination of components with more complex behavior
* [[Building mechanic|Building mechanics]]
* [[Your First Computer]]
* [[Mods:Introduction|Modding introduction]]
* [[Dedicated Server Setup Guide]]

== Stats ==

The wiki has:

* [[Special:AllPages|{{NUMBEROFARTICLES}} articles]]
* [[Special:ListFiles|{{NUMBEROFFILES}} files]]
* [[Special:ListUsers|{{NUMBEROFUSERS}} registered users]]
* [[Special:RecentChanges|{{NUMBEROFEDITS}} total edits]]

Anybody can edit this wiki. For more information, see [[Logic World Wiki:Contributing]].

Building mechanic

2025-09-10T07:22:09Z

Jimmy: Created page with "{{stub}} '''Building mechanics''' are tools the player can use to build, i.e. to manipulate components and wires. == List of building mechanics == * Editing * Resizing {{todo|complete this list}}"

{{stub}}

'''Building mechanics''' are tools the player can use to build, i.e. to manipulate [[Component|components]] and [[Wire|wires]].

== List of building mechanics ==

* [[Editing]]
* [[Resizing]]

{{todo|complete this list}}

Vanilla

2025-09-09T18:49:16Z

Jimmy: Created page with "{{stub}} '''Vanilla''' refers to the base game content that is part of Logic World without installing any mods."

{{stub}}

'''Vanilla''' refers to the base game content that is part of Logic World without installing any mods.

Component

2025-09-09T18:48:28Z

Jimmy: Add navbox components

{{stub}}

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

{{Navbox components}}

== See also ==

* [[:Category:Components]]

Template:Navbox components

2025-09-09T18:47:51Z

Jimmy: update title

{{Navbox
| title=[[Component|Components]] in [[vanilla]]
| [[:Category:Input components|Input components]]
|+ [[File:MHG.Button thumbnail render.png|16px]] [[Button]]
|+ [[File:MHG.Key thumbnail render.png|16px]] [[Key]]
|+ [[File:MHG.PanelButton thumbnail render.png|16px]] [[Panel Button]]
|+ [[File:MHG.PanelKey thumbnail render.png|16px]] [[Panel Key]]
|+ [[File:MHG.PanelSwitch thumbnail render.png|16px]] [[Panel Switch]]
|+ [[File:MHG.Switch thumbnail render.png|16px]] [[Switch]]
| [[:Category:Circuitry components|Circuitry components]]
|+ [[File:MHG.AndGate thumbnail render.png|16px]] [[AND Gate]]
|+ [[File:MHG.BufferWithOutput thumbnail render.png|16px]] [[Buffer]]
|+ [[File:MHG.ChubbySocket thumbnail render.png|16px]] [[Chubby Socket]]
|+ [[File:MHG.ChubbyThroughSocket thumbnail render.png|16px]] [[Chubby Through Socket]]
|+ [[File:MHG.Delayer thumbnail render.png|16px]] [[Delayer]]
|+ [[File:MHG.DLatch thumbnail render.png|16px]] [[D Latch]]
|+ [[File:MHG.Buffer thumbnail render.png|16px]] [[Fast Buffer]]
|+ [[File:MHG.Inverter thumbnail render.png|16px]] [[Inverter]]
|+ [[File:MHG.Peg thumbnail render.png|16px]] [[Peg]]
|+ [[File:MHG.Randomizer thumbnail render.png|16px]] [[Oracle]]
|+ [[File:MHG.Relay thumbnail render.png|16px]] [[Relay]]
|+ [[File:MHG.Socket thumbnail render.png|16px]] [[Socket]]
|+ [[File:MHG.ThroughPeg thumbnail render.png|16px]] [[Through Peg]]
|+ [[File:MHG.ThroughSocket thumbnail render.png|16px]] [[Through Socket]]
|+ [[File:MHG.XorGate thumbnail render.png|16px]] [[XOR Gate]]
| [[:Category:Output components|Output components]]
|+ [[File:MHG.StandingDisplay thumbnail render.png|16px]] [[Display]]
|+ [[File:MHG.Drum thumbnail render.png|16px]] [[Drum]]
|+ [[File:MHG.PanelDisplay thumbnail render.png|16px]] [[Panel Display]]
|+ [[File:MHG.Singer thumbnail render.png|16px]] [[Singer]]
| [[:Category:Miscellaneous components|Miscellaneous components]]
|+ [[File:MHG.Chair thumbnail render.png|16px]] [[Chair]]
|+ [[File:MHG.CircuitBoard thumbnail render.png|16px]] [[Circuit Board]]
|+ [[File:MHG.Flag thumbnail render.png|16px]] [[Flag]]
|+ [[File:MHG.Label thumbnail render.png|16px]] [[Label]]
|+ [[File:MHG.Mount thumbnail render.png|16px]] [[Mount]]
|+ [[File:MHG.PanelLabel thumbnail render.png|16px]] [[Panel Label]]
}}

Button

2025-09-09T05:06:42Z

Jimmy: fix categories

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

The '''Button''' is a [[component]] used for accepting the player's input. It can be pressed by left-clicking on it.

== Behavior ==

For as long as the player holds down left-click on the Button, its output will be {{on}}. When nobody is clicking on the Button, its output will be {{off}}.

== Configurability ==

The Button can be [[Editing|edited]] to change the color of the pressable part.

== Placement ==

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

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Input components]]

Flipping

2025-09-09T05:00:05Z

Jimmy: Created page with "{{stub}} '''Flipping''' is a building mechanic that lets you flip a component upside-down."

{{stub}}

'''Flipping''' is a [[building mechanic]] that lets you flip a [[component]] upside-down.

Optimization

2025-09-09T04:59:13Z

Jimmy: fix links and stuff

== Optimization ==

There are countless ways to build any given circuit. Different designs will have different characteristics.
This article will help you design circuits optimized for specific purposes.
You can mix and match different techniques to achieve the results you want.

So, when designing a circuit you need to decide what you want to optimize for. Let's break down each optimization one by one.

Please note that, while you may be familiar with real electronics or programming, in ''Logic World'' there are certain features that are not obvious at first.
These features can be used to your advantage when optimizing circuits.

== Speed ==
Speed is the time it takes for a signal to propagate through a circuit.
In Logic World, most gates have a delay of 1 tick. The more sequential gates you have, the slower the circuit will be.
When you have cycles or feedback in your circuit, speed becomes even more critical.
In complex circuits, you can measure the speed by counting ticks from the first activation of the input to the ''final'' state on the output.

There are three major ways to cut the delays:

*Remove unnecessary gates
*Use fast gates, such as [[Relay|Relays]] or [[Fast Buffer|Fast Buffers]]
*Mods

Let's break it down further.

==== Remove unnecessary gates ====
To start, the most newbie-friendly way to optimize gates is to just remove repetitions.
For example, if you have a NOT gate followed by another NOT gate, you can just remove both of them! The same applies to other gates. Instead of placing many AND gates following one after another, make a single big AND gate with multiple inputs.

Now moving on to a more complex topic.
The first big distinction of ''Logic World'' from real life is that there are no OR gates! Instead, wires are just connected together.
This game design already removes some gates.
But the OR operation is still a necessary part of logic, even if implicitly. We still need to connect wires together.
The problem is that the wrong way may either introduce delays or lead to backpropagation.
{{Backpropagation}}
A solution to this by using fast gates will be discussed later. Here I will show a hacky way: connecting multiple wires together from '''output''' pins.
You may notice that in the screenshot on the right, the '''output''' pin from the button is connected to a lamp and then the lamp is connected to another gate.
In general, if a wire is connected between normal pins, it will allow the signal to travel everywhere. The exception is the '''output''' pin.
Wires ''coming'' out of '''output''' pins do not conduct signals backward. To use it, you need to connect all the affected items to all the related '''output''' pins individually. You can always find the output pin by its big fat size. The next screenshot below shows the correct way.
[[File:Fix-backprop.png|thumb|right|alt=Everything is connected from output pins|Everything is connected from output pins]]
If you do it correctly, you won't need additional gates to stop backpropagation.
The drawback is that it requires a direct path from all the inputs to the outputs.

----

Also, in complex circuits it becomes hard to see individual wires.
<div class="mw-collapsible mw-collapsed">
Expand to see an example<div class="mw-collapsible-content">
[[File:Toomanywires.png|center|frameless|alt=toomanywires|toomanywires]]
</div>
</div>

----

Moving on to other techniques to remove unnecessary gates.
This part will require some logic understanding. In many cases, you can improve the circuit by just using a different formula than the one you initially thought of.
And remember the lack of OR gates, some circuit variations are simply simpler.
For example, you need <math>(B \land A) \lor (B \land C)</math>, this will require 2 explicit AND gates. But you can rewrite it as <math>B \land (A \lor C)</math>.
Notice in the screenshot that a different formulation leads to a smaller circuit.
[[File:ABC-circuit.png|thumb|On the left - two explicit gates. On the right - a simple refactoring removes one gate]]
Although this simple example doesn't improve speed (because it's not sequential), this lesson still shows that you can remove unnecessary gates.

The most useful thing to know here is [[wikipedia:De Morgan's laws|De Morgan's laws]]. They allow you to rewrite common formulas from one form to another.
There could be other examples, but just remember, this part will become easier with experience and overall logic understanding.

A bit more complex technique is to use negations. This often requires a complete rethinking of the design.
But when done correctly, it can lead to a significant reduction in the number of gates, especially in very big circuits.
To start, you need to stop thinking in terms of ON/OFF to activate something, you must embrace the negation!
For example, what if you can use 0 to indicate the enabled state in some part? This will already remove a NOT gate from the design.
{{todo|add specific examples with negated logic}}

==== Use fast gates ====
In ''Logic World'' there are so-called fast gates, such as [[Relay|relays]] or [[Fast Buffer|fast buffers]].
These gates don't have a delay to propagate the signal. This is far from real life, but if you learn to use them correctly, they can significantly speed up your circuits.
Let's break them down.
*[[Fast Buffer]] is a simple gate that just propagates the signal from input to output without any delay. The main purpose is to avoid backpropagation. It's also useful to route wires neatly.
:The drawback is that it's very bulky, increasing the circuit size significantly.
*[[Relay]] is a gate that also propagates the signal without delay, but only if enabled. It's different from Fast Buffers in two major ways:
** It propagates signals both ways, so it can't be used to avoid backpropagation.
**Enabling it takes 1 tick, but after it's enabled, it will propagate the signal without delay.
While fast gates increase the overall number of gates, they remove delays.
So you can use Fast Buffer to replace regular [[Buffer|buffers]] and
Relays to replace [[AND Gate|AND gates]].
But remember, sometimes you still need regular Buffers to synchronize signals. Otherwise, signals coming from fast gates may not match with signals from other gates.
Please note, that extensive usage of fast gates may lead to slower performance, as all connected gates updated all at once each tick.

A notable example of a circuit with fast gates is an [[ICA|Instant Carry Adder ('''ICA''')]].

==== Mods ====
There are many mods that add complex circuits as single black boxes, and they usually take 1 tick to perform the function.
Examples: CPUs, RAMs, Displays, Keyboards, Network devices, Decoders, Buffers, etc.

== Performance ==
Even if you design a very fast circuit, it may be too big for the game to handle, especially on high tickrates, leading to lags or slower execution overall.
You may want to trade off some circuit speed for better simulation performance.
Usually it may be done by splitting the circuit into smaller parts that are activated only when needed.
The heaviest parts are usually decoders (by themselves or with RAM), HDDs, LUTs.
Let's say you have a huge decoder with 1024 outputs. In a naive design, it will activate all the gates at once, leading to a big lag spike.
How do you optimize it?
You can do it by iteratively converging on the output, using the divide and conquer approach.
For example, split the computation into two iterations:

#First iteration: a 3-bit decoder, effectively multiplexing the input between 8x parts.
#Second iteration: only one active 7-bit decoder among 8 parts, with 128 outputs.

You can divide it however you want, the main idea is to reduce the number of gates activated at once.
{{todo|expand on the topic}}

== Size ==
If you focus only on speed or performance, you may end up with a huge circuit that is hard to build and manage.
Sometimes you need to optimize purely for size.
Minimizing the size will force you to avoid bulky fast gates, introduce cycles, remove parallelism, etc., often leading to slower circuits. But with high tickrates, it may still be worth it.
We will not be focusing on designing a logic with a smaller footprint. Instead, here are''structural'' tips that some people find useful:

*Use "round" or "hollow" designs.
*Use 1-tile stackable parts.
These "round" or "hollow" designs are made by placing supporting structures at the edges or against each other and putting logic and wiring in the middle of it. Always remember, ''Logic world'' is 3D!
This approach is extremely useful for wiring, as it allows you to basically connect '''everything to everything'''.
Examples:
[[File:Compact-design1.png|frame|center|alt=Logic gates are only in 4 corners, all wires are inside |Logic gates are only in 4 corners, all wires are inside]]

[[File:Compact-design2.png|frame|center|alt=Logic gates are against each other|Logic gates are against each other]]

{{todo|expand on the topic}}

Lookup Table

2025-09-09T04:58:28Z

Jimmy: /* Construction */

Any arbitrary logic formula can always be represented in [https://en.wikipedia.org/wiki/Disjunctive_normal_form disjunctive normal form]. Put in simple terms, the output of the formula is computed using a single OR operation on its inputs coming from a number of AND gates. Each AND gate represents a distinct case where the output is supposed to be ''true''.
[[File:5BitEqualityLut.png|alt=5 bit equality LUT|thumb|5 bit equality LUT]]

{{LUT}}.
== Construction ==
A LUT is implemented by first creating a list of all input combinations that should lead to a ''true'' output. From this list, the LUT can then be built quite easily.
It consists of multiple relay chains that are simply OR-ed together at the end, where one chain corresponds to one input-assignment that should lead to a truthy output value. The aforementioned relay chains are started by a single NOT-gate whose inputs are all signals that are ''false'' in the case where a ''true'' output is expected, followed by a set of relays where the top input is expected to be ''true'' for such a ''true'' result.

We can avoid delays by not using [[Buffer|Buffers]], it will make circuit perform the operation in a single tick!
In that case, back-propagation must be prevented by using [[Fast Buffer|Fast Buffers]].
In this case each chain needs one component per input (relays plus Fast Buffers), along with one NOT-gate if there are any inputs that are supposed to be ''off''.
=== Complexity to build ===
When building a LUT as described above, we can count the total number of components as:
:<math>C = c \cdot (1 + n)</math>
Where:

<math>c</math> is the number of distinct '''chains''' (true outputs),<br>
<math>n</math> is the number of inputs.

Let's assume half of all possible input combinations lead to a true output:

:<math>c = 50%( 2^n) = 2^{n-1}</math>
So in total:
:<math>C = 2^{n-1} \cdot (1 + n)</math>
In theory it's asymptotically approaching : <math>\mathcal{O}(2^n)</math>

In other words, the required component count grows exponentially with the number of inputs, assuming the number of true-output cases also scales exponentially.

While LUT circuits become very expensive in terms of components, they are the '''extremely fast''', producing an output in a single tick regardless of input size. This makes them essential for designs that must run within strict time limits. For non-trivial functions, this speed is usually only achievable by using a LUT.

{{todo|add infobox giving an overview of time and component count maybe?}}

Lookup Table

2025-09-09T04:58:13Z

Jimmy: fix link

Any arbitrary logic formula can always be represented in [https://en.wikipedia.org/wiki/Disjunctive_normal_form disjunctive normal form]. Put in simple terms, the output of the formula is computed using a single OR operation on its inputs coming from a number of AND gates. Each AND gate represents a distinct case where the output is supposed to be ''true''.
[[File:5BitEqualityLut.png|alt=5 bit equality LUT|thumb|5 bit equality LUT]]

{{LUT}}.
== Construction ==
A LUT is implemented by first creating a list of all input combinations that should lead to a ''true'' output. From this list, the LUT can then be built quite easily.
It consists of multiple relay chains that are simply OR-ed together at the end, where one chain corresponds to one input-assignment that should lead to a truthy output value. The aforementioned relay chains are started by a single NOT-gate whose inputs are all signals that are ''false'' in the case where a ''true'' output is expected, followed by a set of relays where the top input is expected to be ''true'' for such a ''true'' result.

We can avoid delays by not using [[Buffer|buffers]], it will make circuit perform the operation in a single tick!
In that case, back-propagation must be prevented by using [[Fast Buffer|Fast Buffers]].
In this case each chain needs one component per input (relays plus Fast Buffers), along with one NOT-gate if there are any inputs that are supposed to be ''off''.
=== Complexity to build ===
When building a LUT as described above, we can count the total number of components as:
:<math>C = c \cdot (1 + n)</math>
Where:

<math>c</math> is the number of distinct '''chains''' (true outputs),<br>
<math>n</math> is the number of inputs.

Let's assume half of all possible input combinations lead to a true output:

:<math>c = 50%( 2^n) = 2^{n-1}</math>
So in total:
:<math>C = 2^{n-1} \cdot (1 + n)</math>
In theory it's asymptotically approaching : <math>\mathcal{O}(2^n)</math>

In other words, the required component count grows exponentially with the number of inputs, assuming the number of true-output cases also scales exponentially.

While LUT circuits become very expensive in terms of components, they are the '''extremely fast''', producing an output in a single tick regardless of input size. This makes them essential for designs that must run within strict time limits. For non-trivial functions, this speed is usually only achievable by using a LUT.

{{todo|add infobox giving an overview of time and component count maybe?}}

Main Page

2025-09-09T04:57:26Z

Jimmy: /* Wiki articles to check out */

Welcome to the Logic World Wiki. This wiki is dedicated to anything and everything related to [[Logic World]], a video game where you can invent a new computer!

== Logic World Links ==

* [https://logic.world Logic World home page]
* [https://store.steampowered.com/app/1054340/Logic_World/ Logic World on Steam]
* [https://discord.gg/C5Qkk53 Logic World Discord]

== Wiki articles to check out ==

* [[Component]], the items used to build structures in Logic World
* [[Circuit]], a combination of components with more complex behavior
* [[Building mechanic|Building mechanics]]
* [[Your First Computer]]
* [[Modding:Introduction|Modding introduction]]
* [[Dedicated Server Setup Guide]]

== Stats ==

The wiki has:

* [[Special:AllPages|{{NUMBEROFARTICLES}} articles]]
* [[Special:ListFiles|{{NUMBEROFFILES}} files]]
* [[Special:ListUsers|{{NUMBEROFUSERS}} registered users]]
* [[Special:RecentChanges|{{NUMBEROFEDITS}} total edits]]

Anybody can edit this wiki. For more information, see [[Logic World Wiki:Contributing]].

Main Page

2025-09-09T04:56:58Z

Jimmy: update link

Welcome to the Logic World Wiki. This wiki is dedicated to anything and everything related to [[Logic World]], a video game where you can invent a new computer!

== Logic World Links ==

* [https://logic.world Logic World home page]
* [https://store.steampowered.com/app/1054340/Logic_World/ Logic World on Steam]
* [https://discord.gg/C5Qkk53 Logic World Discord]

== Wiki articles to check out ==

* [[Component]], the items used to build structures in Logic World
* [[Circuit]], a combination of components with more complex behavior
* [[Building Mechanic|Building mechanics]]
* [[Your First Computer]]
* [[Modding:Introduction|Modding introduction]]
* [[Dedicated Server Setup Guide]]

== Stats ==

The wiki has:

* [[Special:AllPages|{{NUMBEROFARTICLES}} articles]]
* [[Special:ListFiles|{{NUMBEROFFILES}} files]]
* [[Special:ListUsers|{{NUMBEROFUSERS}} registered users]]
* [[Special:RecentChanges|{{NUMBEROFEDITS}} total edits]]

Anybody can edit this wiki. For more information, see [[Logic World Wiki:Contributing]].

Panel Label

2025-09-09T04:56:10Z

Jimmy:

{{stub}}

{{Infobox component
| title = Panel Label
| id = MHG.PanelLabel
| caption = Panel Label
| configurable = 1
}}

The '''Panel Label''' is a variant of the [[Label]] that is shorter. It matches the height of panel input components like the [[Panel Button]] and [[Panel Switch]], so it is often used to label the function of these input components.

== Behavior ==

The Label displays text.

== Configurability ==

The Panel Label can be [[Editing|edited]] to change the text, as well as the text style, size and alignment.

{{todo|screenshot of the Edit Label Menu}}

The Panel Label can also be [[Resizing|resized]] to have a bigger footprint.

== Placement ==

{{todo|describe placement}}

{{Navbox components}}

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

Label

2025-09-09T04:56:05Z

Jimmy:

{{Infobox component
| title = Label
| id = MHG.Label
| caption = Label
| configurable = 1
}}

The '''Label''' is a [[component]] that can be set to have some text on it. It is used for taking in-game notes and describing what parts of the circuit do, particularly to label inputs like [[Button|Buttons]] and [[Switch|Switches]].

== Behavior ==

The Label displays text.

== Configurability ==

The Label can be [[Editing|edited]] to change the text, as well as the text style, size and alignment.

{{todo|screenshot of the Edit Label Menu}}

The Label can also be [[Resizing|resized]] to have a bigger footprint.

== Placement ==

{{todo|describe placement}}

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Miscellaneous components]]

Flag

2025-09-09T04:56:00Z

Jimmy:

{{stub}}

{{Infobox component
| title = Flag
| id = MHG.Flag
| caption = A green Flag
| configurable = 1
}}

The '''Flag''' is a [[component]] used for decoration, as a teleportation waypoint, and occasionally as a structural element.

== Behavior ==

The Flag's cloth flaps in the breeze. If a [[Player]] comes close to it, they can push the cloth around. Players can teleport to Flags where that's been enabled.

Any component that can be placed on top of a [[Mount]] can also be placed on top of a Flag.

== Configurability ==

The Flag can be vertically [[Resizing|resized]].

The Flag can also be [[Editing|edited]] to change the cloth color and size. From this menu, you can also choose to show or hide this Flag in the Teleport Menu, and change its name within the Teleport Menu.

{{todo|screenshot of the Edit Flag Menu}}

== Placement ==

The Flag can only be placed in the center of a [[Circuit Board]] square or in the center of a board edge. Flags can be fine-rotated.

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Miscellaneous components]]

Chair

2025-09-09T04:55:54Z

Jimmy:

{{stub}}

{{Infobox component
| title = Chair
| id = MHG.Chair
| caption = Chair
| configurable = 1
}}

The '''Chair''' is a [[component]] that [[Player|players]] can sit in.

== Behavior ==

When sitting in a Chair, you cannot move, but you can look around. You cannot build, but you can interact with [[Button|Buttons]], [[Switch|Switches]], [[Key|Keys]], and other Chairs.

== Configurability ==

The Chair can be [[Editing|edited]] to change its color.

== Placement ==

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

== Gallery ==

<gallery>
Players sitting in chairs.jpg|A group of players sitting in blue Chairs arranged in a circle.
</gallery>

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Miscellaneous components]]

Circuit Board

2025-09-09T04:55:49Z

Jimmy:

{{stub}}

{{Infobox component
| title = Circuit Board
| id = MHG.CircuitBoard
| caption = A 1x1 gray circuit board
| configurable = 1
}}

The '''Circuit Board''' is a structural [[component]].

== Behavior ==

The Circuit Board has no special behavior except for being part of a larger structure.

== Configurability ==

The Circuit Board can be [[Resizing|resized]] from 1x1 up to 80x80. It can also be [[Editing|edited]] to change its color.

== Placement ==

The Circuit Board has the most complex placement of any component in the game.

{{todo|actually explain the placement, and provide helpful images}}

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Miscellaneous components]]

Drum

2025-09-09T04:55:40Z

Jimmy:

{{stub}}

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

The '''Drum''' is a [[component]] that plays an unpitched sound when its input is {{on}}. It is similar to the [[Singer]], but it cannot be tuned.

== Behavior ==

When a Drum's input turns {{on}}, it will start playing a sound. When the input turns {{off}}, the sound will stop playing.

== Configurability ==

The Drum can be [[Editing|edited]] to choose the sound to play.

{{todo|image of the Edit Drum Menu}}

== Placement ==

The Drum can be placed the same way as a [[Peg]]: in the center of a [[Circuit Board]] square, on the edge of a Circuit Board, or on top of a [[Mount]], with 8+2 additional fine-placement positions on board square and edge. It can also be fine-rotated.

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Output components]]

Singer

2025-09-09T04:55:36Z

Jimmy:

{{stub}}

{{Infobox component
| title = Singer
| id = MHG.Singer
| caption = A Singer tuned to C4
| configurable = 1
| io.minInputs = 1
| io.maxInputs = 1
| io.outputs = 0
}}

The '''Singer''' is a [[component]] that plays a pitched sound when its input is {{on}}.

== Behavior ==

When a Singer's input turns {{on}}, it will start playing a sound. When the input turns {{off}}, the sound will stop playing.

== Configurability ==

The Singer can be [[Editing|edited]] to choose the pitch of the sound to play and the instrument to use.

{{todo|image of the Edit Singer Menu}}

== Placement ==

The Singer can be placed the same way as a [[Peg]]: in the center of a [[Circuit Board]] square, on the edge of a Circuit Board, or on top of a [[Mount]], with 8+2 additional fine-placement positions on board square and edge. It can also be fine-rotated.

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Output components]]

Display

2025-09-09T04:55:32Z

Jimmy:

{{Infobox component
| title = Display
| id = MHG.StandingDisplay
| caption = A Display with one input
| configurable = 1
| io.minInputs = 1
| io.maxInputs = 4
| io.outputs = 0
}}

The '''Display''' is a [[component]] used for displaying visual information.

== Behavior ==

A Display changes color depending on the state of its inputs. The color it chooses depends on its [[Display Configuration]], which can be set in the Edit Menu.

The Display changes color on the same frame the input (or inputs) change state.

== Configurability ==

The Display can be [[Editing|edited]] to increase its input count from the default of 1 up to a maximum of 4.

In the same menu, you can select the [[Display Configuration]] for this Display to use. You can also access the menu for editing, adding, and deleting display configurations.

== Placement ==

When a Display has 1 input, it can be placed the same way as a [[Peg]]: in the center of a [[Circuit Board]] square, on the edge of a Circuit Board, or on top of a [[Mount]], with 8+2 additional fine-placement positions on board square and edge. It can also be fine-rotated.

When it has more than 1 input, it can only be placed in the center of a board square or on top of a mount, and cannot be fine-rotated.

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

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Output components]]

Panel Key

2025-09-09T04:55:28Z

Jimmy:

{{stub}}

{{Infobox component
| title = Panel Key
| id = MHG.PanelKey
| caption = Panel Key
| configurable = 1
| io.minInputs = 0
| io.maxInputs = 0
| io.outputs = 1
}}

The '''Panel Key''' is a variant of the [[Key]] that goes through the [[Circuit Board]] it's placed on.

== Behavior ==

{{todo|describe behavior}}

== Configurability ==

The Panel Key can be [[Editing|edited]], with the same options as [[Key|Keys]].

== Placement ==

The Panel Key can only be placed in the center of a [[Circuit Board]] square. It can be fine-rotated.

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Input components]]

Key

2025-09-09T04:55:24Z

Jimmy:

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

The '''Key''' is a [[component]] used for accepting the player's input. Its state is synchronized to the state of a physical key on the player's keyboard, or another real life input like a mouse button, gamepad button, or MIDI input.

== Behavior ==

The Key is configured with a certain real life input. When that input is held down in real life, the Key is also held down, and its output is {{on}}. The Key can also be clicked on like a [[Button]] to press it. Otherwise, the output is {{off}}.

== Configurability ==

The Key can be [[Editing|edited]]. Several properties can be changed:

* The real life input the Key corresponds to.
* The color of the pressable part of the Key.
* The color of the text on the Key.
* Whether the Key can only be pressed while sitting in a [[Chair]].

{{todo|image of the edit key menu}}

== Placement ==

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

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Input components]]

Panel Switch

2025-09-09T04:55:19Z

Jimmy:

{{stub}}

{{Infobox component
| title = Panel Switch
| id = MHG.PanelSwitch
| caption = Panel Switch
| configurable = 1
| io.minInputs = 0
| io.maxInputs = 0
| io.outputs = 1
}}

The '''Panel Switch''' is a variant of the [[Switch]] that goes through the [[Circuit Board]] it's placed on.

== Behavior ==

{{todo|describe behavior}}

== Configurability ==

The Panel Switch can be [[Editing|edited]] to change the color of the flippy part.

== Placement ==

The Panel Switch can only be placed in the center of a [[Circuit Board]] square. It can be fine-rotated.

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Input components]]

Switch

2025-09-09T04:55:15Z

Jimmy:

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

The '''Switch''' is a [[component]] used for accepting the player's input. It can be toggled by left-clicking on it.

== Behavior ==

When the Switch is flipped to one side, its output will be {{on}}. When it's flipped to the other side, its output will be {{off}}.

== Configurability ==

The Switch can be [[Editing|edited]] to change the color of the flippy part.

== Placement ==

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

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Input components]]

Panel Button

2025-09-09T04:55:09Z

Jimmy:

{{stub}}

{{Infobox component
| title = Panel Button
| id = MHG.PanelButton
| caption = Panel Button
| configurable = 1
| io.minInputs = 0
| io.maxInputs = 0
| io.outputs = 1
}}

The '''Panel Button''' is a variant of the [[Button]] that goes through the [[Circuit Board]] it's placed on.

== Behavior ==

{{todo|describe behavior}}

== Configurability ==

The Panel Button can be resized. It can also be [[Editing|edited]] to change the color of the pressable part.

== Placement ==

The Panel Button can only be placed in the center of a [[Circuit Board]] square.

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Input components]]

Button

2025-09-09T04:55:04Z

Jimmy:

Delayer

2025-09-09T04:54:57Z

Jimmy:

{{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 can be [[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]]

Panel Display

2025-09-09T04:54:34Z

Jimmy:

{{Infobox component
| title = Panel Display
| id = MHG.PanelDisplay
| caption = A 1x1 Panel Display with 1 input
| io.minInputs = 1
| io.maxInputs = 9
| io.outputs = 0
|io.propagationDelay=0}}

The '''Panel Display''' is a [[component]] used for displaying visual information. It is similar to the [[Display]], but instead of being placed standing up, it's placed through a [[Circuit Board]]. This allows for easily building flush screens, or for hiding the circuitry that is wired up to the component.

The Panel Display is about <math>2 \frac{1}{6}</math> tiles long, 1 tile in width, and 1 tile in height (65cm × 30cm × 30cm. See [[measurements]]).

== Behavior ==

A Panel Display changes color depending on the state of its inputs. The color it chooses depends on its [[Display Configuration]], which can be set in the Edit Menu.

The Panel Display changes color on the same frame the input (or inputs) change state.

== Configurability ==

The Panel Display has a default size of 1x1 [[Measurements|tiles]], but can be [[Resizing|resized]] up to 12x12.

The Panel Display can be [[Editing|edited]] to increase its input count from the default of 1. The maximum input count depends on its size. A 1x1 Panel Display can have up to 3 inputs, but if resized, it can have up to 9.

In the same menu, you can select the [[Display Configuration]] for this display to use. You can also access the menu for editing, adding, and deleting display configurations.

== Placement ==

The Panel Display can only be placed in the center of a [[Circuit Board]] square.

== Trivia ==

* Unlike its counterpart the [[Display]], the Panel Display can have up to 9 input pegs when resized from its default size, whereas the [[Display]] can only have up to 4 input pegs.
* The Panel Display is one of six components that can only be placed through a Circuit Board. The others are the [[Panel Button]], [[Panel Key]], [[Panel Switch]], [[Through Peg]], and the two hidden components [[Through Socket]] and [[Chubby Through Socket]].

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Output components]]

Editing

2025-09-09T04:53:22Z

Jimmy: Created page with "{{stub}} '''Editing''' is a building mechanic that lets you open a menu to change the properties of a component."

{{stub}}

'''Editing''' is a [[building mechanic]] that lets you open a menu to change the properties of a [[component]].

Resizing

2025-09-09T04:53:09Z

Jimmy:

{{stub}}

'''Resizing''' is a [[building mechanic]] that lets you change the size of a [[component]].

Mouse Hat Games

2025-09-09T04:52:11Z

Jimmy: Created page with "{{stub}} Mouse Hat Games is an international indie game studio."

{{stub}}

Mouse Hat Games is an international indie game studio.

Optimization

2025-09-09T04:51:04Z

Jimmy: fix links

== Optimization ==

There are countless ways to build any given circuit. Different designs will have different characteristics.
This article will help you design circuits optimized for specific purposes.
You can mix and match different techniques to achieve the results you want.

So, when designing a circuit you need to decide what you want to optimize for. Let's break down each optimization one by one.

Please note that, while you may be familiar with real electronics or programming, in ''Logic World'' there are certain features that are not obvious at first.
These features can be used to your advantage when optimizing circuits.

== Speed ==
Speed is the time it takes for a signal to propagate through a circuit.
In Logic World, most gates have a delay of 1 tick. The more sequential gates you have, the slower the circuit will be.
When you have cycles or feedback in your circuit, speed becomes even more critical.
In complex circuits, you can measure the speed by counting ticks from the first activation of the input to the ''final'' state on the output.

There are three major ways to cut the delays:

*Remove unnecessary gates
*Use fast gates, such as [[Relay|Relays]] or [[Fast Buffer|Fast Buffers]]
*Mods

Let's break it down further.

==== Remove unnecessary gates ====
To start, the most newbie-friendly way to optimize gates is to just remove repetitions.
For example, if you have a NOT gate followed by another NOT gate, you can just remove both of them! The same applies to other gates. Instead of placing many AND gates following one after another, make a single big AND gate with multiple inputs.

Now moving on to a more complex topic.
The first big distinction of ''Logic World'' from real life is that there are no OR gates! Instead, wires are just connected together.
This game design already removes some gates.
But the OR operation is still a necessary part of logic, even if implicitly. We still need to connect wires together.
The problem is that the wrong way may either introduce delays or lead to backpropagation.
{{Backpropagation}}
A solution to this by using fast gates will be discussed later. Here I will show a hacky way: connecting multiple wires together from '''output''' pins.
You may notice that in the screenshot on the right, the '''output''' pin from the button is connected to a lamp and then the lamp is connected to another gate.
In general, if a wire is connected between normal pins, it will allow the signal to travel everywhere. The exception is the '''output''' pin.
Wires ''coming'' out of '''output''' pins do not conduct signals backward. To use it, you need to connect all the affected items to all the related '''output''' pins individually. You can always find the output pin by its big fat size. The next screenshot below shows the correct way.
[[File:Fix-backprop.png|thumb|right|alt=Everything is connected from output pins|Everything is connected from output pins]]
If you do it correctly, you won't need additional gates to stop backpropagation.
The drawback is that it requires a direct path from all the inputs to the outputs.

----

Also, in complex circuits it becomes hard to see individual wires.
<div class="mw-collapsible mw-collapsed">
Expand to see an example<div class="mw-collapsible-content">
[[File:Toomanywires.png|center|frameless|alt=toomanywires|toomanywires]]
</div>
</div>

----

Moving on to other techniques to remove unnecessary gates.
This part will require some logic understanding. In many cases, you can improve the circuit by just using a different formula than the one you initially thought of.
And remember the lack of OR gates, some circuit variations are simply simpler.
For example, you need <math>(B \land A) \lor (B \land C)</math>, this will require 2 explicit AND gates. But you can rewrite it as <math>B \land (A \lor C)</math>.
Notice in the screenshot that a different formulation leads to a smaller circuit.
[[File:ABC-circuit.png|thumb|On the left - two explicit gates. On the right - a simple refactoring removes one gate]]
Although this simple example doesn't improve speed (because it's not sequential), this lesson still shows that you can remove unnecessary gates.

The most useful thing to know here is [[wikipedia:De Morgan's laws|De Morgan's laws]]. They allow you to rewrite common formulas from one form to another.
There could be other examples, but just remember, this part will become easier with experience and overall logic understanding.

A bit more complex technique is to use negations. This often requires a complete rethinking of the design.
But when done correctly, it can lead to a significant reduction in the number of gates, especially in very big circuits.
To start, you need to stop thinking in terms of ON/OFF to activate something, you must embrace the negation!
For example, what if you can use 0 to indicate the enabled state in some part? This will already remove a NOT gate from the design.
{{todo|add specific examples with negated logic}}

==== Use fast gates ====
In ''Logic World'' there are so-called fast gates, such as [[Relay|relays]] or [[Fast buffer|fast buffers]].
These gates don't have a delay to propagate the signal. This is far from real life, but if you learn to use them correctly, they can significantly speed up your circuits.
Let's break them down.
*[[Fast buffer]] is a simple gate that just propagates the signal from input to output without any delay. The main purpose is to avoid backpropagation. It's also useful to route wires neatly.
:The drawback is that it's very bulky, increasing the circuit size significantly.
*[[Relay]] is a gate that also propagates the signal without delay, but only if enabled. It's different from Fast buffers in two major ways:
** It propagates signals both ways, so it can't be used to avoid backpropagation.
**Enabling it takes 1 tick, but after it's enabled, it will propagate the signal without delay.
While fast gates increase the overall number of gates, they remove delays.
So you can use Fast buffer to replace regular [[Buffer|buffers]] and
Relays to replace [[AND Gate|AND gates]].
But remember, sometimes you still need regular Buffers to synchronize signals. Otherwise, signals coming from fast gates may not match with signals from other gates.
Please note, that extensive usage of fast gates may lead to slower performance, as all connected gates updated all at once each tick.

A notable example of a circuit with fast gates is an [[ICA|Instant Carry Adder ('''ICA''')]].

==== Mods ====
There are many mods that add complex circuits as single black boxes, and they usually take 1 tick to perform the function.
Examples: CPUs, RAMs, Displays, Keyboards, Network devices, Decoders, Buffers, etc.

== Performance ==
Even if you design a very fast circuit, it may be too big for the game to handle, especially on high tickrates, leading to lags or slower execution overall.
You may want to trade off some circuit speed for better simulation performance.
Usually it may be done by splitting the circuit into smaller parts that are activated only when needed.
The heaviest parts are usually decoders (by themselves or with RAM), HDDs, LUTs.
Let's say you have a huge decoder with 1024 outputs. In a naive design, it will activate all the gates at once, leading to a big lag spike.
How do you optimize it?
You can do it by iteratively converging on the output, using the divide and conquer approach.
For example, split the computation into two iterations:

#First iteration: a 3-bit decoder, effectively multiplexing the input between 8x parts.
#Second iteration: only one active 7-bit decoder among 8 parts, with 128 outputs.

You can divide it however you want, the main idea is to reduce the number of gates activated at once.
{{todo|expand on the topic}}

== Size ==
If you focus only on speed or performance, you may end up with a huge circuit that is hard to build and manage.
Sometimes you need to optimize purely for size.
Minimizing the size will force you to avoid bulky fast gates, introduce cycles, remove parallelism, etc., often leading to slower circuits. But with high tickrates, it may still be worth it.
We will not be focusing on designing a logic with a smaller footprint. Instead, here are''structural'' tips that some people find useful:

*Use "round" or "hollow" designs.
*Use 1-tile stackable parts.
These "round" or "hollow" designs are made by placing supporting structures at the edges or against each other and putting logic and wiring in the middle of it. Always remember, ''Logic world'' is 3D!
This approach is extremely useful for wiring, as it allows you to basically connect '''everything to everything'''.
Examples:
[[File:Compact-design1.png|frame|center|alt=Logic gates are only in 4 corners, all wires are inside |Logic gates are only in 4 corners, all wires are inside]]

[[File:Compact-design2.png|frame|center|alt=Logic gates are against each other|Logic gates are against each other]]

{{todo|expand on the topic}}

Clock

2025-09-09T04:50:36Z

Jimmy: Created page with "{{stub}} A '''Clock''' is a circuit that changes its output state predictably over time."

{{stub}}

A '''Clock''' is a [[circuit]] that changes its output state predictably over time.

Fast Buffer

2025-09-09T04:49:51Z

Jimmy: minor fixes

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

The '''Fast Buffer''' is a [[component]] used for [[digital logic]]. It has two inputs, with one higher up than the other. The lower input will be {{on}} if the upper input is {{on}}, but not vice-versa; in this way, the component "buffers" the signal by only allowing it to travel one way.

The Fast Buffer is similar to the [[Buffer]], but:

* It takes up more space
* It uses two inputs, instead of one input and one output
* It updates in zero [[tick|ticks]] instead of one

Fast Buffers are commonly used to [[Optimization|optimize]] circuits for speed. Their unique zero-tick logic allows time to be saved in many circuits.

== Behavior ==

The Fast Buffer's two inputs are linked, with the lower input following the state of the upper input.

{{Truth table
| inputs=Higher Input,Lower Input
| outputs=0
| caption=Fast Buffer Truth Table
| 0 0
| 1 1
}}

The lower input updates it state in the same [[tick]] that the upper input changes state.

Because the lower peg is an input and not an output, if multiple circuits are attached directly to the lower peg, signals can flow between them, unlike with regular [[Buffer|Buffers]]. If this behavior is undesirable for your circuit, you can add additional Fast Buffers, one for each section of the circuit you want to keep isolated. {{todo|image demonstrating this}}

== Placement ==

Fast Buffers have two attachment points, one for each square covered by the body of the component. These attachment points can be placed in the center of a [[Circuit Board]] square or on top of a [[Mount]].

{{Navbox components}}

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

Resizing

2025-09-09T04:49:10Z

Jimmy: Created page with "{{stub}} '''Resizing''' is a building mechanic that lets you change the size of a component."

{{stub}}

'''Resizing''' is a [[building mechanic]] that lets you change the size of a component.

Panel Label

2025-09-09T04:45:43Z

Jimmy: add stub template

{{stub}}

{{Infobox component
| title = Panel Label
| id = MHG.PanelLabel
| caption = Panel Label
| configurable = 1
}}

The '''Panel Label''' is a variant of the [[Label]] that is shorter. It matches the height of panel input components like the [[Panel Button]] and [[Panel Switch]], so it is often used to label the function of these input components.

== Behavior ==

The Label displays text.

== Configurability ==

The Panel Label can be [[Edit Component Menu|edited]] to change the text, as well as the text style, size and alignment.

{{todo|screenshot of the Edit Label Menu}}

The Panel Label can also be [[Resizing|resized]] to have a bigger footprint.

== Placement ==

{{todo|describe placement}}

{{Navbox components}}

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

Panel Label

2025-09-09T04:45:23Z

Jimmy: Created page with "{{Infobox component | title = Panel Label | id = MHG.PanelLabel | caption = Panel Label | configurable = 1 }} The '''Panel Label''' is a variant of the Label that is shorter. It matches the height of panel input components like the Panel Button and Panel Switch, so it is often used to label the function of these input components. == Behavior == The Label displays text. == Configurability == The Panel Label can be Edit Component Menu|..."

{{Infobox component
| title = Panel Label
| id = MHG.PanelLabel
| caption = Panel Label
| configurable = 1
}}

The '''Panel Label''' is a variant of the [[Label]] that is shorter. It matches the height of panel input components like the [[Panel Button]] and [[Panel Switch]], so it is often used to label the function of these input components.

== Behavior ==

The Label displays text.

== Configurability ==

The Panel Label can be [[Edit Component Menu|edited]] to change the text, as well as the text style, size and alignment.

{{todo|screenshot of the Edit Label Menu}}

The Panel Label can also be [[Resizing|resized]] to have a bigger footprint.

== Placement ==

{{todo|describe placement}}

{{Navbox components}}

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

Label

2025-09-09T04:45:01Z

Jimmy: fix category

{{Infobox component
| title = Label
| id = MHG.Label
| caption = Label
| configurable = 1
}}

The '''Label''' is a [[component]] that can be set to have some text on it. It is used for taking in-game notes and describing what parts of the circuit do, particularly to label inputs like [[Button|Buttons]] and [[Switch|Switches]].

== Behavior ==

The Label displays text.

== Configurability ==

The Label can be [[Edit Component Menu|edited]] to change the text, as well as the text style, size and alignment.

{{todo|screenshot of the Edit Label Menu}}

The Label can also be [[Resizing|resized]] to have a bigger footprint.

== Placement ==

{{todo|describe placement}}

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Miscellaneous components]]

Label

2025-09-09T04:42:52Z

Jimmy: Created page with "{{Infobox component | title = Label | id = MHG.Label | caption = Label | configurable = 1 }} The '''Label''' is a component that can be set to have some text on it. It is used for taking in-game notes and describing what parts of the circuit do, particularly to label inputs like Buttons and Switches. == Behavior == The Label displays text. == Configurability == The Label can be edited to change the..."

{{Infobox component
| title = Label
| id = MHG.Label
| caption = Label
| configurable = 1
}}

The '''Label''' is a [[component]] that can be set to have some text on it. It is used for taking in-game notes and describing what parts of the circuit do, particularly to label inputs like [[Button|Buttons]] and [[Switch|Switches]].

== Behavior ==

The Label displays text.

== Configurability ==

The Label can be [[Edit Component Menu|edited]] to change the text, as well as the text style, size and alignment.

{{todo|screenshot of the Edit Label Menu}}

The Label can also be [[Resizing|resized]] to have a bigger footprint.

== Placement ==

{{todo|describe placement}}

{{Navbox components}}

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

Flag

2025-09-09T04:40:40Z

Jimmy: /* Configurability */

{{stub}}

{{Infobox component
| title = Flag
| id = MHG.Flag
| caption = A green Flag
| configurable = 1
}}

The '''Flag''' is a [[component]] used for decoration, as a teleportation waypoint, and occasionally as a structural element.

== Behavior ==

The Flag's cloth flaps in the breeze. If a [[Player]] comes close to it, they can push the cloth around. Players can teleport to Flags where that's been enabled.

Any component that can be placed on top of a [[Mount]] can also be placed on top of a Flag.

== Configurability ==

The Flag can be vertically [[Resizing|resized]].

The Flag can also be [[Edit Component Menu|edited]] to change the cloth color and size. From this menu, you can also choose to show or hide this Flag in the Teleport Menu, and change its name within the Teleport Menu.

{{todo|screenshot of the Edit Flag Menu}}

== Placement ==

The Flag can only be placed in the center of a [[Circuit Board]] square or in the center of a board edge. Flags can be fine-rotated.

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Miscellaneous components]]

Mount

2025-09-09T04:38:06Z

Jimmy: fix category

{{stub}}

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

The '''Mount''' is a structural [[component]].

== Behavior ==

The Mount has no special behavior except for being part of a larger structure.

== Configurability ==

The Mount can be vertically [[Resizing|resized]].

== Placement ==

Mounts can be placed on the lines between [[Circuit Board]] squares and on board edges. With fine-placement, they can be placed in the center of board squares.

{{todo|image of different ways Mounts can be placed, and how they can fit between Panel components}}

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Miscellaneous components]]

Circuit Board

2025-09-09T04:38:05Z

Jimmy: fix category

{{stub}}

{{Infobox component
| title = Circuit Board
| id = MHG.CircuitBoard
| caption = A 1x1 gray circuit board
| configurable = 1
}}

The '''Circuit Board''' is a structural [[component]].

== Behavior ==

The Circuit Board has no special behavior except for being part of a larger structure.

== Configurability ==

The Circuit Board can be [[Resizing|resized]] from 1x1 up to 80x80. It can also be [[Edit Component Menu|edited]] to change its color.

== Placement ==

The Circuit Board has the most complex placement of any component in the game.

{{todo|actually explain the placement, and provide helpful images}}

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Miscellaneous components]]

Chair

2025-09-09T04:38:05Z

Jimmy: fix category

{{stub}}

{{Infobox component
| title = Chair
| id = MHG.Chair
| caption = Chair
| configurable = 1
}}

The '''Chair''' is a [[component]] that [[Player|players]] can sit in.

== Behavior ==

When sitting in a Chair, you cannot move, but you can look around. You cannot build, but you can interact with [[Button|Buttons]], [[Switch|Switches]], [[Key|Keys]], and other Chairs.

== Configurability ==

The Chair can be [[Edit Component Menu|edited]] to change its color.

== Placement ==

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

== Gallery ==

<gallery>
Players sitting in chairs.jpg|A group of players sitting in blue Chairs arranged in a circle.
</gallery>

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Miscellaneous components]]

Flag

2025-09-09T04:38:04Z

Jimmy: fix category

{{stub}}

{{Infobox component
| title = Flag
| id = MHG.Flag
| caption = A green Flag
| configurable = 1
}}

The '''Flag''' is a [[component]] used for decoration, as a teleportation waypoint, and occasionally as a structural element.

== Behavior ==

The Flag's cloth flaps in the breeze. If a [[Player]] comes close to it, they can push the cloth around. Players can teleport to Flags where that's been enabled.

Any component that can be placed on top of a [[Mount]] can also be placed on top of a Flag.

== Configurability ==

The Flag can be [[Edit Component Menu|edited]] to change its color and its size. From this menu, you can also choose to show or hide this Flag in the Teleport Menu, and change its name within the Teleport Menu.

{{todo|screenshot of the Edit Flag Menu}}

== Placement ==

The Flag can only be placed in the center of a [[Circuit Board]] square or in the center of a board edge. Flags can be fine-rotated.

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Miscellaneous components]]

Category:Miscellaneous components

2025-09-09T04:37:18Z

Jimmy: Created page with "Category for components that don't fit into the other categories."

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

Singer

2025-09-09T04:36:43Z

Jimmy: fix category

{{stub}}

{{Infobox component
| title = Singer
| id = MHG.Singer
| caption = A Singer tuned to C4
| configurable = 1
| io.minInputs = 1
| io.maxInputs = 1
| io.outputs = 0
}}

The '''Singer''' is a [[component]] that plays a pitched sound when its input is {{on}}.

== Behavior ==

When a Singer's input turns {{on}}, it will start playing a sound. When the input turns {{off}}, the sound will stop playing.

== Configurability ==

The Singer can be [[Edit Component Menu|edited]] to choose the pitch of the sound to play and the instrument to use.

{{todo|image of the Edit Singer Menu}}

== Placement ==

The Singer can be placed the same way as a [[Peg]]: in the center of a [[Circuit Board]] square, on the edge of a Circuit Board, or on top of a [[Mount]], with 8+2 additional fine-placement positions on board square and edge. It can also be fine-rotated.

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Output components]]

Drum

2025-09-09T04:36:39Z

Jimmy: fix category

{{stub}}

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

The '''Drum''' is a [[component]] that plays an unpitched sound when its input is {{on}}. It is similar to the [[Singer]], but it cannot be tuned.

== Behavior ==

When a Drum's input turns {{on}}, it will start playing a sound. When the input turns {{off}}, the sound will stop playing.

== Configurability ==

The Drum can be [[Edit Component Menu|edited]] to choose the sound to play.

{{todo|image of the Edit Drum Menu}}

== Placement ==

The Drum can be placed the same way as a [[Peg]]: in the center of a [[Circuit Board]] square, on the edge of a Circuit Board, or on top of a [[Mount]], with 8+2 additional fine-placement positions on board square and edge. It can also be fine-rotated.

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Output components]]

Display

2025-09-09T04:36:33Z

Jimmy: fix category

{{Infobox component
| title = Display
| id = MHG.StandingDisplay
| caption = A Display with one input
| configurable = 1
| io.minInputs = 1
| io.maxInputs = 4
| io.outputs = 0
}}

The '''Display''' is a [[component]] used for displaying visual information.

== Behavior ==

A Display changes color depending on the state of its inputs. The color it chooses depends on its [[Display Configuration]], which can be set in the Edit Menu.

The Display changes color on the same frame the input (or inputs) change state.

== Configurability ==

The Display can be [[Edit Component Menu|edited]] to increase its input count from the default of 1 up to a maximum of 4.

In the same menu, you can select the [[Display Configuration]] for this Display to use. You can also access the menu for editing, adding, and deleting display configurations.

== Placement ==

When a Display has 1 input, it can be placed the same way as a [[Peg]]: in the center of a [[Circuit Board]] square, on the edge of a Circuit Board, or on top of a [[Mount]], with 8+2 additional fine-placement positions on board square and edge. It can also be fine-rotated.

When it has more than 1 input, it can only be placed in the center of a board square or on top of a mount, and cannot be fine-rotated.

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

{{Navbox components}}

[[Category:Vanilla components]]
[[Category:Output components]]