Yes, for now. We considered addressing it in the short-term by changing the way some decentralized nations were laid out at the start of the game, but it would be ahistorical and not a sustainable / generic solution. Instead we have been working on an improved colonization mechanic that takes Claims into account to address this, which will be coming in a later patch.
There are some changes that improve the AI in this area:
and some other bugfixes and tweaks that, taken together, will improve it further.
Addressing the issue with the pricing algorithm traders use to determine traded volume is a major change that will require substantial testing and experimentation, so we were unable to address this for 1.1.
Too much radicalization also disrupts the industries, and note that they will only do this if they are quite profitable. Using only minimum wages for this would mean that wages would not rise at all as the economy grows, which would be neither a desirable nor particularly realistic outcome.
Performance work is ongoing and I know some improvements have been made for 1.1 in this area, even though they haven't made it into the changelog (since they're entirely under-the-hood).
I did some digging and I think we just missed this in the patch notes
Circular trading was caused by one of the computations not taking the post-trade price of the goods into account, thinking it would always be possible to trade even though they were also being traded with. So it was a bugfix, not a design change.
They were removed if they were not referenced anywhere in code or script. No functionality was removed, only misleading entries in the defines file that suggested something worked a certain way when it didn't.
It's on the list. Our design team can only make and get changes vetted so fast. I couldn't squeeze tech changes in for 1.1 soon enough.
You mistake my respectfully disagree, its with your tone. Bold screaming of an actual fix, without giving any context of what you mean by that is a wonderful way to convince others of your argument. In my personal opinion this fix is good enough for now and I don't think the split state solution that is being proposed (or I have to assume here because you've not actually proposed something, just really screamed "is that it?") here is of any actual value in relation to the other issues that need tackling.Can we expect an actual fix to this problem, so Gibraltar and Pondicherry wouldn't count as treaty ports in any circumstances (like rank change), or this is how it will be working forever?
Uhm, I guess this means it IS intended and Gibraltar intended to be a treaty port forever?
France is still powering ahead a bit, but no longer able to access the British Market and fuel it as crazily as it did before.
Good question! We always need to time releases carefully to make sure staff are on hand if something unforeseen happens. Even patch release dates are usually set several weeks in advance and rarely moved.
I feel you, and I'm sorry! It turns out, after repeated playtesting, that running the tutorial as a subject in the British market really messes up the pacing and can introduce a number of bugs in the flow. Several parts of the early tutorial is centered around making noticeable changes to the profitability of buildings or the prices of goods, and it turns out this is much harder to do as a small nation in a giant market than what's suitable for a tutorial. We'll try to make it up to South Africa in the future!
Sadly no. This has to do with how we separate presentation layer and logic layer in V3, which lets us do some cool things to enhance performance and responsivity but disconnects the game logic scripting facilities from the GUI scripting. We're going to take a shot at it for future patches though, since it's highly requested modder functionality. Stay tuned!
We've got a solution that will potentially work for 1.2 - it needs vetting.
Reported overflows get the highest priority (after hard crashes), but they can also sometimes be tricky to solve technically, since numbers can get really big in V3. It is possible that some root issues have been fixed in these patches that cause the other overflows to no longer happen either, but if you do encounter any other overflow errors in 1.1 once it drops, please do file bug reports.
