[Strangepan] [2.0.42] Small Egg Rafts do not expand

[kuviman]

Since 2.0.27: Small egg rafts no longer absorb pollution because they will never produce stompers or strafers

If you hover the small egg raft though, it still says that its going to absorb pollution to spawn wrigglers

Also, they still try to expand - you can see good expansion candidate chunks around them, but they never spawn wrigglers that actually expand

This means its possible to kill all normal rafts but leave the small ones behind and enemies will stop expanding/attacking your base

[Nauviax]

Bumping this issue instead of creating a bug report; I'm like 99% sure that small rafts aren't even spawning wrigglers anymore, let alone sending expansion parties.

I think I preferred small rafts absorbing pollution and sending wriggler wave, but I see why the 2.0.27 changes were made. Though as-is, these small nests never seem to have ANYTHING guarding them, so the only enemies you need to kill for them are the ones that spawn when the raft dies. Surely this isn't intended and the small rafts should be spawning a few wrigglers to guard them?

Obviously less important once you clear them out and normal nests expand into the area, but makes getting your first few eggs very easy.

[Nauviax]

This is still an issue in [2.1.8]. Is this planned to be fixed or is it intended behavior? I haven't seen a small raft spawn anything for over a year now.

I noticed that the spawning cooldown is constantly resetting to ~180 ticks each time it hits 0 so it's trying to spawn *something*, but nothing ever spawns and no pollution is absorbed.

I've taken to leaving the small nests around as they seem to prevent expansion parties from creating working nests in the same area. I feel like if they aren't going to spawn any wrigglers to neither attack, defend or expand, then they should at least have their Factoriopedia entry updated to not list "Enemy spawn probability"? Though I'd much rather they start launching attacks and expansions again.

[Loewchen]

This is still an issue in [2.1.8]. Is this planned to be fixed or is it intended behavior?

It is Assigned, it will be worked on when there is time.

[Nauviax]

Apologies, I saw it was assigned but wasn't sure if these sorts of things get forgotten or removed if they are left inactive. I'll leave the devs to it.