They've not acknowledged any of the 1.5 bugs that I'm aware of, which is just as frustrating as them not fixing them.Cheers for the communication. Have they noted the councilor secondary tasks not firing issue as a bug yet?
- 11
- 2
They've not acknowledged any of the 1.5 bugs that I'm aware of, which is just as frustrating as them not fixing them.Cheers for the communication. Have they noted the councilor secondary tasks not firing issue as a bug yet?
The bug report forum is full of confirmed bugs, including the councilor secondary tasks bug if I remember correctly.They've not acknowledged any of the 1.5 bugs that I'm aware of, which is just as frustrating as them not fixing them.
The CK3 devs are not going to be directly involved with the console version, it should all be handled by the company doing the port unless Paradox does things differently.Maybe most of their attention is on the console version ?
I agree on the council side effect bug. That one isn't game-ruining but it's pretty major. (Although on the bright side, it seems no more sinful bishop exposed!)The single bigger patches instead of smaller hotfixes is fine if we're not talking about major bugs. 1.5 introduced several major bugs that can not be held off and should be fixed as soon as the fix is ready, even if that means a small hotfix every few days. Game breaking bugs are a lot different then tweaking and balancing something. As it stands right now, the game is playable but not at it's full extent because of the various bugs. They need fixing now, not in a month.
All I can speak for is the council events bug which was fixed in hours of it's discovery by modders. For me, this is enough to make me shelf the game, and even more so when it took a single modder a couple of hours to find and fix the bug. There is NO reason, not a single one, why Paradox couldn't have had this fixed in the last patch or at any point since then. To me, it shows a complete lack of care on Paradox's side in ensure the game is working as intended and a lack of priority to get the game working as intended in a reasonable time frame.
Actually, that one still triggers, it just never shows. If you hover over the fervor of any faith, you'll see some from time to time:I agree on the council side effect bug. That one isn't game-ruining but it's pretty major. (Although on the bright side, it seems no more sinful bishop exposed!)
Actually I'm pretty sure the mod fix for the councillor tasks is a work around and not an actual fix for the issue. The issue is there is a new on action that has been created that is not firing, that is supposed to be a lot more efficient than using the old on_monthly_action call. All the mod has done is put the events back into the old on_monthly_action call, to fix the new on action would take changes to the core code, which modders can't do. (Or rather they can, but its a quick way to get you banned from here and Steam).The single bigger patches instead of smaller hotfixes is fine if we're not talking about major bugs. 1.5 introduced several major bugs that can not be held off and should be fixed as soon as the fix is ready, even if that means a small hotfix every few days. Game breaking bugs are a lot different then tweaking and balancing something. As it stands right now, the game is playable but not at it's full extent because of the various bugs. They need fixing now, not in a month.
All I can speak for is the council events bug which was fixed in hours of it's discovery by modders. For me, this is enough to make me shelf the game, and even more so when it took a single modder a couple of hours to find and fix the bug. There is NO reason, not a single one, why Paradox couldn't have had this fixed in the last patch or at any point since then. To me, it shows a complete lack of care on Paradox's side in ensure the game is working as intended and a lack of priority to get the game working as intended in a reasonable time frame.
I consider that a fix.Actually I'm pretty sure the mod fix for the councillor tasks is a work around and not an actual fix for the issue. The issue is there is a new on action that has been created that is not firing, that is supposed to be a lot more efficient than using the old on_monthly_action call. All the mod has done is put the events back into the old on_monthly_action call, to fix the new on action would take changes to the core code, which modders can't do. (Or rather they can, but its a quick way to get you banned from here and Steam).
Hehe, yeah we as users would consider that a fix.I consider that a fix.![]()
I think of it rather differently. To me, it's a fix, as it restores full functionality. What needs fixing is the new event-calling system (probably not the best term, but I trust my meaning is clear).Hehe, yeah we as users would consider that a fix.
I know from dev sides of things though that is not considered a fix![]()
Actually I'm pretty sure the mod fix for the councillor tasks is a work around and not an actual fix for the issue. The issue is there is a new on action that has been created that is not firing, that is supposed to be a lot more efficient than using the old on_monthly_action call. All the mod has done is put the events back into the old on_monthly_action call, to fix the new on action would take changes to the core code, which modders can't do. (Or rather they can, but its a quick way to get you banned from here and Steam).
Somehow that seems worse. It's not that an existing system accidentally got broken by new code. The dev team purposefully replaced an existing system with something new, but QA didn't properly confirm that the new system was working before release.
Or maybe they knew it wasn't working but had run out of time to get it functioning before release, and rather than rolling back (customer friendly option) decided to release broken and fix later (dev team friendly option).
Agreed. It is possible that fixing the bugs will require ripping-out and fixing a significant chunk of code, which would obviously take time. If this was the case, however, then I feel that the devs should be upfront about it and maybe advise people to roll-back to 1.4 for the time being.
Agreed. Even a simple "we've encountered a major bug and we're working on it but we can't reveal anything else for now" would be enough. A lack of developer communication on widespread issues tends to lead to the forums getting clogged with grumps and conspiracy theorists.In that case the delay would be understandable, but some communication from the team would be highly appreciated. Despite not being technically game-breaking, the bug affects a relevant part of game content and this prevents me from playing this release, so I'd really like to have an ETA for the fix.