Capitalism 2 and Capitalism Lab Forum

v6.5.14 （actually same bug occurred in almost all v6 versions）;
with all DLC and all are open;

When a private AI company A merger with another AI company B ( always be a listed company), if my firm or any one of my subsidiaries hold the shares of B, and then my firms become the shareholder of A after the merger deal.

But, even my firms are minorities, I still could find the Merger Button on A and can Merger A without any cost. And then the founder of A, will lose all his shares and get no money in his Wealth Panel.

We will investigate the problem.

I suppose that you meant using the "Merger" button on the Stock Market screen, right?

Please provide us with your save game file right after the first merger happened (as described below), so that we can test it using the "Merger" button on the Stock Market screen and try to track down the bug.

When a private AI company A merger with another AI company B ( always be a listed company), if my firm or any one of my subsidiaries hold the shares of B, and then my firms become the shareholder of A after the merger deal.

You can find save game files of Capitalism Lab from the C:\Users\<your user name>\Documents\My Games\Capitalism Lab\SAVE

You may provide us with your save game file by posting it here on the forum as a ZIP file attachment or emailing the save game file to us at info@enlight.com.

If your save game file is too large for attachment, you may check out this post about how to send us large files: https://www.enlight.com/forum/viewtopic.php?f=13&t=2473

this is the second time merger in my game. i will upload my save file.

The bug will be fixed in the next patch v6.5.15.

another bug:
when the share of a listed company is split down,10 shares become 1 share,
the shares holded by insurance capital will looks weird:the value and ratio are both too big.
when the insurance fund sell part of these shares, the total market value and ratio will change abnormally.

before: after: after selling: save file-before: save file-after:

This bug will be fixed in the next version 6.5.15.