For the technology issue, do you have specified the recipe twice as unlock-recipe?

I thinked of this when doing a mod. The problem is that entity "upgrade" is not always a compatible upgrade, specially underground belt, if you paste a blueprint that do underground belt spaghetti, and downgrade all of them to the same underground tier the blueprint will not work. Also range of ...

Are all the requirements met mentioned in https://lua-api.factorio.com/latest/pro ... xt_upgrade?

robot256 wrote: Tue Dec 30, 2025 8:20 pm What about assigning the ghost entity to a dummy neutral force?

You know, this is the solution. Thanks a lot! I don't even need a "dummy" force, just setting the ghost to neutral makes the logistic network not trying to deliver items.

For internal reasons, I have an entity which I create as a ghost and destroy it usually. To make it placeable as a ghost, I had to create a dummy item with place_result set to this entity. However, if this ghost is placed inside a logistic network, it shows that the ghost is missing materials for ...

I created the mod. It was not as complex as I initially thought:
https://mods.factorio.com/mod/blueprint-auto-downgrade

I'd be interested in (co-)developing such a mod. My idea is to provide a dialog upon placement, if one of the entities is not available in the logistic network. Then for each of those entities (maybe also include a check if available entities >= amount needed), show possible candidates to replace ...

Whatever is best for UPS. I'd say only a few mods use the undo/redo API at all.
For me, as a programmer, it is more useful (or convenient) if entries of an array of UndoRedoActions really are UndoRedoActions (having a type and some data). If you decide to leave it as-is, please add a hint to the ...

So, looking into this - a given undo item can have several actions in that item and one or more may be invalid. When pushing the structure to Lua the push logic will skip invalid entries however it still increments the index that it uses to put the undo item actions into the lua table.

I can "fix ...

Can you provide a save file created between steps 3 and 4? i am unable to reproduce any issues and i suspect i am misunderstanding which actions are super forced or normal or ghost or blueprint builds.


Rotate the belt in the cursor so that is is not facing north. Place it where the ...

Steps to reproduce:
1. Build a belt
2. Super-force build a splitter (belt is now marked for deconstruction and splitter ghost is created)
3. Place the belt again in another direction on the same position (splitter ghost is removed)
4. Print the last undo item. The first entry is nil
/c game.print ...

The only event that is fired related to that is on_player_cursor_stack_changed when you insert a non-ghost module

Steps to reproduce:
Use the mod I attached. Place 2 electric poles and connect them with red or green wire. Then press Ctrl+Z. The floating text states that the connection was undone, but no chat message.

When I disconnect a wire connection by script the next tick after it was connected and I want ...

I figured out that the tiles of the other planets do not use the elevation variable inside map_gen_settings. If you check planet-fulgora-map-gen.lua and tiles-fulgora.lua (other planets accordingly), you see that the usey a funny mix of everything.

Even modifying the "fulgora_elevation" property to ...

Relating to https://www.factorio.com/blog/post/fff-402. When using set_blueprint_entities, even without modifying anything, it forgets those wire connectiong going to external entities.

script.on_event(defines.events.on_player_setup_blueprint, function(event)
local item = event.record or event ...

Maybe https://lua-api.factorio.com/latest/eve ... gui_opened?

Usually, techs "disappear" when there are modified/replaced by a mod, which is subsequently deactivated.
If you started playing with a mod that changed or removed the tech, and decided to deactivate that mod, then you get this result.

Can't guarantee it's the root cause though.

[Edit] : This ...

What do you want to achieve exactly?

You can also run migration code in the on_configuration_changed event after checking if the buggy version of your mod was NOT installed

Also pyrawores does that with e.g. aluminium rock. It's basically a very low spawning probability