Improved OmniCrusher unit AI

Bug #896045 reported by EVA-251
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Ares
Fix Released
Wishlist
AlexB

Bug Description

As it stands, OmniCrusher=yes invokes rather brain-dead AI on the units that use it. They constantly try to close the distance and crush enemy vehicles that attack them- which while useful for an open-top APC like the Battle Fortress, is not for say, a large battle tank or a super unit, where OmniCrushing would be a perk, not a core reason to buy it.

Or in other words, I suggest splitting this behavior off, via a tag, something like
OmniCrusher.AggressiveAI=yes/no ;do we want to be aggressive and try crushing things when given an attack order/get attacked by something?

Tags: attack battle try
Revision history for this message
WoRmINaToR (worminator) wrote :

I support this. It's a frustrating logic to deal with when you have massive epic units and you have to decide between the omni-crusher logic that you want on the unit but a braindead AI that comes with it, and no omni-crusher with the normal AI. It especially sucks in a mod like mine where I generally like to increase the general weapons range of most units, making a unit AI which is so hellbent on crushing even more useless and annoying.

Priority is another story but I'd definitely like to see this looked into someday.

Revision history for this message
AlexB (alexander-b) wrote :

See blueprint for a description of the feature.

Changed in ares:
assignee: nobody → AlexB (alexander-b)
status: New → Fix Committed
milestone: none → 0.a
AlexB (alexander-b)
Changed in ares:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Related blueprints

Remote bug watches

Bug watches keep track of this bug in other bug trackers.