I think that does exactly what it says on the tin. To emulate pasting a ghost upgrade over an existing entity you want to do:


local entity = game.player.selected
entity.order_upgrade{
target = "steel-chest",
force = "entity.force",
player = game.player
}


Now, if you are wanting to brute ...

Loaders ignore the automated insertion limit and will fill up an assembler to the the hard limit (stack size + 4 * hand-stack) (iirc).

It was eluded to in https://forums.factorio.com/viewtopic.php?p=668370#p668370 that this might be something deserving of a "fix", thus I'm posting this as a bug. If ...

A loader attached to an asteroid collector will (if full) initially output to both lanes of a belt. It will stop outputting asteroid chunks if one lane gets backed up.

Conditions:
- One lane is backed up / blocked. See attached screen shot.
- Initial flow on free lane is interrupted (empty ...

This should be moved to resolved. Was fixed in 2.0.57(2.0.56).

129343

In 2.x a logistic section can only contain a given filter once. For historical context, 1.x allowed duplicate signals to be created in a control behavior and it summed the values. This now happens between duplicate signals across unique logistic sections on the same combinator.

The built in chooser ...

I believe this is only a minor cosmetic issue, but figured I'd report it anyway.

When doing game.print() on a LuaPlayer object it pretty prints some of the members (index, name, controller, position, surface, and connected). In that display it shows the index as '0' when the index is actually 1. If ...

Look like a similar thing to viewtopic.php?p=662942#p662942 where LuaRecord::contents was being created as a compacted list without keys which resulted in LuaRecord::get_active_index() to point to non-existing keys in LuaRecord::contents.

I'm not sure I understand your response here, as it really doesn't apply to what I demonstrated.

Are you saying there are two different formats with in 2.0.35, or that 1.1.x and 2.x are two different formats? If it is the latter, yeah that's clear. What isn't clear is why 2.x generates two ...

A 1.1 blueprint in a players storage, game inventory, or game library are all converted upon load into 2.x. Filters in constant combinators have their location (index) changed. All filters in the combinator are compacted into a 1 indexed, sequential list with no gaps. If you export that BP on 1.1 ...

This is a crash of the factorio binary after an error in a mod crashes the mod / save game.

It specifically happens when attempting to update a blueprint in a players library, and not when attempting to update a blueprint in the game library. While attempting to update the BP in the game library ...

LuaRecord::get_active_index() was added in 2.0.29, presumably to allow working with blueprint book stored in players or game libraries. This LuaRecord is also now ( 2.0.34 ) the way we interact with updated blueprints in on_player_setup_blueprint (https://forums.factorio.com/88100).

If picking up a ...

+1

Wholeheartedly yes. This capability from Recipe Book is sorely missed.

Koub wrote: Sun Dec 08, 2024 9:11 am [Koub] Merged into an older thread with the same suggestion.

@Koub

Which conversation did you merge this into. I think viewtopic.php?f=6&t=123696 used to be one, but it appears to have been removed.

It doesn't need to be official, but more just officially recommended as the one and only "enable feature flags" mod so there's only one mod that other mods need to check for and there aren't fifty different mods for the same thing

Why would the other mods be checking for a mod when they should ...

Exactly. If there are only non-SA mods enabled, SA binary will behave exactly the same as non SA binary to make it possible for MP games to be possible between SA and non-SA binaries. As such there is nothing to change here. If all features would be enabled by default in SA binary then cross ...

The idea that certain engine capabilities are locked behind feature flags is a great idea and I support their use. Where the current implementation falls down is an inability to interrogate their presence.

The current implementation of feature flags does not indicate weather or not a feature exists ...

robot256 wrote: Thu Dec 19, 2024 5:55 pm Good catch. FYI there is a separate subforum for documentation issues: viewforum.php?f=233

Bah, yeah, this should go there then. I figured there had to be. I was looking in the wrong parent.

The surface.create_entity documentation indicates that the 'filters | request_filters' keys take a parameter of type 'array[InventoryFilter](?)' when the type is inserter, loader, or logistics-container.

logistics-container:
request_filters :: array[InventoryFilter]?

loaders:
filters :: array ...

Thanks for the added explanation. Was just wrapping my head around that and doing the additional maths too. I understand now. Thanks for putting up with me.

But all the different speed loaders should show the same value? Was that a compromise that came in with the fix for 118529? Prior to that the showed reasonable values.