patch 2.08 is out

[velk]

Originally posted by Pillin:
The explanations offered by Pillin and Aikamun make sense to me. Because let's face it...thousands of folks in the province. Even if they run away in fear a few times, they can always come back the next day and help some more. After all, it is a whole month.

I think the crucial thing you have missed here is that the unit in question isn't going to be paraylzed for a month, they are going to recover a few minutes afterwards.

Unless, of course, you assume that any given province ( including defense 0, population 0 ones ) automatically contains a number of astral magic using farmers who will proceed to cast paralyze ( and never get resisted ) every 30 rounds for the rest of the month 8)

Anyway, it's veering off topic somewhat. Does anyone think that the following is unreasonable :
If both sides are fully routed AND both sides cannot move AND they are not immobile AND the turn limit expires they should both automatically rout rather than automatically die.

[Zapmeister]

I'm not sure what what is meant by:

If both sides are fully routed ... they should both automatically rout ...

In any event, considerations of "realism" (whatever that means in a fantasy game) take a back seat to more pragmatic concerns, like ensuring that the hosting terminates.

The auto-die code is in there to ensure that no combat can get "stuck" for reasons involving Paralyze or other reasons not foreseen, and I for one don't particularly care whether or not it can be rationalized in game terms.

Originally posted by Saber Cherry:
I'm surprised that nobody has a fix-mod for the Utgard theme yet. I have been kinda out of contact since I am currently on vacation, but I'll fixe the Seithkona and put it in the bugfix mod later today, and post to indicate when it is done.

-Cherry

You can't change the Utgard theme. You can fix the Seithkona, but you can't fix the fact that they have a smouldercone AFAIK since you are unable to modify a theme, only the base nation.

I have a mod with fixed Seithkona, but either I am to dense to figure it out, or it isn't possible to just modify the Utgard theme.

[Saber Cherry]

I see. I was going to fix Seithkona, but I guess the problems run deeper... I'll wait around a bit. Hard for me to access a computer anyway.

[Zurai]

Originally posted by Zapmeister:
The auto-die code is in there to ensure that no combat can get "stuck" for reasons involving Paralyze or other reasons not foreseen, and I for one don't particularly care whether or not it can be rationalized in game terms.

But why auto-die and not auto-rout? Why not just end the battle with both sides having "fled the field" so to speak? That's how every other TBS I can think of where this situation is possible handles it.

[PDF]

Originally posted by Zen:

quote:

---

Originally posted by Saber Cherry:
I'm surprised that nobody has a fix-mod for the Utgard theme yet. I have been kinda out of contact since I am currently on vacation, but I'll fixe the Seithkona and put it in the bugfix mod later today, and post to indicate when it is done.

-Cherry

You can't change the Utgard theme. You can fix the Seithkona, but you can't fix the fact that they have a smouldercone AFAIK since you are unable to modify a theme, only the base nation.

I have a mod with fixed Seithkona, but either I am to dense to figure it out, or it isn't possible to just modify the Utgard theme.

---

Are you sure ? I mean that the problem seems to lie with the Utgard Seithkona UNIT, that should have an ID and be moddable independently of whether it's used in a theme or not .
Or does the bug lies elsewhere - ie the unit is fine but stg screw it when it's used by Utgard Jotunheim ?

[Johan K]

Originally posted by josh_f:

I'm not sure I follow what your asking. I copied the files from the patch to the full dominions.app.

That sounds like the way to go. Could you do a
ls -l dominions2.app/Contents/Resources and a
ls -l dominions2.app/Contents/MacOS
and mail me the result to johan at illwinter.com.