You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is an example from chapter9_utils.cfg, INFERNO_LILITH_SIDE
recruit=Knight of Disaster,Knight of Disaster,Doom Knight,Knight of Pain,Knight of Disaster,Knight of Disaster,Doom Knight,Knight of Pain,Knight of Annihilation,Knight of Oblivion
I've seen this before and always assumed having "Knight of Disaster" in there four times was intended to make it that much more likely to be recruited, as if recruit worked like rand.
Based on some testing I did for something unrelated, and some reading on how the AI works, I don't think this is correct (anymore?). I do remember reading something about configuring the AI recruiting behaviour and a way to give preference to some units (though I know it also considers things like having a minimum of N scouts, etc).
Anyway, if this was done for the reason I think it was, there's probably a lot of review and reconfiguration necessary.
The text was updated successfully, but these errors were encountered:
This is an example from chapter9_utils.cfg, INFERNO_LILITH_SIDE
recruit=Knight of Disaster,Knight of Disaster,Doom Knight,Knight of Pain,Knight of Disaster,Knight of Disaster,Doom Knight,Knight of Pain,Knight of Annihilation,Knight of Oblivion
I've seen this before and always assumed having "Knight of Disaster" in there four times was intended to make it that much more likely to be recruited, as if recruit worked like rand.
Based on some testing I did for something unrelated, and some reading on how the AI works, I don't think this is correct (anymore?). I do remember reading something about configuring the AI recruiting behaviour and a way to give preference to some units (though I know it also considers things like having a minimum of N scouts, etc).
Anyway, if this was done for the reason I think it was, there's probably a lot of review and reconfiguration necessary.
The text was updated successfully, but these errors were encountered: