mudcrabempire wrote: ↑Sat May 25, 2019 4:44 pm The "long, thin leg" patent which is typical for many insects (insects are small!) simply cannot physically support creatures of that size.

what makes you think that gravity is anywhere near earth like?

It's not doing source "script". Its a markup language , referring to the markup source as script is correct usage of the word, its not a full programming language but it still uses text based (ie script) markup to convey additional information (I want an icon printed, not the text itself)...

wheybags wrote: ↑Thu Mar 21, 2019 2:17 pm We're not savages, we use std::string :p

ahh uncontrolled allocations and heap fragmention it is then!

(I joke, I joke! )

It's not really a bug, and the character count for each image tag is not likely to change, but we will probably bump the limit to account for this. Ideally the intuitive behaviour would be for the limit to apply to the rendered characters (ie icons) rather than the source "script" since a...

Why is this considered not a bug? Because this issue is apparently on edge between "Won't fix." and "Not a bug". I would classify it rather as "Won't fix.", but impact of this classification is minor. I dont understand. I dont understand why its been deemed that the FI...

Technically speaking not a bug, as it's working right now per design. So it's a design flaw in the train prioritising calculation for circuit-controlled signals. A bug isn’t only when the implementation doesn’t match the design, the design can be “bugged” too. Right now it’s inconsistent, unintuiti...

Are you using the in game clock mod to see the time of the day? Other than what clocks we make from circuits and the day/night cycle, there is no indication of units of time passing in game. You’ve assumed that in game time is sped up up somehow, when that assumption is baseless. Physically the plan...

Why is this considered not a bug?

Ok after doing some more testing with a constant combi hooked up the that bottom signal and manually toggling it on and off, it seems like when a signal goes green from a circuit change the train with the lowest train ID is released. When the signal goes green "naturally", the longest wait...

Removing the circuitry on the bottom fixes it. Yup, I confirm that, also I just noticed that the 2 trains that get stuck have the highest train IDs for them all. So is this a bug? Shouldn't the train that gets picked be the same whether the signal is circuit controlled or not? (I'm only controlling...

I always end up with 2 trains that sit and wait in stacker forever. The left station is unloading the petrol, the top 2 stations are just fillers to test the setup. The bottom circuitry is a simple latch to hold the red signal closed unless petrol < 30k IIRC, the top circuitry is just to prioritise ...

I was playing around with a prospective stacker design and noticed that in the version built around chain signals only I ended up with some trains that always lost the race for a spot at the real station opening and sat there waiting forever in the stackerwhilst newer trains arrived and jumped the q...

You would have to manually construct a signal with everything set to 1 (eg by chaining constant combis with a batch in each) then you can subtract your input signal from your “all signal” wire (you want -1 in each of your input signals) and anything that’s > 0 will be your result. You're assuming th...

To make things more confusion, this is not the case when providing the player with items from the Logistic Network, you will always provide the exact number you request (to prevent overfilling stacks and flooding your inventory I guess). Are you sure on the last part? I haven’t tried on 16.x but on...

The left-most splitter is already receiving 40/s to which it can distribute its items, meaning that there's nothing to split. Instead, it becomes a merger but there's nothing to merge because, it is receiving 40/s. Its not receiving 40 items/s it's receiving 60 (although it doesnt know that, all it...

Splitters cant feed information back up the production line, your logic is that since there is only output for one belt, then the bottom splitter should use the entirety of the bottom belt and let the top one "spill out", how does it know which of the 2 belts its supposed to take from? You...

It probably makes little difference to belts as a transport medium, but it really hurts belts as a communication medium, I was experimenting with encoding information in belts and the conclusion I came to is it’s just not worth playing with in its current form. If nothing else it just looks kinda ug...

845CD350-8394-4674-917B-3E2EE950B3CE.jpeg This is what I use, it gives a running average over the interval specified, in the example here 60 ticks means it shows the items per second averaged over a second. If you wanted items per minute averaged over a minute then change all the 60s to 3600s. If y...

So the problem is priotity splitters dont do that great of a job at full belt speed with a pulsed input since it has no buffer. Probably the most likely time you'll encounter this is an unloading station and high inserter stack sizes, and you want to maximise unload speed to belts. I was playing aro...

In my case I'd like a slightly different behaviour as an option, what I'd like is the priority output for one resource to be in one direction, and the priority output for the other to be the opposite. For an input that has exactly two different kinds of items this is exactly how it already behaves ...