Have you tried pulling two different items, one or two belts each, in the same blueprint? I think interleaving two of these in a single blueprint might be significantly smaller than putting two copies of this end to end.

Have you considered parameterizing the blueprint so you can choose a new item all at once when placing it instead of having to edit a splitter then copy its settings each time?

This looks pretty neat. I have one question/concern though...

In the middle, there's one extra splitter not necessary to the functioning of the design here. It mixes the two temporary middle belts. I know that mixing sushi belts is generally good, but you aren't doing any other mixing here so this ...

I would love to be able to have this as part of progression in a mod pack.

Kudos to the devs for having a fallback mode to run on 1GB of VRAM (or less?)!

Syncing mods with a save and restarting will, by default, disable the debug adapter mod. This will result in the game failing to restart if you were previously using that mod and the relevant command line parameter.

The player has to find the debug adapter mod in the sync dialog and manually enable ...

protocol_1903 wrote: Wed Jun 11, 2025 6:01 amfor this and other scenarios like it

Elaborating on other uses cases would probably at least slightly increase the chances of something like this getting implemented.

If I had to guess, I'd say something on your computer is killing the process. I've never seen Factorio exit with nothing in the log to even indicate it's exiting, let alone why.

I only don't want to connect entities within the same blueprint. I still want to connect an underground pipe in a blueprint to an underground pipe outside the blueprint.

Also another mod can modify their cursor stack before I check it.

PS: And I'd really prefer to have discussions of the larger ...

Bump. After a long adventure through many layers of problems trying to get https://mods.factorio.com/mod/automatic-underground-pipe-connectors working using build_from_cursor instead of create_entity, I'm giving up and going back to the drawing board on using create_entity, and that means I need to ...

That's a remarkably short log. Do you see the same contents in the current and previous log files after encountering the problem twice?

OK, how about a more limited scope, *just* for entities being created by a blueprint?

That would be my strategy. Set a flag in on_pre_built, check the flag in on_built_entity, clear the flag in on_post_built.

PS: This is an XY post. The underlying problem/goal here is to place pipe ghosts on Aquilo with the necessary tiles under them. The broader inquiry into how to solve that sort of problem with that mod is at viewtopic.php?t=129325

PS: This is an XY post. The underlying problem/goal here is finding a way to prevent https://mods.factorio.com/mod/automatic-underground-pipe-connectors from building a pipe ghost between two new underground pipe ghosts in the middle of a blueprint placement. The broader inquiry into how to solve ...

When the player places a blueprint, one on_pre_built event fires, then one on_built_entity for each ghost that the blueprint creates.
This request is for an event that fires at the end of that process, indicating that the build process for the blueprint is finished. The event could fire for non ...

There are never events in the queue because there is no event queue [...] then runs over them 1 at a time I'm having trouble imagining how this can be true. Obviously I haven't seen the source code, but the only implementations of this I can think of involve access to a list of the entities that ...

Another approach to implementing this could be to start from build_from_cursor to make something like build_from_itemstack

My end goal here is to be able to visualize part of the game world mid-tick while debugging another mod, so I don't have to keep mentally processing the positions and directions of entities that are being modified during the run of a script. A convenient side effect would be getting that ...

Similar results could be had from another angle if we had a way to query the events in the queue. Something like game.get_queued_events returning an array of pairs of event type and event data, for events queued to be handled by the current mod that haven't been triggered yet. Then I could loop ...