pogoman
commented
1 month ago The lines affecting the functionality you are describing are here and here; basically anyplace where i touch job expiryInterval.
The original value is: new IntRange(450, 550);
The result of these changes is that raider's check for enemies more frequently than in vanilla. In vanilla rimworld the raider receives a new job every 4.5 - 5.5s. When a job finishes/expires if there are no enemies within attack range, the raider continues on with whatever non-attack job they were assigned with (i.e. job starts again). If one of your pawns is nearby during this timer the raider will not react to the pawn until the 4-5s has expired. So in your vanilla test the raider makes it all the way to cover.
In my mod the value is much lower so the raider in your scenario stops halfway to cover and engages as the job timers are short and a colonist has come into combat range of the raider.
So my recommendation would be to restore those expiryIntervals to default, but be careful as i changed them specifically because of slow reaction times of raiders. I dont play rimworld much anymore but when i did i made the game as hard as i could, and slow reaction times from raiders meant you could easily cheese them by moving in and out of attack range with a faster colonist and abusing their job timers. An unfortunate side effect of knowing how the AI works i suppose.
EDIT: I should probably mention i used to play with combat extended where getting the first shot off was more important than getting into half cover. If you are playing without it then cover probably makes more sense as combat takes a lot longer, so as you say a raider firing in the middle of an open field is less valuable than it finishing the move job into cover
llunak
I play on extreme desert and there is something wrong with the mod when it comes to seeking cover. The problem is that raiders have a tendency to rush my colonists, even if they have guns and should rather seek cover. I don't remember the problem with 1.4 previously, but my previous playthrough wasn't in such open terrain.
As an example, load test2.rws.zip and let it run. There are 2 raiders, the lower one with a rifle does a good job of seeking cover. But the upper one with a pistol will simply run towards my colonists and cover on the opposite side of the same wall, which is dumb. If the mod is disabled, the raider will instead take cover behind the marble chunks above, which is a better decision.
(Also, the mod's About.xml lacks Harmony in the dependencies and the game disables the mod with rather cryptic errors if Harmony is not loaded because of this.)