搜索结果: *

Yeah, thanks guys.
I think I'll manage with what I've got now. 

Actually, jacobhinds, the simple fact of starting a new game made the knight upgradable to the paladin in one ctrl+x.
So the STR and AGI values don't seem to matter at all.

@ Kelthin:
The thing is, adding a new troop is perfectly save-compatible. Putting in at any place is any troop tree is perfectly save-compatible as well.
You can also change a unit's level, and the game registers this change.

But it doesn't update the amount of experience needed to upgrade to the next unit in the corresponding tree.
That's in my experience the only thing that's not save-compatible.

So there's no way to make the game update that? 

To make further testing simpler, and so you people can help me better, I switched to Native.

So I created a test unit called "Swadian Paladin"; it is based of the swadian knight, but has higher stats, higher skills, and a level of 50.
I made it upgrade from the swadian knight.

I checked it in-game: I had to press ctrl+x 12 times (so it needed a bit less than 12000exp) to make it upgrade.

I closed the game.

I modified the default Swadian Knight so it now is level 5 (from default level 25)

I checked back in-game, and.... I still need to press ctrl+x exactly 12 times to get a Paladin.

What am I missing here? 


EDIT: Oh ****, I know. I need to start a new game. 
Ew. So most troop changes are save-compatible but not the experience-to-upgrade thingy? Damn.
Is there any way to make it so?

Alright, so after your reply, I ran a long series of tests.
And... What you said seems to be incorrect.

I have found that there is absolutely no correlation of any sort between the level of any units and the amount of experience needed for a unit to upgrade to the next "rank".

Now... you might have been talking about the "rank" of the unit, and not its level (aka RPG level I dunno, level 25 for a swadian knight? I don't remember). In which case it'd make more sense.