Leader unit not obeying [avoid] tag

[quantumfleet]

So I've been building a scenario where, if the player makes it to an enemy leader's castle, he runs a short distance (past an easily-defended chokepoint), gets some reinforcements, and stays there for the rest of the scenario. The idea is that he stays behind the easily-defended chokepoint with his reinforcements while other events force the player to leave the area, allowing him to become a recurring villain. To keep his units behind the chokepoint, I've added an [avoid] area covering covering an area that would allow him to leave the area, and it works well. Not even a dark adept sitting in a shallow water hex can entice his units out.

The problem, however, is that the leader himself appears to be unaffected by the [avoid] tag, and instead makes a beeline for his castle keep, which is but a turn or two away. How can I fix this?

[beetlenaut]

[avoid]...A location for the AI to avoid moving to. The AI will never move a unit to this location except for trying to move its leader to a keep.

This sounds like a feature instead of a bug. You could use an event to remove all the leader's movement points each turn, or change the keep to a custom terrain that only looks like a keep, but doesn't work. I hope one of these solutions meets your needs because it's all I can think of.

Edit: You could also put in a feature request to add a key to [avoid] that allows you to override this behavior.

[Sapient]

What exactly is the desired behavior? Should the leader contribute to opportunistic attacks or just sit there passively?

Depending on the desired behavior, one easy idea that popped into my head was setting the can_recruit to "no".

[quantumfleet]

[avoid]...A location for the AI to avoid moving to. The AI will never move a unit to this location except for trying to move its leader to a keep.

How did I miss that????

What exactly is the desired behavior? Should the leader contribute to opportunistic attacks or just sit there passively?

Depending on the desired behavior, one easy idea that popped into my head was setting the can_recruit to "no".

I've thought about this for a while, and eventually settled on having him just sit there passively. Adding a "passive_leader=yes" worked like a charm.

Thanks for the responses.