If your warchief or protector is getting spammed, it is because your totem delay ms is too low. The logic for dropping totems is:
Code:
if (skill.CanUse() && (mobsAroundTotem1 < 1 || mobsAroundTotem2 < 1 || mobsAroundTotem3 < 1 || !totem1CanSee || !totem2CanSee || !totem3CanSee)) // if any of the totems don't have a target near or they can't see it, recast
The key point in that, is that if
any of those conditions is true, it will recast. Warchief and protector have a delay for the dude to pop up, which as far as I can tell, means the totem is not targeting anything, thus "cannot see". So if your totem delay ms is such that
any apparition does not have time to appear and target before the totem delay ms is refreshed, the bot will continuously cast.
Not sure if marko001 has changed this in his update, haven't tried it yet.
Mine was spamming as well, I changed my placement ms to 1000, doesn't spam anymore (it is slow compared to a spell totem to get them all down initially, but it allows time for the guys to pop up so all my totems can "see" a target). Bear in mind, you'll need to adjust this based on your placement speed. Spend a bit of time to see how many ms you can shave off before it starts spamming again.
One way I can think of to "fix" this, is to introduce a secondary delay which triggers after max number of totems are reached, to allow time for the last totem to pop up before the totem ms delay refreshes.