Home Trending Latest threads New posts Developer diaries

1.08 Bug-Vassilzations, etc

Jump to latest Follow Reply
  • We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
Show only dev responses
Khephren

Khephren

Watery Tart
25 Badges
Mar 29, 2003
1.285
2
  • 500k Club
  • Hearts of Iron IV: No Step Back
  • Victoria 3 Sign Up
  • Battle for Bosporus
  • Hearts of Iron IV: La Resistance
  • Hearts of Iron IV: Expansion Pass
  • Hearts of Iron IV: Expansion Pass
  • Hearts of Iron IV: Death or Dishonor
  • Hearts of Iron IV: Field Marshal
  • Hearts of Iron IV: Colonel
  • Hearts of Iron IV: Cadet
  • Hearts of Iron IV Sign-up
  • Europa Universalis IV: Pre-order
  • Arsenal of Democracy
  • Victoria 2
  • Europa Universalis III Complete
  • March of the Eagles
  • Iron Cross
  • Europa Universalis III Complete
  • Hearts of Iron III Collection
  • Hearts of Iron III: Their Finest Hour
  • Europa Universalis IV: Call to arms event
  • Europa Universalis IV
  • Europa Universalis III Complete
  • Crusader Kings II
First noticed while playing AGCEEP, but upon trying the Vanilla GC same results. I like to country hop and I noticed on two seperate occasions, since 1.08 has been released, where I could not declare war against a certain country even though there was no reason for this to be so. Upon inspecting a save game today, I found the following:
Code: 
    alliance = { 
        id = { type = 4712 id = 179006 } 
        type = vassalization 
        startdate = { year = 1422 month = august day = 18 } 
        expirydate = { year = 1772 month = august day = 18 } 
        participant = { SCO } 
        } 
    alliance = { 
        id = { type = 4712 id = 227639 } 
        type = vassalization 
        startdate = { year = 1424 month = january day = 5 } 
        expirydate = { year = 1774 month = january day = 5 } 
        participant = { POM } 
        } 
    alliance = { 
        id = { type = 4712 id = 228946 } 
        type = vassalization 
        startdate = { year = 1424 month = january day = 23 } 
        expirydate = { year = 1774 month = january day = 23 } 
        participant = { BGL } 
        }

Multiple entries of this type. When a country cancels a vassalization, its tag is removed, but the pseudo-vassilization remains? I checked past version savegames (1.07,1.06) and this never occurred. This is a major bug as the country left in the vassilization is left diplomatically handicapped. ( A vassal with no master ). I have a Vanilla GC savegame but I believe this can be seen in any 1.08 savegame.

Example: Turkey vassalizes Byzantium. Byzantium breaks vassilization. Turkey cannot declare war on Byzantium. ( This is what happened to me )
 
Upvote 0
Khephren said:
First noticed while playing AGCEEP, but upon trying the Vanilla GC same results. I like to country hop and I noticed on two seperate occasions, since 1.08 has been released, where I could not declare war against a certain country even though there was no reason for this to be so. Upon inspecting a save game today, I found the following:
Code: 
    alliance = { 
        id = { type = 4712 id = 179006 } 
        type = vassalization 
        startdate = { year = 1422 month = august day = 18 } 
        expirydate = { year = 1772 month = august day = 18 } 
        participant = { SCO } 
        } 
    alliance = { 
        id = { type = 4712 id = 227639 } 
        type = vassalization 
        startdate = { year = 1424 month = january day = 5 } 
        expirydate = { year = 1774 month = january day = 5 } 
        participant = { POM } 
        } 
    alliance = { 
        id = { type = 4712 id = 228946 } 
        type = vassalization 
        startdate = { year = 1424 month = january day = 23 } 
        expirydate = { year = 1774 month = january day = 23 } 
        participant = { BGL } 
        }

Multiple entries of this type. When a country cancels a vassalization, its tag is removed, but the pseudo-vassilization remains? I checked past version savegames (1.07,1.06) and this never occurred. This is a major bug as the country left in the vassilization is left diplomatically handicapped. ( A vassal with no master ). I have a Vanilla GC savegame but I believe this can be seen in any 1.08 savegame.

Example: Turkey vassalizes Byzantium. Byzantium breaks vassilization. Turkey cannot declare war on Byzantium. ( This is what happened to me )
Click to expand...

so the "alliance" will be TUR only then? How then does the game know it is with BYZ? Or can't TUR attack anyone at all then?
 
I have no idea how it knows, but the option to attack Byzantium was greyed out until I deleted that line in the savegame :confused:
 
Khephren said:
I have no idea how it knows, but the option to attack Byzantium was greyed out until I deleted that line in the savegame :confused:
Click to expand...
but you *could* attack others? (I'm nothing like a computer wizard, though :) )
 
Can you dupe this on demand? IOW are you saying that every time the player (or the AI as well?) cancels a vassalisation this occurs?

Does it only occur after a "country hop"? If so, how are you doing this? You need to NOT load a save while within the game, but exit out to the main menu and load from there.
 
It seems to be after every vassilization is cancelled. If you play 100 years and then check a savegame, there will be literally dozens of these entries. You don't have to country hop, I just happened to notice it because I was country hopping. BTW, I checked back on all my past savegames and this bug was introduced in that patch that added all the new tags. Before that it never appeared. Like I said, I could send you a savegame, but if you check one of your own, it will be there. ( Just need to give the game about a 50 year run, long enough to make and cancel a few vassilizations )
 
OK, I'll report it, thanks.
 
Second that.
 
Sorry, I've had no response from Paradox to the report. I can only guess Johan is busy on something else right now. I'll *bump* the report.
 
One thought while we're waiting; it would seem fairly trivial to write a utility, or even something like a Word macro, to process a save game file automatically. Anyone up for that?
 
Guess not, huh.
 
Khephren said:
It seems to be after every vassilization is cancelled. If you play 100 years and then check a savegame, there will be literally dozens of these entries. You don't have to country hop, I just happened to notice it because I was country hopping. BTW, I checked back on all my past savegames and this bug was introduced in that patch that added all the new tags. Before that it never appeared. Like I said, I could send you a savegame, but if you check one of your own, it will be there. ( Just need to give the game about a 50 year run, long enough to make and cancel a few vassilizations )
Click to expand...
It doesn't seem to happen for vassalizations that are broken by the player (either as the vassalizer or the vassalizee). Do you remember if it only happens when the AI vassalizee breaks the alliance? (this is the only example given, BYZ/TUR, BYZ breaking)
 
After having a little more time to look at it, I realize there is quite a bit more randomness to it. The only thing I can say for sure is that it will always happen when a vassilization is broken by event. ( Happens lots in AGCEEP ) It happens with other vassilizations and I'ver even noticed RM's with the same problem, but there doesn't seem to be a pattern.
 
Is this still happening? I just went through my latest save game file and there's not a single instance of this.
 
I don't have it also, although dozens of vassalization cancells occured in the game. None of these by player, however.
 
You must log in or register to reply here.
Top Bottom
Back