My hope is that by then they'll release EU4 2.0 along with Despacito 2 so the bug list might be trimmed down a bit.
Just a bit.
16 bugs/design inconsistencies that have existed for multiple patch cycles
- Thread starter bbqftw
- Start date
-
We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
My hope is that by then they'll release EU4 2.0 along with Despacito 2 so the bug list might be trimmed down a bit.
Just a bit.
So why not make a post with links to the respective bug reports? Makes it easier for Paradox to follow up.
Why would anyone think making 2 threat about the same topic is a good idea?
It's hard to find motivation to do this kind of work when bug reports are flat out ignored.
For example issue #3 has been reported at least 5 times, most by me but another poster submitted one also. Years later, it's still there:
At some point it gets tiresome. Why don't we just bug report it? Actually there's a pretty good reason these kinds of discussion threads appear rather than a simple bug report. The purpose of this thread is to point out bug reports that have been flat out ignored for years (obnoxious, long-standing bugs) despite their adverse impact on the game and deprioritization compared to esoteric exploits and things that don't cause the game to literally lie to newbies and veterans alike.
Also, trade league members don't get called in by CoBs when the tooltip says otherwise. In general it's impossible to tell which allies/guarantors will defend CoBs. I feel like this is rather important information for the player to have. One might even say it's more important than nerfing one faiths and one cultures.
There currently exists an ironman exploit that allows nation switching "/tag" console style. There's also an exploit that allows any selectable country to start with custom nation ideas in ironman. The tag switching exploit was previously fixed before returning in a recent patch along with a host of other bugs. It would be a bit ironic and not the least surprising if tag switching legitimately for better ideas gets nerfed while starting the game with 33% admin efficiency is still possible. Gotta nerf the real exploits like Otto -> Byzantium because forumers who can't Mare Nostrum say it's broken.
There currently exists an ironman exploit that allows nation switching "/tag" console style. There's also an exploit that allows any selectable country to start with custom nation ideas in ironman. The tag switching exploit was previously fixed before returning in a recent patch along with a host of other bugs. It would be a bit ironic and not the least surprising if tag switching legitimately for better ideas gets nerfed while starting the game with 33% admin efficiency is still possible. Gotta nerf the real exploits like Otto -> Byzantium because forumers who can't Mare Nostrum say it's broken.
Last edited:
Just Swedish laziness. Clear as water
Not really though. Some of these are ~ text edit tier of difficulty to fix. They've done a lot more to benefit and break the game than that.
Since bad will is unlikely as an explanation the most plausible conclusion is some kind of egregious process flaw. The pattern of what gets patched vs not just doesn't make sense regardless of what motive one guesses...regardless of whether you assume cut-throat $$$ incentive, making the game better, making it more accessible to beginners, making it more balanced or whatever else leaving lying UI in while patching some of the stuff that actually got attention doesn't make sense.
I'm guessing it's a combination of QA being severely understaffed compared to what they have to deal with, and that some bugs just take too much effort to fix compared to their impact. The text editor ones are probably buried so deep that they'll never get fixed for as long as DLCs keep introducing new bugs.
But then again it is curious how quickly the Kyoto engine and England double IA/tag shift exploits were fixed.
But then again it is curious how quickly the Kyoto engine and England double IA/tag shift exploits were fixed.
Good development organizes some prioritization of bug-fix requirements and actually schedule them for patches. My experience (30+ years) is that most companies don't do that but just pick up the most talked about issues. It's called reaction to, not pro-active. I have had multiple occasions where the CEO came down to the IT department to argue some changes. That's the worst case of "reaction to" development but far too common. PDX seems to be the same
Can you link me to one such report? A search for "belligerent" posted by you but didn't find a report showing that issue, possibly due to the forum search issue.
Unfortunately I can't. That stuff was lost along with the entirety of just about everything ever with that search bug. I haven't bothered with new reports after the 5th time or so, but reported as early as 2015 for sure.
2015 was also the start of the "can't take this province you could core instantly because we'll pretend you can't core it". I reported that during the open beta during the "common sense" DLC timeframe. It got ignored, implemented into the game, and still exists to this day.
Fort bugs, of which there are at least several objective ones, date back that far also. My personal favorite is how the game equates movement lock to "hostile zone of control" (I have a Ceylon picture of it that's 3 years old). This isn't just a tooltip error - if you get units caught and shattered it's possible to get same-province wiped across two battles despite that there are no forts in a 10 province radius. Also ignored.
Imgur dates this as at least 2 years old for example. "You can't return to the province you're in now because it's blocked by a hostile fort".
Do you consider couple of years it took them to fix England IA/tag shift exploit quick?
IIRC it was possible to do with France and England, someone did it with both and they only fixed the France decision, then after I did it with England it got fixed the next week. I'm sure if someone used the custom nation exploit to WC in 50 years on 1.26 then it would get fixed pretty quickly, just like how tag switching was never a problem until the dev clash.
The overall bug fixing priority is something like :
Bugs from new patch (just the ones found in the first month) > exploits used by Florryworry > exploits posted on reddit >>>>>>>>>>>>>>> everything else. Some of the exploits aren't bugs per se but loopholes from careless coding. I would imagine the actual priority should be something like
UI/game mechanic bugs that get reported the most often > bugs that get reported the least often.
I doubt the experience of the average EU4 player would be affected by doubled peace getting fixed compared to having the coalition tooltip updated.
The overall bug fixing priority is something like :
Bugs from new patch (just the ones found in the first month) > exploits used by Florryworry > exploits posted on reddit >>>>>>>>>>>>>>> everything else. Some of the exploits aren't bugs per se but loopholes from careless coding. I would imagine the actual priority should be something like
UI/game mechanic bugs that get reported the most often > bugs that get reported the least often.
I doubt the experience of the average EU4 player would be affected by doubled peace getting fixed compared to having the coalition tooltip updated.
Last edited:
Yeah, I guess the double CTA bug would be fixed already because Florry, hadn't the Dharma be so close.. Meanwhile, declaring on a tributary.. Who's gonna join? Let's make a backup and see..
It existed at least since 1.14, likely even earlier than that. I think they've patched some particular cases in some patches, but it was always usable until they've introduced 'remove_non_electors_emperors_from_empire_effect'.
Surely you mean if someone used the custom nation exploit and posted about it?
Yeah, it looks that way. But they have fixed bugs I've reported outside of this pattern (perhaps because they were crashing the application). So they don't entirely ignore other issues. I don't really understand why they are fixing some exploits. So someone found a way to play with "unlimited points" custom nation - it has no effect on anyone who don't intentionally go through the trouble of exploiting that. And if someone does it, how does it hurt PDS if people play their game the way they want?
As much as I hate saying this where is the dev commenting on this thread? ANYTHING would be nice.
"You guys are right these are issues that we've let go and we're gonna do something about it"
or
"No"
Either response would be at the very least something, as opposed to the complete and utter deafening silence we've had on these ACTUAL ISSUES with the game that have existed for years.
"You guys are right these are issues that we've let go and we're gonna do something about it"
or
"No"
Either response would be at the very least something, as opposed to the complete and utter deafening silence we've had on these ACTUAL ISSUES with the game that have existed for years.
Yeah, I guess the double CTA bug would be fixed already because Florry, hadn't the Dharma be so close.. Meanwhile, declaring on a tributary.. Who's gonna join? Let's make a backup and see..
I told DDRJake about double CtA several months ago as a show of good faith. I asked Florry not to use it until 1.25 under the impression that anything shown on stream would have a higher chance of getting fixed. But what happened is the other exploit I mentioned but the devs already knew about and Florry has used already did get fixed, which was double peace, while double CtA still works. I would prefer that it remains unfixed for the time being since it's a fun exploit that allows for some crazy scenarios such as an HRE vs. Ottomans vs. Ming world war pre 1500, or perhaps a sub 1600 Mare Nostrum. And of course because there are much more important problems to address than niche exploits.
Double peace was also stealth fixed, the change wasn't in the patch notes. It was pretty much only useful for cutting down big blobs during WCs, and only had a dramatic impact on perhaps speed WCs. But then Marco improved on the previous fastest WC time by more than 10 years without double peace so it turned out to be not that important after all.
As for to CoB vs. not to CoB, backups are the only way since the default backup syncs up with the main save file after 1.23 because reasons.
I don't know if they are understaffed but I find really weird to only acknowledge last week a well known bug from Rules Britannia's D1 by all the community : https://forum.paradoxplaza.com/foru...-ai-vassal-with-unsustainable-fleets.1106873/
Sometimes, I really wonder if they are playing there own game....
Last edited:
It existed at least since 1.14, likely even earlier than that. I think they've patched some particular cases in some patches, but it was always usable until they've introduced 'remove_non_electors_emperors_from_empire_effect'.
Surely you mean if someone used the custom nation exploit and posted about it?
Yeah, it looks that way. But they have fixed bugs I've reported outside of this pattern (perhaps because they were crashing the application). So they don't entirely ignore other issues. I don't really understand why they are fixing some exploits. So someone found a way to play with "unlimited points" custom nation - it has no effect on anyone who don't intentionally go through the trouble of exploiting that. And if someone does it, how does it hurt PDS if people play their game the way they want?
What's funny is that even after Trin added the 'remove_non_electors_emperors_from_empire_effect' script there are still two or three formation decisions that allow it. One is Byzantium which can still be used for a fast revoke, though not as effectively. I actually thought that the reason the England decision worked while the France decision didn't was intended. And now since everything else has been fixed except for Byzantium I now assume they're simply careless. Although for getting double IA, abdicating/re-election or changing religions are still faster, I hope those aren't considered exploits.
I do hope the custom nation exploit gets fixed since runs that are done with those exploits can be passed off, and are, as legitimate. It's also something that goes beyond existing game mechanics and has to do with file editing. As for all the other exploits I agree.
To be fair to developers some bugs can be fixed accidentally while fixing (or changing) something else. So they might have fixed it accidentally without even being aware that such problem existed.