As for noise expression - I am not quite sure I understand the need for the "noise expression engine" altogether, the post is a bit hard to understand and it's not very clear what it can do that simply writing functions itself wouldn't. For example description of implementing things like ...

Thanks for the report. FluidStream does not support source_offset, so the fix won't be quick. I will try to implement it when I have some time.

While going through the code I noticed this was changed in 2.0. I hope it doesn't bother you too much in 1.1.

Duplicate of 103769

Duplicate of 103763

Hello, assuming the desync is related to x86 vs ARM consistency, 1.1.96 fixed two such issues - infinite resource richness and an overflow in random penalty noise expression seed. Could you try reproducing it in the latest experimental release?

As a programmer myself I'm curious what exactly you mean here. I understand the part that different platforms do floating point operations differently, and they might have different results. And because Factorio is deterministic it's very important that all calculations always result in exactly the...

Copied from https://crowdin.com/project/factorio/discussions/228 Hello! I am implementing plural localization support for decimal numbers. I want to add another option to `plural_for_parameter` - `decimal`. If specified, all plurals of decimal numbers would translate to `decimal`; otherwise, to `re...

Thanks for the report. This has been broken for a long time and is unlikely to get fixed in 1.1. For 2.0, I refactored the localization code and adding proper decimal numbers support is on my to-do list.

Thanks for the report. Based on Steam API documentation, this is not a bug. You may find the DRM-free binary useful for mod development; you can download it from our website.

Deadlock989 wrote: ↑

Fri Nov 03, 2023 5:38 pm

Mine was prettier.

Indeed. For 2.0 we added technology rich text tag for this purpose which would open the linked technology after being clicked. We just didn't want to backport it to 1.1 because it would take time and could introduce some bugs.

Actually, it was fixed for 2.0 a few months ago thanks to an external contributor, we just forgot to update the topic.

You can change preferred screen in graphics settings, it will be remembered.
Also, there is a handy windows shortcut to quickly move applications between screens: Win + Shift + left/right arrow key

Having a save file which reliably reproduces the desync would be very helpful. So far I was unsuccessful in my attempts. You could try enabling replay and attaching last autosave together with a desync report when it happens. Keep autosave interval to at most 5 minutes.

Related / possible duplicate: 106289

Thanks for the report, this is intentional. See 64233.

MEOWMI wrote: ↑

Mon May 22, 2023 6:23 pm

I'm guessing it just hides the marker, rather than changes functionality?

Yes, it only hides the markers without changing the behavior. Also, if you hover over an entity, the status will still report as being marked for deconstruction, which is intended.

It is for scenarios where you can choose difficulty, such as Tight spot.

Thanks for the report. It took a long time, but thanks to robot orders refactoring which happened a few versions ago, we can include this fix in 1.1.82.

Thanks, it's fixed for the next release. LocalisedString won't ignore 'correct' translation status of its parameters, so if one of them has unknown translation, the parent string will also be marked as not being correctly translated. This could be considered as a breaking change which is why I hesit...