You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The Zhongming/Gongbo army tree purges Nosaka Sanzō, but if you release Japan he's still the leader.
Steps to reproduce
As CHI, accept Nosaka Sanzō.
Defeat Japan with Falling Sun white peace.
Go the Zhongming/Gongbo path.
Complete the army purge foci (the first one, I believe).
Invade and release Japan.
Possible Cause
Sanzō has a trait that gets him purged; devs coded the purge event without thinking that Sanzō would still be there and not already Japan leader (?). Easy fix would be removing him from the purge event.
Screenshots
(Sorry that I didn't grab a screenshot of the event. I tried but it was too late. I'm on an airplane rn.)
Save File
Not possible
Log Files
Not possible
Important Files Attached
I have attached the game/error logs and a save to go with this report. I understand that failure to do so will likely result in automatic closure of this issue if not enough information is included to determine the cause of this issue.
The text was updated successfully, but these errors were encountered:
OS
Windows 10
HOI4 Version
1.14.7
Kaiserreich Version
1.1.3
List any other mods used
KR Music, KR Models
Were you using Steam?
Yes
Were you in multiplayer?
No
Which expansions do you NOT have?
NSB, AAT, BBA, Content and Aesthetic DLCs
Explanation of the Issue
The Zhongming/Gongbo army tree purges Nosaka Sanzō, but if you release Japan he's still the leader.
Steps to reproduce
Possible Cause
Sanzō has a trait that gets him purged; devs coded the purge event without thinking that Sanzō would still be there and not already Japan leader (?). Easy fix would be removing him from the purge event.
Screenshots
(Sorry that I didn't grab a screenshot of the event. I tried but it was too late. I'm on an airplane rn.)
Save File
Not possible
Log Files
Not possible
Important Files Attached
The text was updated successfully, but these errors were encountered: