meifray wrote: Wed Oct 15, 2025 6:08 pm is it usable in vanilla modding?

If my memory serves me right yes, its just not been done yet afaik. You obviously can't rely on the space-age graphics for your own fusion prototypes then.

FYI fusion-reactors & generators are not locked behind any feature flag

I ran across another couple of doc issues in continuation of https://forums.factorio.com/131291.


BlueprintEntity rail-signal & rail-chain-signal variants are missing a rail_layer property which should be string ? or some union with a "elevated" variant and potentially another variant but I'm ...

h.q.droid wrote: Tue Oct 14, 2025 11:04 am But the repo is quite old (2.0.46) and I'm not sure whether it reflects the current state.

The amount of modifications the lua VM internals get is quite low at this point, so the last commit for 2.0.46 should be the current state (at least as far as I know).

Just FYI Lua implementation that Factorio uses is publicly available on GitHub: https://github.com/Rseding91/Factorio-Lua

So if you want to search / test for vulnerabilities you can do so

I'm currently redoing my blueprint ser/de implementation since large parts of this are now properly documented in the lua docs and not only reverse engineered on the wiki.
While working on this I ran over the following issues so far (potentially more to come):

BlueprintEntity turret variants have ...

The important thing to note is that hex numbers must be in lowercase, so 0xff instead of 0xFF.

the headless linux build can be downloaded by anyone? its freely available.

https://factorio.com/get-download/stabl ... ss/linux64

It looks like the example entries are missing some spacing between them and overlap vertically a bit.

yeah I was referring to the single comma

Types/FluidFlowDirection has a description for the "output" variant that seems like its not expected to be there.

LoaderPrototype::adjustable_belt_stack_size mentions boolean as its type but it should be bool.

Hello there fellow strictly typed dump parser :D


Is there a reason why empty arrays are set as {} instead of []? This is kind of against the JSON standard . E.g. the ingredients for the recipe-unknown recipe on line 60888 . Use [] for empty arrays instead?


I ran into this some time ago (https ...

ConstantCombinatorPrototype::pulse_duration is specified to be a uint but the prototype docs do not contain such a type. Only the specific variants uint8, uint16, uint32, uint64. The runtime docs however do have a uint concept.

Types/EntityPrototypeFlags is missing the "building-direction-16-way" member (used by rail signals / chain signals).

CargoHatchDefinition::illumination_graphic_index is a uint32 but specifies a default value of -1.
So what is it? Is its default a uint32 underflow to 2^32 - 2? Or is it a signed int32?

HeatEnergySource::emissions_per_minute is overridden since heat energy sources don't support pollution. It mentions a default value of 0 but the type of emissions in 2.0 is dictionary[AirbornePollutantID -> double] and not just double anymore.

I think not specifying a default value and maybe ...

In 1.1 PipeConnection::type had a default of "input-output" and apparently the renamed field in 2.0 still does aswell but its not mentioned.
The new PipeConnection::connection_type property apparently also has a not mentioned default value of "normal".

UtilitySprites::platform_entity_build_animations is not marked as optional / DLC specific. But its not present in base 2.0 while it is in space-age.

I assume its related to the space_travel feature flag?

You could open a PR to add support for your target in the nixpkgs repo, the relevant files are here .

Tho I don't think its a good idea to use nix for game installs directly, rather have steam be installed through it instead. Especially with a lot of new releases that are expected to come the ...