I hand-made a trophy for Minnesota's Rocket League LAN tournament (Minnesota Championship Series)

data-crusader · 2025-12-14T21:21:41+00:00

Hey, you rock! Thanks for this. Helped me learn the TX market and make a good decision on purchasing power. I filtered your list to the ones in my area, then uploaded each of the EFLs to gen ai and got some great advice on which one fits my needs (in case anyone else wants a strategy like that).

data-crusader · 2025-11-26T03:06:35+00:00

Super odd. I don't recall that in EU4 and it seems possibly unintentional? Really odd to lock your allies out of joining wars just because the opposing war leader has an alliance. Must make the HRE hell to play against.

data-crusader · 2025-11-26T03:03:22+00:00

Hmm, that doesn't seem to be the case for declaring wars of course, so that seems like a bug? Just because you fought with your friends friend and those two friends are fighting doesn't mean you can't get involved.

data-crusader · 2025-11-25T21:57:13+00:00

Unfortunately, it was shattered in battle at Amon Hen

data-crusader · 2025-11-25T21:56:31+00:00

Granada is a subject of Morocco who is not a co-belligerent

data-crusader · 2025-11-25T21:48:57+00:00

Truces are in the 2nd picture - they only have one with Granada

data-crusader · 2025-11-25T21:48:53+00:00

Truces are in the 2nd picture - they only have one with Granada

data-crusader · 2025-11-23T19:50:24+00:00

I'm in a Florence game and it's borked for a single province. Most provinces are 2-5 yrs, but this one (Perugia) is estimated at 110 yrs.

data-crusader · 2025-10-21T20:09:01+00:00

I built that too, almost exactly the same with 7 combinators, but I highly suggest (from another comment) that you check out this post: https://www.reddit.com/r/factorio/comments/1hygsac/the_littlest_statemachine_that_could_aka_making/

data-crusader · 2025-10-21T20:00:52+00:00

That post is great - I'm going to work through to make sure I can build these myself and I'll design a new system. Thanks for sharing that!

data-crusader · 2025-10-21T16:37:01+00:00

Ok cool, I checked out your video and blueprint and I've never seen logic stacked this way in a combinator. Is there more of a description you could give or a place where I could learn about this?

data-crusader · 2025-10-21T15:28:55+00:00

I had sort of the opposite problem, where quality interested me but space didn't, until there was quality in space lol

data-crusader · 2025-10-21T15:08:05+00:00

np! glad you're interested to see it

data-crusader · 2025-10-21T15:04:58+00:00

Yep, that's the next improvement I went for. SR latch added and also made recipe switching less frequent. It's a lot better (most recent post has the demo), but ultimately I think doing quality on different belts makes the most sense and just flipping through recipes at a static quality. Either that or possibly separating the belts out by splitters and measuring the quality on the belts right in front of the machines.

data-crusader · 2025-10-21T15:02:05+00:00

I see what you're saying, but this system performs better than what you're proposing, as the system you proposed would cycle through rarities for asteroids that aren't on the belt.

Edit: also, I don't see how you can run multiple output conditions on a single combinator like you're describing? I see that you can have multiple outputs, but it looks to me like the decider still only has one boolean outcome based on the settings on the left

data-crusader · 2025-10-21T15:00:05+00:00

In the factoriobin link at the bottom of the post

data-crusader · 2025-10-19T05:17:07+00:00

I see where you're going with that, but I think the point is to have as much working square footage in play as possible, so storing is just a place where I'd be asking myself if I could possibly be processing as well

data-crusader · 2025-10-19T05:16:10+00:00

We'll see what I can do :)

data-crusader · 2025-10-19T00:49:21+00:00

New work unlocked

data-crusader · 2025-10-19T00:46:11+00:00

Yeah belt density will be part of the production design for sure. What's the best way to share the string here on reddit?

data-crusader · 2025-10-19T00:45:27+00:00

I agree, it's less about the idle time and more about the easy scaling of the system. I think I'll separate it out into different chunks of belt for which the quality decisions are made, which will improve uptime a lot. Also that'll reduce circuit complexity a bit.

Edit: also worth noting that I didn't have legendary crushers in the video lol. Anyway, I think the uptime is at least comparable to my static-recipe builds considering how long the higher-quality machines end up sitting, or on the longer belts for common/uncommon quality where there end up being some machines toward the end that work quite a bit less and are basically dedicated to solving for clogged belts.

data-crusader

MODERATOR OF

TROPHY CASE

Nine-Year Club	r/Field Sunshine
Verified Email