Confirmed Victoria III - Bankroll fail but still takes the money and hard to stop it.

  • 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.

MrBumbles

Recruit
18 Badges
Jan 24, 2013
2
0
  • Hearts of Iron IV: Cadet
  • Crusader Kings III
  • Age of Wonders: Planetfall Deluxe edition
  • Age of Wonders: Planetfall
  • Prison Architect
  • Shadowrun Returns
  • Age of Wonders III
  • Surviving Mars
  • BATTLETECH
  • Cities in Motion 2
  • Cities: Skylines - After Dark
  • Pillars of Eternity
  • Cities: Skylines Deluxe Edition
  • Cities: Skylines
  • Magicka
  • Lead and Gold
  • Dungeonland
  • Crusader Kings II
Short summary of your issue
Bankroll fail but still takes the money and hard to stop it.

Game Version
1.0.5

What OS are you playing on?
Windows

Do you have mods enabled?
No

Have you tried verifying your game files?
No

How much "pain" is this causing you?
2

Please explain the issue you experienced in the most condensed way possible
I bankrolled Great Britain as Tasmania (owned all of Australia and North Island) after the "Australian Federation" event. The bankroll failed as relations were below poor (they wasn't we had good relationship) 1 day after enacting it, the influence returned to me however the -151K it was going to cost me did not and I kept losing the money but the game thought I wasn't bankrolling and it wasn't 'properly' showing up in expenses. I fixed it by bankrolling a MUCH lower nation, which succeeded, then cancelled it and back to +27.2k.

Please explain how to reproduce the issue
Bankroll a larger power, maybe the have to be your overlord? not sure on that one

Is there anything else you think could help us identify/replicate the issue?


I have attached a save game
Yes

Upload Attachment
File(s) attached
 

Attachments

  • tazmania.v3
    20,8 MB · Views: 0
Upvote 0

Duke Corvus

Lt. General
External QA
Feb 26, 2021
1.493
553
Hi, MrBumbles,

Thanks for the report! Glad you were able to find a workaround until the issue gets fixed. We've added it to our database, so you can be sure the dev team will look into it.

Cheers!