Page 1 of 1

[Oxyd] [0.18.42] Biters stop attacking

Posted: Tue Aug 04, 2020 4:18 pm
by darklich14
Why do they stop attacking? Thousands of units pile together and every time they are aggravated, they just pile to bigger and bigger groups. They never attack only ever despawn after whatever the time window is. There are only a handful of unit groups and the pathfinder does not appear to be wildly overloaded. There is an obvious path to the source of the aggravation so what gives?
Screenshot from 2020-08-04 12-11-02.png
Screenshot from 2020-08-04 12-11-02.png (3.9 MiB) Viewed 2185 times

Here is a link to the save:
https://gofile.io/d/P58wuA

Re: [0.18.42] Biters stop attacking

Posted: Tue Aug 04, 2020 4:43 pm
by azesmbog
darklich14 wrote: Tue Aug 04, 2020 4:18 pm Why do they stop attacking?
This is a rhetorical question. They are pacifist biters. We sat down to smoke before a long journey. I have not asked this question for a long time, at least they did well that such groups disappear over time. Before, I had millions of them, stood and ate UPS.
This is by design :)

Re: [0.18.42] Biters stop attacking

Posted: Tue Aug 04, 2020 4:58 pm
by darklich14
azesmbog wrote: Tue Aug 04, 2020 4:43 pm
darklich14 wrote: Tue Aug 04, 2020 4:18 pm Why do they stop attacking?
This is a rhetorical question. They are pacifist biters. We sat down to smoke before a long journey. I have not asked this question for a long time, at least they did well that such groups disappear over time. Before, I had millions of them, stood and ate UPS.
This is by design :)
No biter should be left behind. They should all die by the burning liquid remnants of their ancestors.

Re: [0.18.42] Biters stop attacking

Posted: Tue Aug 04, 2020 5:09 pm
by azesmbog
Well, I don’t know, maybe you’ll be luckier and they will answer you. My inquiries on this matter were simply ignored. Therefore, I decided that this was intended by the developers.
Good luck!

Re: [Oxyd] [0.18.42] Biters stop attacking

Posted: Fri Oct 23, 2020 2:55 pm
by Oxyd
Thanks for the report, this turns out to be the same issues as this, which will be fixed for 1.1.0.