i've submitted a couple patches to help investigate this in more detail (or if we're lucky, maybe just fix it)

mods, if we could adjust the title to "Crash with LuaDebugAdapter when updating breakpoints"

Very strange. It looks like you caused a SetBreakpoints request, which then failed at a completely nonsensical spot as it was looking for the corresponding known source file to (re)validate those breakpoints. Can you tell me more about what you were doing before this happened?

i said this on discord yesterday, but just to have it on the record here in the thread: my conclusion is that require is working as intended and that this was a bug in the mod lua that had merely been hidden by previous quirks of loading that no longer apply, and that the fix is for the mod lua to ...

in 2.0 the package.loaded cache got reset to an earlier state between each top level data stage file, it appears this is no longer the case and it is now more like normal require caching behavior (the main deviation from upstream behavior now is the use of resolved name rather than requested name ...

in inventory sensor data-updates, you do:

require('lib.init')
Framework.post_data_updates_stage()


`lib.init` resolves correctly but is already cached from your earlier call in data, so it does nothing, and you discard the returned reference. You then call into the global var Framework, which ...

yeah i was waiting for it to be merged (which it now has been) to confirm that it's fixed for next release

the dict type option for LuaEntity::neighbours is listed as dictionary[string → array[LuaEntity]], but it appears all the dict-shaped results are actually dictionary[string → LuaEntity]

get_max_inventory_index() on a rocket silo returns 12, but get_inventory(12) seems to always be nil, and the largest defined index is 11:

fuel=1
rocket_silo_input=crafter_input=2
rocket_silo_output=crafter_output=3
rocket_silo_modules=crafter_modules=4
unnamed =5
burnt_result=6
crafter_trash=8 ...

get_inventory(5) on a rocket silo returns an inventory, but that inventory has an empty `name`, and there is no corresponding defines.inventory value. From discussion with Bilka, this seems to be `rocketInventoryIndex`, the inventory of the attached cargo pod.

Just to confirm, the other pr (#7998 re: LuaPlayer.blueprints) does not in fact fix this - but i don't understand this one enough to do anything more helpful

https://lua-api.factorio.com/latest/aux ... cture.html

would be nice to specify the preference when multiple packages of the same mod exist (zipped/unzipped) which one will be loaded

It is now. thank you. also it seems that i cant compile it? it says that trio.h is not found? is there a dependency im missing or something?


we use https://daniel.haxx.se/projects/trio/ for a printf that actually works correctly on every platform (which, amazingly, is not something you can ...

for example, https://lua-api.factorio.com/latest/classes/LuaEntity.html#get_logistic_point could trivially be a function with two overloads: fun():LuaLogisticPoint, fun(index):dictionary, and we could in turn generate overload tags for LuaLS to correctly determine which return it got from a given ...

in the mean time, SignalFilter is probably the type you're actually looking for!

If anyone has any suggestions for how I can detect, from the debugger (in TS), that this has occurred (or is likely to occur in a given environment), i can also offer to set the setting for the future.

The runtime classes with index[] operators currently only specify the values returned by that operator, not the key types to use with it. LuaLS tags require a key type for these as well, which i'm currently filling in with special cases.

https://lua-api.factorio.com/latest/types/FileName.html has `base` in bold, instead of in code tags with underscores

FMTK provides a growing collection of tools for VSCode and other editors. It is available as a VSCode Extension , and a standalone npm cli tool

Tools include:

Debugging, with breakpoints, stepping, variable inspection etc (for any DAP-compatible editor)
JSON Validation of various files ...

https://github.com/justarandomgeek/vsco ... rkspace.md

What's the lifetime of an image that is uploaded and then un-referenced?

Could we have a flag for "hidden"/unlisted images in the gallery to not be shown in the image-strip on the mod page, for use in the markdown description/faq pages?