Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
Its great, you dont have to build every solution on your own.
(I am We are Borg)
Its not uncommon as programmer to use already programmed code.
https://steamcommunity.com/sharedfiles/filedetails/?id=1427054642
https://steamcommunity.com/sharedfiles/filedetails/?id=1427059229
Bob's mods + Factorissimo2 + Warehouse mods make for some interesting possibilities without requiring miles of space.
This is my favorite blueprint on the site: https://factorioprints.com/view/-KnQ865j-qQ21WoUPbd3
Next time I do it, I'll design my own, perhaps learning from the layout I copied.
then eventually we'll reach the ultimate blue print of perfection.
and then improve it!
One thing to bear in mind when dealing with stateful logic (feedback loops) is that you can't be sure of the order in which combinator outputs will be updated. So when the output of one combinator connects to the input of another, the value seen by the second might be before the first has been updated for the current cycle, or after. This can be a significant issue when handling single-tick pulses like those generated by reading belt/inserter contents in "pulse" mode.