Kaiserreich / Kaiserreich-4-Bug-Reports

Issue tracker for Kaiserreich for Hearts of Iron 4
110 stars 40 forks source link

CHI - AI giving all land to puppets in peace conferences #8415

Closed letheanlight closed 4 years ago

letheanlight commented 4 years ago

Quick questions OS: Windows 10 HOI4 version: 1.9.3 Kaiserreich version: 0.12.2 List any other mods used: Kaiserreich Music Were you using Steam?: Yes Were you in multiplayer?: No Which expansions do you NOT have?: I have all expansions.

Explanation of the issue:

CHI can puppet a number of tags through negotiation. If they wins a war while having a puppet, they will give all the land they conquered to their puppet instead of taking any for themselves.

This is a particular problem for the Second Northern Expedition, as it means the AI won't annex Beijing, and thus can't proclaim the Republic of China or proceed further down the focus tree until they eventually integrate their puppet.

Steps to reproduce:

  1. Ensure AI-controlled CHI has puppeted a friendly state, such as Yunnan.

  2. Ensure CHI wins a war while they still have that puppet.

Possible cause:

CHI does not receive claims on Chinese land at any point in the game, not even after becoming the National Revolutionary Government or the Republic of China. This may make it so the AI doesn't prioritize taking land for itself during peace conferences if their are alternatives.

Screenshots: AI CHI giving all of Qing to a puppet Yunnan: chi-1

AI CHI giving Mongolia, Ma Clique, and Tibet to a puppet Fengtian: image

Flamefang commented 4 years ago

Adding DSF because this is a CHI issue.

Rylock commented 4 years ago

@DSFDarker The problem is with the way the peace conference system works. If a country doesn't have a claim or core on a state, but an ally of theirs does, they will let them take it in the conference. I can add a rule for Chinese countries to ignore that, but then they would at least need ambitions on the territory - which I think many countries in China don't even have.

ghost commented 4 years ago

@letheanlight This issue is by accident already addressed in the overhaul of the LKMT in the works but, I will also add this into our internal build so it is fixed for the next update since it is pretty severe.

ghost commented 4 years ago

Fixed.