Building off-grid entities changed at some point between 1.1 and now. The current behavior only attempts to place one when your cursor moves across a tile boundary, and if it can't place one, you "lose" out on the tile and have to move your cursor to a different tile for it to trigger again ...

For reproduction, place a single belt with an item on the left transport line, hover over it with your cursor, and run this command:

+1, this seems like a useful addition, I can see something like LuaTerritory::color working quite well, as well as LuaSurface::create_territory.color

Regardless of intent, this sound hurts my ears. It's perceptually louder than every other entity gui sound in the game, and I had to mod it to be silent.
I am not opposed to ghost gui sounds, however the current ones are not ideal.
I even thought I had a bug in one of my mods while updating it to 2 ...

This method works with LuaPlayer, but spawning a character entity and using it to mine a tile fails.
The description of LuaControl states "Mines the given tile as if this player (or character) mined it." which is the exact same as LuaControl::mine_entity besides the word "tile", and mine_entity ...

1. Please make the combinators fast replaceable.



Sure, requested many times (https://forums.factorio.com/83042). In 1.1, there was a mod by CodeGreen which worked perfectly fine, and its port for 2.0 by O5MO which worked with replacement from inventory but not from map view and/or ghosts ...

+1, I've resorted to a workaround by creating an invisible container with a weight limit of 0 on top of the entity so things interact with it instead, though an inventory with bar might be easier for that on second thought

Attempting to register a tree (not plant) to an agricultural tower with after it has done its initial "clear the area" phase succeeds, but the tower does not attempt to mine the tree, instead keeping the status "Item ingredient shortage".

I don't think many people will be doing a lot of category modification, and while it would be nice in that case to have a dictionary, it's really not that bad to do an array. If I were making a bunch of handcrafting recipes, I wouldn't want to have to specify {"crafting"} every single time, and that ...

front wrote: Wed Oct 22, 2025 8:42 pm Also, I think it was planned for 2.1 anyways.

Not necessarily. Only the splitting of the hybrid categories into their respective parts is confirmed, the unification of `categories` is an optional step 2 that I will only say was recently talked about not doing for fear of breaking changes.

With the addition of additional_categories for recipe prototypes in 2.0.49, there are now two places for recipe categories to be defined.
This works well enough, since it didn't break any existing mods using the category field.
For 2.1, boskid has mentioned he will be removing all of the hybrid ...

I'm surprised this isn't a thing already to be honest

Hi, great topic for a seminar! I started writing this before anyone else responded and then went to eat dinner partway through, so I may be repeating a few things from others.

- Most unexpected/surprising mod you’ve seen (or made) and why it stood out.
It's hard to pick a single mod out of the ...

Hi, one of the (unofficial) Factorio Discord server moderators here.
I only feel the need to chime in because anyone who reads this thread will only ever see one side of the story otherwise, which I don't feel is fair.
This will be my only message in this thread, I do not wish to continue this ...

Nice

minimal reproduction, stick this somewhere in the prototype stage:

May end up doing this myself, but figured I'd put it here in case someone else does it before I do.
Currently the only way to do this is with the console command /swap-players which calls Player::swap_players, but it would be neat if mods could do the same as well.

The request in this case is to pretend core has a version number for the purposes of the dependency, that way mods could use the dependency system as it is now to control the allowed engine version, instead of needing a new info.json field along the lines of factorio_version, or changing factorio ...

There have been a few times where I want to depend on a specific Factorio version, whether it's because of an API method that was added or changed, a new prototype type was made, or any other thing that would make backwards compatibility broken.
There have also been a few times where I've made a mod ...

Title says it all pretty much. The field says the dictionary is always present, and it is in fact not always present, specifically when the item prototype has no flags.
Thank you!