I have a Savegame with a bunch of mods; including Flare Stack and Ammo Loader+.

Everything was working just splendidly. At some point in my playthrough I wanted to change a Flare Stack startup setting (changing the ‘fluid burn rate’ from 10 to 100). When I did the change, restarted Factorio and loaded up the save again, I noticed that Ammo Loader+ was using insane resources when mouse-over’ing a turret. I pressed F5 to see the resource load of the game, and Ammo Loader+ was sitting at 0.82. But when I mouseover a turret, the game freezes for a second and the resource usage jumps to 200+, making the game completly unplayable for 2 seconds, and then it runs normal again; until I mouseover a (different) turret again.

Turning the mod off via the settings whilst the game is running (Escape > Settings > Mod settings > Ammo Loader + > Enable = FALSE) ‘fixes’ the issue.

I really don’t see how these two mods interact in this strange way. If it’s any good I can provide my save games (one where the Flare Stack setting was still 10 and everything was working fine, and one after I changed it to 100) for reproduction.

Hm thanks for bringing this to my attention liquid. I think this is more likely an issue I caused with one of the updates last night, and the flare stack setting change is just coincidental.

I would still like a link to your savegame if it's not too much trouble, so I can debug the issue firsthand. I think, though, that I already know where I can start looking to see what may have gone wrong.

In the meantime, I'll let you know directly if I find a solution and upload a fix.

Hi silentcrim,

I think the issue was with a different mod completely. I did some things right after the other so I'm not sure what fixed it, but I:
- Placed more Ammo Loader+ Worker chests, so that turrets get filled by chests that are much closer by, plus I don't have 2000+ turrets all tied to 1 worker chest anymore;
- Removed some other mods that can increase/decrease gamespeed

I think the combination led to the fix

It's good to hear that the problem was fixed! I was having trouble reproducing this in my debugging setup. Still, I'll keep an eye out for a bug like this, as it is something my mod could possibly cause.

Don't hesitate to let me know if you have any more issues!