WraithTDK Posted April 6, 2019 Author Share Posted April 6, 2019 That's the funniest response I've seen on here in weeks. You're obviously a troll. Good luck my friend. Yes, I can see how to someone like you simple logic would come off as trolling. Link to comment Share on other sites More sharing options...
Pickysaurus Posted April 7, 2019 Share Posted April 7, 2019 There was a problem with the DA:O load ordering but we deployed a fix a while back. I believe Addins.XML was being overwritten rather than appended. But since the fix was released we've had no further reports of problems. Looking at the Vortex commit history that was around 4th December. Link to comment Share on other sites More sharing options...
Tannin42 Posted April 8, 2019 Share Posted April 8, 2019 Look, again: The github issue tracker is the only official list of known issues. The forum is not because it doesn't provide a way to track the current state of issues.The thread you linked to for example with the bug Picky confirmed? That bug we worked on and consider it fixed months ago. Just because a community manager confirmed a bug 5 months ago doesn't mean that we developers know that it's still a thing today.The issue tracker tracks issues: user reports it, we report when we fix it and then close it, to tell you that we think we're done. If a user disagrees, still seeing the issue, they can tell us and we'll reopen the issue.But if you're not telling us, we keep assuming we're done. Many bugs we can't reproduce and so we depend on user feedback to know if it's resolved.Other issues may resurface at a later time, it's not uncommon that fixing bugs is like a game of whack-a-mole where fixing one bug exposes another, fix the new bug you're restoring the original one. And considering we're multiple developers (well, two) currently working on dozens of issues at the same time, we may not be making the connection right away. If we hear about a bug, fix it in the next release then 5 releases later there is a regression and the bug is in again, on a forum a user might look at the original report and see that we acknowledged the issue and assume we're working on it when really we don't know it's back and are not working on it. So this is a fact, like it or not: If the bug is not an open issue on the github tracker then we are not aware of it and are not working on it. If you want to see it fixed you need to report it.If you just talk about it on a forum, all you do is make people unhappy, you're not helping improve the situation. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.