The two things I most want to see: do for trains what they did for belts, and calculate inserter arm positions only if the gpu or a mod needs them. For the inserters, the core sim can just keep a list of swinging inserters in a power net sorted by joules-needed-to-swing-to-target-position and dequeu...

I've tried in Firefox and Chrome Beta and Chromium, I can hit the "copy to clipboard" button on for instance GitHub and the repo url gets copied to the clipboard, but hitting the sweet blue BP button on this forum now does nothing. So it looks to me like there's something about copying to ...

Here's a two-combinator version (plus a constant) that works for any number of chests and item types. In the picture the fourth chest from the right is empty, so everything's waiting. So long as you have less than I think 13 chests you can unload at full speed. Number the inserters, set the nth inse...

I worked around it by mapping the real lctrl as the "hyper" mod, so long as there's only one physical key for each modifier bit the game works. Why this is so hard to handle in Factorio's engine but not for anything else on the planet, I have no idea.

Biters have constant issues, stuck against cliffs. That's part of the vanilla experience. It does not feel that illegitimate to ask for a better pathfinding, if only for Biters. They've got this game using every scrap of memory bandwidth available. Buff the RTS depth means nerf the logistics depth ...

The value of clocking the inserters is they don't check at all unless the circuit changes, which for full-hand clocks means every clocked inserter gets looked at 12 times less often than the inventory it takes from changes. Getting the inserter to check whether the available inventory's as big as so...

No, because productivity is always finite and the universe will end, or at least become unable to generate enough energy to run a PC, in finite time.

That's like saying a bicycle's better than a motorcycle because if you wreck you don't get hurt nearly as bad. It's better *by that metric*, but that's not all that matters.

Wiring up the lights to make pretty pictures of the data I leave up to whoever wants the fancy stuff bad enough to implement it, here's how you get however much of a circuit history you want to make pictures of.

One really cute way, given you've got 1-1 trains, is to have the stone train's locomotive in back, and the brick train's locomotive in front.

Well, if you want a circuit that does that, build it. But if you want to guarantee letting exact odd item counts through you're going to have to cut your throughput down to one lane or bulk up the build dramatically to add some error correction to it.

is it possible to add an arithmetic combinator which divides the input by two so as not to have to divide by two when entering the constant combiner ? Sure, but lots of recipes have ingredient counts like 3 and 5, and belts have two lanes. This is engineering-land, you're not going to get perfect. ...

I'm wondering, how is it that in your two creations the combiners output the value x2? Is it not possible to enter exact numbers and get this result as an output? That's the response delay, the decision to ask for more takes a tick, applying it takes a tick, so the tick after it decides to ask for ...

I haven't stared at it hard enough to be certain, but I'm betting it's that you reset to zero for every batch and don't remember strays, and your logic can't keep up, blue belt traffic comes at 2-3 tick intervals, your logic probably takes three ticks to react so it lets extras through sometimes an...

I haven't stared at it hard enough to be certain, but I'm betting it's that you reset to zero for every batch and don't remember strays, and your logic can't keep up, blue belt traffic comes at 2-3 tick intervals, your logic probably takes three ticks to react so it lets extras through sometimes and...

Here's mine, in two different layouts. Set the ingredient counts in the constant combinator, set the ingredient items in the <0 enables, turn on the constant combinator. Supply a nonzero Z on the red wire or turn off the constant combinator to stop after the next complete recipe batch. 0eNrtWF1v2jAU...

One way you could do this is to tie the stored credentials to the server, the password and the authorized user, so the server can see a hash code and verify that it's the hash code it would have given that specific user without giving away any secrets. The server can have its own secret id along wit...

If you disable the inserter before it actually picks something up, it doesn't pick anything up. From belts, it has to chase a moving item, that takes some time. This is a pretty brute force 7-tick pulse generator, toggle the constant combinator, sometimes the inserter manages to chase its target dow...

Please restore the function serializing on save. I use a global table to tie e.g. selection and timer events to the right response. I can't find any sane way to handle this, closest I can get is a separate ~on-reload~ table holding dumped functions, but I can't restore the gutted global table on lo...

Please restore the function serializing on save. I use a global table to tie e.g. selection and timer events to the right response. I can't find any sane way to handle this, closest I can get is a separate ~on-reload~ table holding dumped functions, but I can't restore the gutted global table on loa...