There is spreadsheet at https://docs.google.com/spreadsheets/d/1p7XRA4jIjK3tszJMIE_DlHvRJmQvp_6RukfNdcuwuPs/edit?usp=drivesdk but I don't think it's updated.
And if you check the first post in this thread the intersections should be there as well, but since we're discussing new categories it isn't ...

My advice is to never downgrade Factorio versions.

It happened to me as well, I used viewtopic.php?t=94427 to get my blueprints back (had to put everything in the same blueprint book though).

Oops I also posted this one incorrectly, I meant to post this as a bug report. Can it be moved?

Oops, I mean to post this as a bug report. Can it be moved?

I was playing the game when it crashed while auto-saving. I have attached the autosave, previous autosave, dump, and log.

After Factorio crashed, I restarted it and continued playing from the previous autosave. I increased the autosave frequency from per 5 min to once per minute, but no further ...

Steps to reproduce:
1. Load the attached save file.
2. Make sure "show decoratives" is on.
3. Make sure you are underground.

What happens:
Small colored rectangles appear on the screen briefly at random positions. They continue flashing/blinking when the game is paused, and zooming out let's you ...

Huh, makes sense that it is intentional. Different colors can also help to find things more quickly in the factory (assuming the player has played enough Factorio, and tends to use a consistent tier of buildings).

Also, as to thing X (refinery, train...) not having a higher tier, I like to think ...

Makka77 wrote: Fri Feb 28, 2025 12:32 am Ever since the FFF with this video...

https://www.youtube.com/watch?v=CgMV2dFFdFE

Those aren't unit tests, they are integration tests.

An event on_signals_changed is not the same as a readable value /attribute is_signals_changed, I thought this thread was about the latter.

Hares wrote: Thu Jan 08, 2026 8:38 am However, the whole purpose for this request is to not perform on_tick events for each monitored network.

I'm pretty sure this request won't change that. You'll still have to check the value of is_circuit_network_changed every tick, it's not an event.

One problem I see is that you use the any-fuel wildcard, but want it to react to the train's cargo. I don't think this will work (this was also mentioned in the other thread.).

Also, can you confirm that the triple-wildcard interrupt works if you don't use dynamic train stop limits or priority ...

Any chance for Factorio 2.1?

Thanks for the reply. I found a workaround by editing the info.json so that one of the mods isn't loaded (insert extra semicolon somewhere).

I get the same error without using Docker, is there a way to solve this? I would like to keep multiple versions of the mod in the mod folder, like you can do with normal mods.

Minor issue, but the collision box for the new curved rail is offset to one side too much imo. Looking at the gravel, it seems like the underground belt should be fine there, and the edge on of the collision box below the rail is a lot closer to it than above.

afbeelding.png

The underground belt ...

Thanks for telling me. I've changed the thread title so its clearer. I didn't know that Switch-Switch local multiplayer existed since I don't play on the Switch much (I could have guessed, since I know the DS has it).

TL;DR
Add local multiplayer/coop to the Switch.

What?
In addition to the normal "single player" and "multiplayer" options in the start menu, add a "local multiplayer" option. Selecting this option allows 2-4 players to play Factorio on the same Switch device when it is docked by using multiple ...

when it comes to setups involving side-loading, and splitters, and circular belts, there is no perfect "front" belt.


I don't quite see how side-loading and splitters preclude having a natural update order, but I agree that there's no way to fix looped belts. From what I understand, the lanes ...

Since now the highest preforming intersections are now larger than 1.1 intersections and perform worse then the best 1.1 intersections.

The 2- and 4-lane bilevel 2.0 intersections have higher scores than the corresponding buffered pre-2.0 intersections, so what you said isn't quite true (for ...

Sad, but thanks for considering it.
I have found a workaround that seems to work: super-force-build the blueprint on top of the ghosts after placing it once.