Vassal Bug? Land Area Calculation

[Backpack]

Last night, (playing v2.08 with Blake's improved DLL in custom Assets) - I got Egypt to capitulate AND give me a city in exchange for peace.

There is a bug in the vassal state land area calculations (I think, I could just be missing something)

The calculation occurred BEFORE I was awarded ownership of the city, even though it was a single transaction. This meant that Egypt was immediately down to 12% of original land area as of the capitulation, and in a few turns rejected vassal hood.

(The reason it dropped all the way to 12% was the capital was an island city with 3 or so squares of land, and the extorted city had a fair culture area around it).

Can anyone else confirm wacky math like this?
Can anyone think of another reason?
Can anyone confirm that this is intended behavior?

A related but unimportant to the discussion at hand question: Is the length of time from vassal release conditions being met until the vassal is released hard coded or based on some other factors?

Thanks

Kevin

[trev]

It is very rare to be given a city and capitulation, especially a city that affects the land area so much, but yes it does defeat the purpose of th vassalage for it to allow the quick cancelation of vassalage and I would call it a bug that should be fixed, even though your situation was a 1 in a million I think. The land calculation should be after the deal is finalised to avoid that situation.

[Diadem]

I thought vassalage was cancelled if your vassal grew too big? So this only extends the vassalage, doesn't it?

[Thedrin]

No, a vassal can back out of the agreement if their land area decreases to 50% of its size when the agreement was made - if you fail to protect them.