Not a bug.

Simhelper is not compatible with 1.1.107 because debug.upvalueid was removed with other functions due to safety concerns. Space exploration mod and nixie tubes mod were updated to no longer require simhelper. Please update your mods.

Could it be that you were changing hidden settings and accidentaly enabled the "log-stack-trace-on-non-critical-exception" ? It is known to cause freezes since it loads symbols file to generate readable stack trace for the purpose of log file, but it is only supposed to be used when debugg...

Both of those are using the same internal function for revive purposes with the only difference being that silent_revive makes no sound and creates no smoke.

Thanks for the report. Issue is now fixed for 2.0. Root cause is that a/ writing to map_settings does not trigger cache resize, and b/ cache is resized on load. Desync would not happen if any of those 2 would not happen. Main fix for 2.0 is that writing to map_settings will immediately resize those ...

Thanks for the report. I am not considering this to be a bug. If they would be required to be equal then they would be all pointing at the same file.

gth wrote: ↑

Wed Apr 10, 2024 11:03 pm

Cue the disappointment. Can we either:
a) make replay work (almost) universally by making Factorio run "as" an older version, when necessary?
b) migrate replay/save files to the current version (maybe with an asterisk saying it may not be a perfect replica?)

a/ No.
b/ Absolutely No.

Please note this topic derailed from "multithreading by surface" to something about having partial game state on the clients which is not going to happen. Having full game state on the client is one of the fundamentals that allows us to have the game at all (with MP support) so any suggest...

I managed to reproduce this issue in 1.1.x on linux but when trying this in 2.0 on linux it loaded without any issues so it is fixed at least for 2.0. Since part of the fixes was to update minizip library i am not going to mess with 1.1.x anymore and i will say this is a duplicate of https://forums....

Given that programmable speakers were never designed with this use case in mind and since there is no sample queue and at the same time the update is not guaranteed to run at 60 updates per second in case of large maps or slow machines, i am going to call this is Not a bug.

Not a bug. Since diagonal rails have length of 1.41 per entity and they cost 1 rail while horizontal/vertical straight rails have lenght of 2 per entity and they cost 1 rail and since we have no fractional entity costs or fractional item counts in inventory, it is just not a bug. Going by the propos...

I tried to reproduce this issue however everything works fine for me when using 1.1.104 and 1.1.106 with 3 quick bars visible. Do you have any custom controls configured or using any overlays that could be interfering with middle clicks near the bottom of the screen?

Your error suggests that you included control.lua from data.lua. Data stage modding (that goes through data.lua) is supposed to create all the prototypes that will be available later, it runs way before save file is even loaded, even before main menu shows up. control.lua is from runtime stage which...

Not a bug. Electric mining drill has coal in the stuck buffer.

Do not ask me, that name was selected 29th august 2015 when this read was added to LuaItemPrototype in version 0.12.6. Back then there were only like 16 values that were possible to read from LuaItemPrototype.

Most of the stuff you mentioned makes a lot of sense, however i am not sure i am willing to change current behavior. Current behavior is kind of a mash-up of something that can be implemented explicitly using 2 combinators: first doing [each]>0, output [each] (input count), and second combinator con...

Already exists. https://lua-api.factorio.com/latest/cla ... le_effects

No. For a feature that base game would never use but would have to pay the performance cost i am not accepting that. For an item to have durability it would need to have a data attached to it. So far modules have data attached to them but i already made them work without any item data so i am even m...

Thanks for the report. Issue is now fixed for 1.1.107.

This is minor enough and possibly mod breaking enough that i decided to fix this for 2.0.

This is fixed for 2.0.