Dissapointed

[Arralen]

1) There's already patch 2.06, and 2.07 is in the works, as one could have guessed from johans article.

2) johan is on the design team

3) I've never seen the AI cast the same, unstackable spells with target "caster" more than once. Unless the commanders are scripted to do this. Keep in mind, though, that some spells do stack with themselves or each other.

4) ".. in the 2.07 patch the spell AI will drop the estimated worth of some protective enchanments. As it stands it will also value protective enchanments less and less as turns go by. .. think this will take care of most problems. Even if for some reason the AI doesn't recognize an enchantment already done, it wouldn't cast the spell again after some (5 ) combat rounds.

[Arryn]

Originally posted by Arralen:
3) I've never seen the AI cast the same, unstackable spells with target "caster" more than once. Unless the commanders are scripted to do this. Keep in mind, though, that some spells do stack with themselves or each other.

I have had the AI cast Body Ethereal on my (quickened) pretender six consecutive times in the same battle. That's all my pretender cast for 3 complete combat rounds. Body Ethereal does not stack, nor did I script it.

[Kristoffer O]

Originally posted by Arryn:

quote:

---

Originally posted by Arralen:
3) I've never seen the AI cast the same, unstackable spells with target "caster" more than once. Unless the commanders are scripted to do this. Keep in mind, though, that some spells do stack with themselves or each other.

I have had the AI cast Body Ethereal on my (quickened) pretender six consecutive times in the same battle. That's all my pretender cast for 3 complete combat rounds. Body Ethereal does not stack, nor did I script it.

---

Send the trn file to support@illwinter.com so we can take a look at it. Explain what is wrong so we have clue what to look for.

I have never seen anything like it, but there are some reports here that it has happened. No one has sent us any bugged files though, so it is hard to do anything about it.

[Lord_Devi]

I agree completely with the magic system actually. It's the ONLY thing in the game that actually angers me a bit. I've had that exact same problem. "Fire Shield, Fire Shield, Fire Shield, Fire Shield" I mean he only needs one ;P

I think this game only really needs two things to make it as eternal as the other classics (i.e. SEIV), and that's increased modability(but this is already in the works =), and an improved magic combat sytsem.

I'm afraid the excuse of "it's only a suggestion" or, "it's a chaotic battle, he'll do what he thinks is best" just don't cut it. It is NOT a suggestion when I tell my caster to not kill my own men. I should definatly be able to take more control over them - the AI just isn't capable of using it's magic to it's full potential. The old problem of the caster casting summoning spells when it already has a HUGE army comes to mind...

Plus, equally important - or even more so really, is that it makes it funner! =) I mean, giving the players more opportunities to play with the massive amounts of spells just increases gameplay 10 fold I think. Spells are fun, it could be really entertaining trying to find secret combinations of spells etc.

That list of 5 spells just doesn't cut it IMO. Esp how he doesn't even listen to you

[Arryn]

Originally posted by johan osterman:
I am a little sceptical to claims that the AI has cast nonstackable spells that only targets the caster and has no fail chance repeatedly on itself. I attribute the cases reported to having troops nearby that can be affected by spells, so for example body ethreal has an area of 1 and so can be cast on nearby bodyguards, so that reported incident is most likely not a case of casting a nonstackable spell repeatedly on itself.

Johan, you really shouldn't so readily dismiss reports by players of odd AI behavior. My pretender was alone, no bodyguards or other casters within range 5. And the AI DID cast a caster-only spell repeatedly (Body Ethereal), to the tune of six times. The only reason it stopped at six was the battle ended. I wouldn't remember the event so well if it hadn't been such outrageous behavior on the AI's part.

I really resent the attitude that because you don't understand why the AI did something stupid, that we who are doing the reporting must be wrong somehow. Enough people have been reporting this type of problem that I would expect you to sit up and pay attention. Not make excuses and cavalierly dismiss our reports. It's beneath you.

Sincerely and respectfully yours,

[Strages Sanctus]

MY biggest issue really is that the ai will cast offensive spells that damage the caster, even when other options are available that would not harm the caster, and have a better damge/area/fatigue ratio...


This really only becomes an issue if you have a rainbow mage with lots of options available and deep evocation research...

Magma eruption was definitely the worst choice for the Ai to cast... the troops being targetted were militia so not heavily armored.

IMHO the routine should consider:
Note this is only for a caster that has meleers attacking them.

--Number of targets hurting me
--Are the troops I am about to target immune to this type of spell damage?
--How many of the attacking enemey troops will I hit with this spell.
--Will it hurt me if I am in the AOE of the spell?
--How many friendlies will be hurt by this spell?
--Armor of troops attacking me
--Is the spell I am about to use more efficient at damaging or penetrating armor.
-- how much will thi spell fatigue me? will I go unconcious if I cast this spell.

Of course the overall system is obviously very complex indeed and any kind of AI programming is a herculean task by any means. By tackling the at least the issue of offensive spell choices could be made more efficient.

[Arryn]

Originally posted by Kristoffer O:
Send the trn file to support@illwinter.com so we can take a look at it. Explain what is wrong so we have clue what to look for.

I have never seen anything like it, but there are some reports here that it has happened. No one has sent us any bugged files though, so it is hard to do anything about it.

Thanks for listening. Alas, however much I'd love to do so, so that this bug can be squashed, I don't have a trn file from that game. It happened over a week ago, and I wasn't keeping turn-by-turn saves. Hopefully someone else will have kept their file(s) and can show you similar behavior.

I do understand that you cannot fix what you cannot replicate. I've been a programmer for almost 30 years and I can sympathize.