Considering the CoP expansion is arriving in a months time, I'd not use my time for this core-thing if I was developer and rather concentrate on getting this right for january...
I agree, but that's why I suggested they just revert the whole core expiry system back to the 1.2.2 branch.
I have no idea what their codebase looks like and it might be that they're not set up to be able to do that very easily. But from an outsiders perspective, it doesn't look too difficult.
1.3 contained only one core related change, at least one listed in changelog :
- Countries will no longer lose cores on non-culturegroup provinces when annexed
So reverting doesn't seem like it would require a significant amount of re-merging. Nor would it lose us much significant functionality. The net effect would definitely be better.
Anyway you're almost certainly right that nothing is going to happen. The time to do it was a week or more ago. It's probably now late enough that they'll want us to wait.
It is a shame though, this is a pretty significant issue that has dragged on for 5 weeks, and by time of 1.4 will have existed (in varying degrees of brokenness) for 10 weeks. That's quite a long time for an issue that is still spoiling some peoples' ironman games, and causing others not to play ironman at all at the moment.
There is a mod in the Steam workshop that disables disappearing cores...
Highly recommended it is too! Don't forget to rate and favourite it at Steam Workshop. The author's an arse, but the mod is great. As great as three lines of changed defines can be, anyway
Sadly, without mod support in Ironman, it cant help everyone.