[Bug][.85] AI Still webbing ranged units

'Nuff said.

18,965 views 9 replies
Reply #1 Top

I always wonder why the enemy widows will try to web one of my units immediately after the other one has succeeded in webbing it. Surely the big ol "+Webbed" floating above my dude's head would tip off the other spider that he should maybe switch focus to one of the other murderous hordes charging at him with axes raised.

I think part of the problem is that the AI doesn't properly re-evaluate their moves based on the outcome of other abilities and fights. It just kind of focuses one thing forever.

A similar issue is that any battle with enemy archer units feel like you have two parallel combats going on - one wherein your melee units are rushing their front lines, and another where you're desperately defending with that one unit the AI archers really hate for no particular reason.

Reply #2 Top

It's very strange, because this check very easy to implement. Same with casting spells on units with immunity, can't imagine why this still present in the game.

Reply #3 Top

Apparently it is not as easy as you think...

Quoting Frogboy, reply 5

I had that happen too. (webbed an archer).  There is literally hard code in there now to stop that and it still happened.  (pulling hair).
End of Frogboy's quote

Reply #4 Top

I've seen spiders choose not to web my archers in .85, but they still 'overkill' web/beguile on to a single unit, rather than spreading it out.

Reply #5 Top

Quoting SBFMadDjinn, reply 4

I've seen spiders choose not to web my archers in .85, but they still 'overkill' web/beguile on to a single unit, rather than spreading it out.
End of SBFMadDjinn's quote

Yes, I've seen that too.

Reply #6 Top

Webbing ranged creatures ain't always a bad thing, I do that when I want to make sure that my summon will hit the unit and beat it up to a pulp instead of chasing it around (which is easily prevented by AI sending a melee unit next to yours to limit movement while pulling his archer / caster away).

Regarding AI, I haven't noticed lately any double web or other effects of same class cast / used on same unit.

Reply #7 Top

Quoting Anelyn, reply 6
Webbing ranged creatures ain't always a bad thing, I do that when I want to make sure that my summon will hit the unit and beat it up to a pulp instead of chasing it around (which is easily prevented by AI sending a melee unit next to yours to limit movement while pulling his archer / caster away).
End of Anelyn's quote

Yes, to a human it makes tactical sense, but fairly little of what the AI does makes tactical sense.

Reply #8 Top

If beguile could stack and be for ranged and melee units that would be a workaround, I guess.  But I had a double beguile yesterday in 0.85.

With the brood archers now in the game, the spiders could do a web wall, protecting their ranged units for a few rounds with a sticky wall that lasts for 5 rounds, or you have to hit it with two melee units that are then stuck for two rounds to open it for other troops.  

It will only last 2 rounds if you set fire to it with a burning hands, fire staff, or burning axe.  That would be cool.

Reply #9 Top

I doubt anyone uses those spiders from mid game onward :)