So a "food court" in the "mall"

Hi, I'm working on a mod that redefines `assembling-machine-1` to have fluids. This means we are adding the crafting-with-fluids category to the base list. Assembling machine crafting categories in base are defined here: https://github.com/wube/factorio-data/blob/8c59a0299bab069efbd0a11e1107245b6264...

Sorry to necro, but this happened with baketorio by butteredcoffee. I'm updating it for 2.0 right n ow.

TL;DR Adding resources in a mod generally requires adding an autoplacer. This could be simplified with optional parameters to AutoplaceControl . What? An AutoplaceControl is always going to need to be associated with some planet, whether additional or not. Having a "planets" parameter in ...

So it is interesting now. Everyone who plays on my server (Australia, Russia, USA within 50 miles) has no issues, but whenever I join, I lag out and stutter.

I have a feeling these are all related, but different, issues, so I was going to try again once we hit 2.0.

Thanks for the highlight of that note -- much appreciated. I still see this as more of a bug than technical help at this point.

That's fascinating-- were you able to bring the speed back after a reboot or link reset (down/up)? I'm going to try this locally

I completely forgot we had another thread for 1.1.39, but same issue. viewtopic.php?f=49&t=64312&p=552651#p552651

I'm running headless Factorio on a 6-core container on Proxmox on a LAN, and max out downloading the map at between 7 and 8 MB/s. I was wondering if this is expected, or if I should be seeing something faster? The server doesn't look too heavily loaded, and I'm the first person joining. Happy to do ...

We're also seeing a drop from 9.8M down to 1.2M since the most recent update (1.1.39) on a headless server. All our speedtests are showing much better performance (350M+/350M+).

We were running solidly on 1.1.36 with players in the US and Australia, but after upgrading to 1.1.37, our Australian player keeps getting dropped with a server heartbeat error that spams the log. While we are running SE+K2, this error looks to be something different. It almost looks like after a mi...