Maybe it will be a good idea to make a separate sub-subforum for suggestions about historical accuracy to separate them from suggestions on how to improve gameplay.
Upvote
0
Suggestion about "Suggestions"
- Thread starter Red Khan
- 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.
You mean something like 'Duke X should be Russian instead of German!'? This things belong to the bug forum I think.
Hm... Veldmarschalk moved them here... But really 'This forum is for posting your ideas on how the game can be improved or features you would like to see. ' isn't really what wrong cultures are. It should be made more clear where this threads belong too.
Exactly. And they indeed get moved here. I can understand why, it's not a bug, as in error in program, after all.
But it's not a suggestion of a new feature or improvement either. It's an error which should be corrected. So for me it belongs more to the bug forum. But currently no forum is fitting for this...
Yes, I've been mentioning that too, and I totally disagree with the new thread-moving rationale and the idea that pointing out historical inaccuracies is a a 'suggestion on how to improve the historical accuracy of the game'.
I don't want to tell P-dox and their community moderators how to run their place, and I'm fine with those threads being either in the normal bug forum or a special forum just for that type of problems, it's their decision. But lumping historical inaccuracies together with suggestions on how to improve the game is ridiculous, and it just doesn't work.
When a character has the wrong culture or dynasty or parent or age or whatever — it's a bug report, except it concerns data and not code. Not a suggestion of 'improvement'.
Like I asked one of the moderators: if I report a typo or some other language error, will that be a suggestion on how to improve the game's spelling or grammatical correctness?
It's insulting really.
The original etymology of 'bug' supposedly relates to hardware glitches, anyway, so even for code it's an extension of the meaning of the original term.
To an extent, yes, but it's still an error.
I really dislike the way fanboys rush to defend anything and everything which is not an actual scripting error as WAD and go away and die, i.e. suggest a 'feature change'.
This entire sub-forum was a mistake. Feedback - such as the data errors in culture should all be within the primary forum. Having a suggestion sub-forum is just a way to bury things so that you don't have to deal with them down the road as they gain popularity.
It is much easier to ignore everything posted in this sub-forum than actually consider what feedback is being given.
Grumpy cat mode: what's the difference where inaccuracies stored, if they are not being fixed?
The problem is that fixing a wrong date is as easy as 1-5 minutes of copy-pasting and saving to the right file for the patch if you have the authority to do it (otherwise a mail/call to someone who has it), especially if the opening poster provides the code and you can see the code is correct. Hard data accuracy issues shouldn't have to wait in the same queue as speculative feature requests or even complicated bug fixes (especially any sizeable reworks of a mechanic or anything that requires beta testing before go-live).
Well, I guess we could even have a single sticky post for discussion-free data accuracy issues. Basically the posters have to provide wikipedia links (priority before other links) and concise explanations, limited to undisputable issues or in any case without lobbying for a controversial position (like: 'according to the more established/dominant theory he really died on [date]' should still be okay).
They already often did change history and database files. But at the moment they are not in priority because they need to fix larger bugs. Ask sleight of hand how many of his database fixes were fixed by paradox. And even many of mine. It's not just on the priority list now. They need to focus on the real problems before they fix small issues. They did do it, but not currently.
Given the forum doesn't move terribly fast, I don't think splitting it further is a good idea. On the other hand, the bug report forum can move fast (particularly on the weekend) as does the main forum, so some things like database fixes can get buried (because there is little to discuss)
Could help that by keeping database fixes to just one sticky thread (or deleting the threads after putting the proposed change on a periodically aggregated to-do list).