How about setting a "mod_raised" entry in event tables passed by mods, the name of the raising mod? Mod authors could then cheaply blacklist or whitelist or whatever to avoid trouble.

@quyxkh: Inserters don't swing in a perfect arc though. They chase items on belts and sometimes wait for the source/target to become unstuck. Does that still work? Worst case this only works for container-to-container swings, but I don't think inserters recalculate their target mid-swing, I think i...

That 92% touch-count reduction kept my monkey chattering until it came up with this: Swinging inserters go on a head-tail queue, simplest might be one for every connected-power-grids and delivered-joules-required combination. The list anchor has a what's-on-the-list summary and a count of how many j...

Yes, once you've got red/green science solved, the next challenge is to skill up so it's not just solved, it's trivial. Blue and gray demand some real competence at small-scale production and pose new problems for design, then purple and gold do it again with even more new problems to solve. If you ...

I don't understand

we have no way to verify anything given to us from script.raise_event

at all. It can't mean "we have no access to the arguments", it can't mean "we can't read or check the contents of lua tables". What can you do with burst parameters that you can't do with table entries?

While I'm happy to see my map up there like that, and your ratios are much closer matches to the ones I get, I have to caution that the all.trains map in particular is bursty, and its first couple of minutes are in one of the ebbs, it's producing about 95-96k/min chips for that interval.

Power-out's already an exceptional condition, right? Worst case, in a brownout you have to fall back to per-tick inserter updates, I'd think it's just whenever the power supply changes that you have to recalculate the swing.

Top lesson from the UPS Wars threads hasn't changed: inserter swings almost completely dominate production cost. I suspect it's because the engine updates the inserter arm position every tick, but why? There's no collision checks, arm position mid-swing is there for us humans to look at, right? So h...

So, these aren't enough to vault me onto the leaderboards but I think they'll, uhh, carry their freight here. UPS.Wars.3.quyxkh.clocked.dispatch.pickup.trains.zip UPS.Wars.3.quyxkh.clocked.dispatch.all.trains.zip So I was thinking, why chase after every scrap of production and then try to control de...

I don't see any material difference between checking the arguments when script.raise_event() gets a predefined event number and refusing to allow scripts to do that but then offering alternate ways for scripts to do exactly that.

Oh.my.god. They're _clocking the output inserter on a boosted greenchip assembler_. And it's working. I trust at least some people besides just me will get a laugh at how chagrin-inducing this is for me. At least I know why I didn't think of it myself. I'm not going to try for Allaizn's mark, I choo...

A note: i was just so proud of myself when I figured out how to lose the internal buffer chests in my layout. Learned two things: (1) it's _slower_, and (2) long stretches of open belt seem are not negligibly cheap, replace them with neathie pairs for a noticeable bump. I won't make DaveMcW time the...

I started out with quyxkh's design and initially only wanted to make a few minor improvements, but I ended up rebuilding most of it. I loaded it up and the instant I saw your production cell I knew I was beat. quyxkh: "I don't need no stinking cars". allaizn: " this is how you use a car." Everythin...

Okay, here's a second tuneup, stripped the rest of the excess capacity for an extra few percent and made the layout a little more retry-friendly just so it looks better while running, the retry dispatching itself is better than anything else I've thought of to try. Dedicated trains = excess capacity...

Here's a first shot at it, it's not pretty but it seems to be playing in the right ballpark. Perhaps notable, it uses cs5.5 assemblers, and trains. I love trains. Screenshot from 2019-10-30 08-05-06.jpg snap@T4045343=8784x14192+1058-109.75,z2.jpg edit: added a ~5% tuneup, stripped some of the excess...

You're using Dijkstra even for single-stop stations?

Apple is mostly great at making popular already invented technologies (by, among other things, mercilessly cutting anything not deemed important to the design). To be fair, if you don't know what to do with what you've got, what's the point? Xerox had no fucking clue. Jobs knew what he was looking ...

When I want a power drain that will draw down accumulators I use a Big Bank o'Beacons.

fuel drop off stations […] that is simpler than running a logistic signal True, but you can't retrofit additional fuel-drop stops into existing designs, this fits into many existing stop setups. I do lean to the wildly-overengineer-everything-then-boil-out-all-the-nonsense style and that design bar...

[…]it's arguably better to have a bad experience than none at all. Sure, if you look only at the good parts for the four people who might run this, but the pain/gain ratio for development work on it, considering everyone affected, is all but literally insane. Work the devs do on the x86 build helps...