Factorio Forums

I was working on updating my mod for 2.1 in the attachment and I do not know what is going on. I think it should work. Game state and API disagree on the LogisticFilter.request_from at an index, causing unpredictable emergent behavior of my mod. LogisticFilter.import_from works as expected. LogisticFilter.request_from does not. Even if I set request_from to "planet" as fallback. It is still broken. For example it can have a state that if you spam e to confirm it swaps between "any" and "planet" (the claimed default).

Can you please give an example of what's going wrong? Your description doesn't explain enough to point me at anything. A video would work best.

https://youtu.be/KKGGwmMn9U4 it seems to be something related to multiple filters being required to reproduce it. In the video I set 2 requests and then the second request to "all". my mod reorders them. but the second request is now "planet" again instead of "all".

I am not able to reproduce what's shown in your video. When I perform those steps the fish ends up the first row, and the rockets the 2nd row - and both have the correct import from shown. Do you have any other mods active?

no I tested it with minimal mods now and it is still exactly like in my video to me. so I guess my machine is the problem, if everything is fine on your machine. Like it really should not be hard to reproduce for you. the display GUI point seems to be wrong for me actually. odd. through swapping and printing slot 1 and 2 I can confirm the API being correct. So the yellow GUI button indicating which option (planet, platform or all) is active is lying to me. sorry that I did not consider that being the Bug here.

Are you playing single player or multiplayer? If multiplayer, are you the host or joining a game? Could you post your log file?

the single player debug world and here is the log.

I'm not sure what to do next with this. I can't reproduce any issues and looking at the code it doesn't give any hints about what might be going wrong.

I wasn't able to reproduce this exact issue but with someone else's help I was able to reproduce a different form of this and fixed that for the next release. You'll have to see if it also addresses the exact scenario you're seeing.