Literal tens of pages of bug reports in the bug reports forum going without even dev/staff response, including all of the ones linked in my signature (that I have reported personally), some of which I have identified the fix for - still no response, months and months later.
This is why I don't play CK2 or Stellaris anymore, despite having sunk lots of money and time into them.
Now that I've taken a look at your bugs, I'm starting to wonder if you're even arguing in good faith, since most of your issues were reported quite close to the patches we've gotten since the report (and it is
very unreasonable to expect the devs to always take the time to release bugfix patch N+1 just because bugfix patch N didn't fix all issues (and even more so during/just after the summer)).
The "critical" bugs:
- The Lodge mission issue is certainly annoying, but
critical is overselling it. Also, there was less than two months between when you posted the report and when the most recent patch was released, so it is far from certain that there would have been time to fix and test it, particularly with IC testing going on.
- The religious control mandate bug is probably worse than the first one, but chances was it was too late to include a fix in both 3.1.1 and 3.2.0 when you reported it, and there also wan't a whole lot of time between the report and 3.2.1.
- The sympathy bug seems even worse. Again, not a whole lot of time to fix it in any of the patches we've gotten.
- I'm not sure the MR coronation envy is a bug, as you could be envious of something even if you're not eligible for it (that might even be
why you are envious), though I've not checked if the localization would be odd in such a case. Also, there would not have been a lot of time to fix this, either, and it certainly isn't a
critical issue.
- Getting more money stolen than you have isn't necessarily a bug, considering many events can put you in the red. Also, the bug certainly isn't
critical, and there wouldn't have been a lot of time to fix it.
- The incompetent ruler modifier doesn't seem
critical, and there again wasn't a lot of time to fix it.
- The chest pain issue sounds like it is more severe than some others. Still, not a lot of time to fix it in one of the patches we've gotten, and it probably isn't
critical.
- The inability to declare war on your nomadic liege is rather severe, and might actually qualify as
critical. However, seeing as you reported it less than a week before 3.2 the only patch it realistically could have been fixed in would be 3.2.1, and there could be a plethora of reasons for not fixing it there (e.g. the bug might not have been possible to reproduce, it might only happen in very rare cases (lowering the priority), or the solution wasn't identified in time).
The minor bugs:
- The China interface bug is actually something you reported with reasonable time for them to fix. However, it isn't going to crop up very frequently, so fixing it is likely very low priority.
- The letter event gender was also reported early enough that it possibly could have been fixed. However, a localization issue is generally not high priority.
- The warrior lodge gender issue was reported fairly late. Again, localization issues are rather low priority, and female leaders of warrior lodges will normally be rare, so this bug shouldn't show up extremely frequently.
- The tooltip age issue has no impact on gameplay. I agree that it should be fixed, but it sounds like a fairly low priority thing if it only affects dead characters, and it was also reported fairly late.
- No reformed pagan religion has a tribal pillar, so that probably isn't a bug and ignoring the bug report seems very sensible in that case (though I'll agree that a "This is WAD" reply would be nice), and changing things to have reformed pillars might not make sense as a reformation might be weird enough that it wouldn't make sense to transfer a pillar. Also, there wouldn't have been a lot of time to fix it.
- The owner issue clearly is a bug, but unless it renders you ineligible to use the book it doesn't seem like it impacts gameplay. Also, there wouldn't have been a ton of time to fix it.
- The apostate burning going to the ruler instead of the regent might be something to look at, but there are various events that skip regents (or that bypass council voting for things, for that matter), so it isn't necessarily a bug (or the bug is widespread enough that it should be fixed across the board). I'll give you credit for pointing out what the solution would be, though, even if there wouldn't have been a lot of time to fix it.
- TRIGGER_CLAN_TITLE is a localization issue, which probably would be low priority. Also, it was reported
very close to 3.2's release, so it would have been unreasonable for there to have been a fix
there, and it might not have been important enough to have been included in 3.2.1.
- The self-congratulatory bug is a bit weird, but it probably isn't particularly common, so fixing it would likely have been low priority. There also wasn't a lot of time for it.
- The Hindu MO tooltip bug is clearly a bug. The localization issue is likely low priority, while the minus sign is a bit more severe, though still not something that will affect a lot of people. Also, considering you reported the issue on the same day as 3.2 was released, there's
really not been a lot of time for the devs to patch it.
As a general theme, you've also not really
provided solutions as much as you've
identified problems; I'll grant that some of the fixes would be rather obvious (e.g. if the MR coronation thing
is a bug, you should put "NOT = { government = merchant_republic_government }" or "is_feudal = yes" in the trigger), but there's still a difference between "This is wrong" and "This is wrong, and
this is how you fix it".
As for the lack of responses, I agree that that isn't ideal, but a lack of a response doesn't necessarily mean that something
won't be fixed, nor does a response guarantee a fix
will happen, and there might be good reasons not to respond to bug reports (e.g. you don't want to create the expectation that there
will be a response as that might cause even more outrage when there isn't one).
.png){kind=avatar}
