Can't you just read that from the player's LUAEntity?

allow_dispatching_robots

There's a discussion board on the mod page you can post in: https://mods.factorio.com/mod/swarmageddon_20/discussion

By default, mod authors get notifications sent to their email when a new thread is posted. At least in my experience.


That was one of the first things I looked at. But the ...

There's a discussion board on the mod page you can post in: https://mods.factorio.com/mod/swarmaged ... discussion

By default, mod authors get notifications sent to their email when a new thread is posted. At least in my experience.

I would've thought the second one would work too, but unfortunately its not what I thought the issue was. I don't see anything in the code that should change how it works just because there's another recipe added.

Maybe someone else will have an idea.

You can disable blinking of icons entirely with an option, I think under accessibility IIRC. Nothing that lets you change the timing - mod api support for it was requested forever ago.

Your images show that you can in fact make iron gears or chests from the compressed iron, even when compressed gears exist, so the recipe can be used as an intermediate regardless.

What happens if you have only 1 compressed iron and 1 compressed gears in your inventory? Can belts be made then?

If ...

Does the disabled_by_script property not work for that? Far as I know it disables animations too.

I just edit the title with [DONE] or whatever to mark things done.

Looks like it's just a UtilityConstant - max_fluid_flow

API documentation exists at https://lua-api.factorio.com/latest/index.html - there's a link at the top of the page. All the available modifiers are at https://lua-api.factorio.com/latest/types/Modifier.html - if it's not listed there, it's not possible to do it via technology effects.

There's no ...

Can someone please elaborate on where to find this 'hidden setting to revert to OpenGL'? I'm hoping / assuming it's a command-line flag or config file that I can edit manually, as like I said -- I can't even launch the game post 2.0.68.


https://wiki.factorio.com/Application_directory lists ...

protocol_1903 wrote: Sat Sep 20, 2025 9:50 pm They specified data stage, not control stage. +1

The description says it's used in ALL stages - settings, prototypes (data), and runtime (control). The description of the for_player parameter explicitly lists the other stages.

AFAIK that non-equal check is for the QUALITY of the yumako, so its filtering for non-common yumako to the right side. Its all common, so none is going to the right.

If you want all yumako going to the right regardless of quality, there's an 'any quality' setting.

decorative_removal_probability is only on Tile prototypes, not entities.

Entities have remove_decoratives and rail prototypes also have removes_soft_decoratives

Are you sure it wasn't the game-wide setting for spoiling rate being changed? That wouldn't show up on the item, since it's not a change to the item. If it's EVERY item, that's likely the cause.

For now, there's options for transparency and scaling in the mod I wrote before disabling blinking was an option: https://mods.factorio.com/mod/No_Power_Icons . I added it because people requested it specifically for making recipes/filters visible.

Are you saying you want production to work the same way as now, except that items with a lower quality than the cap...just don't get produced?


OP asked for the other way around. If the cap is set to rare, and an epic part was rolled, it would be reduced to rare instead. They did not specify ...

Hi, Can someone explain this part to me?

local resource_autoplace = require("resource-autoplace")
...
autoplace = resource_autoplace.resource_autoplace_settings({ ... etc ...})

where does that "resource-autoplace.lua" file come from?


It's part of the base game. There's a few lua scripts in ...

SaboteurKiev wrote: Fri Aug 08, 2025 6:00 pm It would be ok, if they just stop moving., but i want to say that they are swimming and grouping near some "vertical" lines.

Those are chunk boundaries. When they move into the chunk outside the radius where they're active, they stop moving, so many can pile up at the boundary.

Neat. Looks kind of like a miniature bastion fort.