Having the "layer_group" available for read in control stage would make way easier to determine what kind of tile is being looked at, is it water? ground? zero?
As for "layer" it returns an uint that could make things messy with modded tiles, so i think the "layer_group" would make a nice addition

This is not serviceable in this exact case (on_tick script), it will definitely crash at some point

Indeed, i did try early on but i did write it wrong, the correct syntax is as follow

local fluid = entity.fluidbox[1]
fluid_input = MY_FUNCTION(fluid.name, fluid.amount)


probably need to add ...

If you want the input/output fluid of an assembly machine I'm pretty sure you should use the fluid boxes and not the inventory.

https://lua-api.factorio.com/latest/LuaEntity.html#LuaEntity.fluidbox


Indeed, i did try early on but i did write it wrong, the correct syntax is as follow

local ...

Do you really need the count? Otherwise, surface.find_entities_filtered will always return a table (which may be empty), so the wrapper around the for-loop shouldn't be necessary.


The script keeps scanning for entities (on_tick) and apparently COUNT is much more UPS friendly than FIND.
Runnning ...

Pretty straight forward, it was fairly easy to read contents for items using this bit of code, yet, i can't get it to work with fluids, what am i missing?

local count = player.surface.count_entities_filtered{area=DEFINED_AREA, type="assembling-machine"}
if count >= 1 then
for _, entity in pairs ...

SOLUTION:
To check if the slot is empty or not, valid_for_read must be used

playerarmor = player.get_inventory(defines.inventory.character_armor)[1]
if playerarmor and playerarmor.name == "Nameofsomearmor" then
dostuff
end



Jesus i did just the same without indexing [1]...

EDIT:
[1] refers to the slot iself so is never nil, [1].name returns the name of the ...

This is probably a dumb question, but, i can't find the right docs to address the armor slot in control stage.

This is what i'm trying to achieve

if event.created_entity.type == "boiler" and event.created_entity.prototype.fluidbox_prototypes[1].filter.name == "water" then
event.created_entity.insert_fluid({name = "water", amount = 10})
end


WORKED LIKE A CHARM! Thanks for taking the time to help me solve this, i definitely learned ...

https://lua-api.factorio.com/latest/LuaFluidBox.html
[...]
Are you trying it on boilers that are empty? From checking it myself, the fluidboxes are nil unless there is currently something in it.


That's exactly what i am trying to do, and yes, in the prototype the filter is defined as follow ...

https://lua-api.factorio.com/latest/LuaFluidBox.html

I don't see a 'filter' property on there at all - it's get_filter[index] to read a filter at the given index. The return is a FluidBoxFilter where 'name' would be what you'd check is == 'water'


I'm actually having a hard time in figuring out ...

What i am trying to achieve is to check if the fluid_box.filter [data.lua] value is water, then insert 10 water

if event.created_entity.type == "boiler" and event.created_entity.fluid_box.filter == "water" then
event.created_entity.insert_fluid({name = "water", amount = 10})
end

script.on_event ...

Then you did something wrong. What happens if you use a known good item like "rail" in placeable_by?


FOUND THE CULPRIT!!!

WANTED-ENTITY:

[...]
name = "WANTED-ENTITY"
flags = {"placeable-player", "placeable-off-grid"}
minable = {mining_time = 0.1, result = "ENTITY"} --drops the above "ITEM ...

You are doing the same thing the game does for curved rails. Note how the WANTED_ENTITY, curved-rail, appears in the preview but not in the Components box.

But you don't really want this, do you? You want each entity to appear as its own component.


Thing is that the entity doesn't appear at ...

https://wiki.factorio.com/Prototype/Entity#placeable_by is supposed to tell the game what to use in a blueprint for the given entity, so it might work for this. Haven't tried it myself though.

I was aware of this, but it doesn't seem to work, i tried any combination of "placeable_by" that's why ...

Hello everyone, this blueprint thing is really bugging me out, i have an entity-placeholder which on creation gets destroyed by the script in control.lua, and is replaced with another entity, though the script works, the script-generated entity is not blueprintable.
Is there a way to have the ...

Now i'm stuck with the last of problems which is merely cosmetic, though the code works pretty well, the recipes are now ugly AF, they show both 2x iron plate and 4x iron plate rather than six altogether as i originally thought, any way of merging the output without going onto data-final-fixes ...

Should be fairly straightforward.

Not quite. This will work for a recipe that you have just defined. But don't take for granted that it will work when other mods have had a chance to mess with it!

The problem is, recipe.results is expected to be a table of ProductPrototype . recipe.results ...

Should be fairly straightforward.

local function process(recipe)
if recipe.result == "processing-unit" then
recipe.result = nil
recipe.results = {type="item", name="processing-unit", amount=recipe.result_count or 1}
recipe.result_count = nil
end
if recipe.results then
for i,result in ...

Hello lads, basically what i need to do is this:
type = "recipe",
name = "MY_RANDOM_RECIPE",
--------[...]--------
results =
{
{type = "item", name = "iron-plate", amount = 2},
{type = "item", name = "copper-plate", amount = 2},
{type = "item", name = "processing-unit", amount = 2}
},
main ...