Every programmer worth their salt has learned that āmy code is solidā is a feeling they canāt trust. So unless weāre going to assume that the majority of the dev team is composed of either extremely junior or simply incompetent coders, we can safely ignore the first part of that statement and focus on the second half.
āI canāt repro itā is the worst blocker you can have when trying to fix a bug. Nailing down a consistent repro for a bug is often more than half the work. This is especially true in highly complex software that has lots of moving parts. Like video games 
Thatās just normal troubleshooting checklist. You always try to eliminate the most frequent causes first:
- āIt keeps saying my password is wrong.ā
- āIs your caps lock on?ā
- āThe computer wonāt turn on when I press the button.ā
- āI put fresh batteries in my remote control and itās still not working.ā
- āDid you put the batteries in correctly?ā
And yes, sometimes people ask you to double-check youāre not running mods, because it really does sound like a problem youāve already heard about, a problem that was confirmed to be caused by mods. And guess what? Sometimes the answer is āoops, youāre right, I was running modsā 
Again, letās not conflate āno reproā with āmy code is perfectā. There is absolutely no reason to insist those two go hand in hand, or to imply that Conan Exiles devs are inexperienced, incompetent, or unprofessional.
Unlikely. But the question about why things slip through TestLive into live is a very interesting one. I would really love to be a fly on Funcomās wall and take a peek at how they do certain things. One thing I would love to take a peek at is their internal bug tracker.
See, itās not only the question of bugs not being fixed in TestLive and going to live, because there can be all sorts of reasons for that, ranging from perfectly reasonable to downright unsavory. Itās also about known bugs not being communicated in patch notes.
I can understand not being able to fix bug X because the suits have decreed that you have to meet the deadline Y, for example. The decent thing to do in that case is to include it in the patch notes under āKnown Bugsā or whatever you want to call it. But Iāve seen examples of bugs that have been reported in TestLive and acknowledged by the community managers, then reported again in live and acknowledged by the community managers again. Thatās not only discouraging to people who do us all (and Funcom) the huge favor of spending their free time on TestLive, but itās also a sign that some bugs simply slip through the cracks.
In the end, my bet is that thereās something seriously wrong with Funcomās QA practices. Not the QA team, not the devs, not the people, but the process. And, well, the process does ultimately come from the people, but itās too often the case that the process isnāt under control of the people who do the work and who get blamed for it.
Just my 2 cents.