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
Circuit needs some way of picking out priority targets and attacking them first. Priority targets could be defined in the config file.
Suggestions for the logic behind selecting a priority target. Perhaps when cycling through available targets. for each group, it could begin by checking the priority targets first always. The priority targets could be considered a configurable x% closer than they actually are for the purposes of target selection.
Example targets:
Commanders
Singularity
Moho Geothermal
Superweapons
Anti
Penetrator
Sniper
Catapult
Ultimatum
The text was updated successfully, but these errors were encountered:
I'd prefer to have "example targets" in "isBuilder, resource cost, threat and other descriptive params of a unit" terms.
It already attacks builders first, than enemies with highest threat weighted by distance to own base and by distance from attack group to enemy target, etc. So there's priority picking.
I'll consider configurable config lists, but i think those may simply make configs less readable.
Also use only ZK's Brutal configs for Circuit's performance testing, all other difficulties are handicapped.
It already attacks builders first, than enemies with highest threat weighted by distance to own base and by distance from attack group to enemy target, etc.
Unfortunately most of the targets I'd want to select for priority destruction are not necessarily those with the highest threat or cost on the field. I don't think the configs would be that much more difficult to read by having one more attribute, and its a fairly self explanatory tag. It could be a fixed flag, it doesn't need to a variable, although that would be useful.
eg. The priority targets could be considered a configurable x% closer than they actually are for the purposes of target selection, where x is high (4.0 or 5.0!) for a singularity, middling for a commander (1.25) and low for a target that is actually best avoided (0.1 for a solar). This would make groups willing to travel longer distances and still choose the Singu as the best target, and might make the group ignore a solar even if it is really close. Perfect!
Circuit needs some way of picking out priority targets and attacking them first. Priority targets could be defined in the config file.
Suggestions for the logic behind selecting a priority target. Perhaps when cycling through available targets. for each group, it could begin by checking the priority targets first always. The priority targets could be considered a configurable x% closer than they actually are for the purposes of target selection.
Example targets:
The text was updated successfully, but these errors were encountered: