I've been fiddling with things a little (scaling the vanilla turrets, and ending up with rather absurd numbers); as far as I can tell, there is an offset above the centre point of the turret (in tiles), and a radial offset from the centre point (also in tiles, I think), which is rotated with the tur...

So, a bold search and destroy would look something like the following: s/get_inventory\(\s*defines.inventory.(?:player|god)_main\s*)/get_main_inventory()/g; s/defines.inventory.player/defines.inventory.character/g; s/power-armor-2/power-armor-mk2/g; s/personal-roboport-equipment-2/personal-roboport-...

If your mod derives new things from old things, you have to either: run in data-updates, depend on every mod that could possibly define a new thing you derive things from, or provide an API for other mods to register their thing with your mod. All of the compression mods, for example, have this natu...

Much nicer, thank you. =)

That's why I suggested Scanning Radar as well; it provides a 'radar', that does all of the work via scripting in order to scan a circular area, rather than a square area.

You could look at how Scanning Radar or Big Brother do things?

What are you using now? Shouldn't a simple-entity-with-force be sufficient to make turrets attack it if in range?

Actually, it should work, most (but not all) of the tall entities have a selection/collision box centred around the base area. Power poles, for example, have a collision box that's centred around their base area, so scaling the entity image from icon-size to entity size around the centre of entity s...

That's just what I was looking for, even if the mechanism is nowhere near as complicated as what I first suggested.

They already can?

I added a burnt_result_inventory to a train, and it works just fine.

Nuclear reactors work as expected, I believe.

What I think doesn't work (well?) is having an output inventory and a burnt result inventory.

Fairly certain I saw a mod go past that does just that. I'd suggest looking at Recursive Blueprints or Ghost Scanner, which are both similar in nature. I think that one of the Picker mods might have this function?

Worse; for many entity types, a blank description results in an auto-generated description, and there's no way I know of to add to it, you can only replace it.

Edit: fix tyop

What if the end of a belt is always raised? That should look okay too.

Alternatively a belt that just ends wants a fence to stop the items falling off.

Could also be squeak through; if there's enough room for the player to squeak through the field of solar panels, there's enough room for a tree to remain standing, if it's in just the right spot.

The only problem here is the "set stack size" part. If you use several items you need to calculate a minimum which is really, really hard to do with combinators. IMO it is not worth the effort. I'm reasonably certain that the stack insert only accepts one filter slot, and uses the signal ...

Ideally we shouldn't need to do any lookup at all. Instead it should be sufficient to go: new_recipe.localised_name = { "", { "description.My prefix" }, { "recipe-name." .. recipe.name } } and have the runtime lookup what recipe's localised name happens to be, regardles...

Is main_product now mandatory if you define the (singular) result of a recipe using results? What did you do? To make my code simpler, I normalised the definitions of any recipes I'm about to process, for example: This is the original recipe: data:extend{ { ingredients = { { "wood", 2 } },...

On a side note: How does the game handle the case where a shooting speed research is so high it should result in more than one shot per tick? It's odd to me that these aren't capped at 1/tick. There's a comment on cooldown between attacks that suggests if the cooldown is less than a tick, you fire ...

um. there's now oodles of different mods that do this very thing that you could have a look at for an example of how to do this. Probably one of the most comprehensive is omicompression, which compresses everything; there's the various automatic barrelling mods (which aren't updated, now that barrel...

I think a usual design is to have a constant combinator with the desired contents of the train; subtract current contents of train from desired contents, send that to a set of filter stack inserters which are configured to set filter and set stack size That works nicely with one train car, but not ...