We famously have our Issue Council, deputizing a giant chunk of our community to help inform us and help with regression. What's that like? Does that make your job easier, or does it make your job harder?

It definitely doesn't make it harder, no. It maybe gives us a little bit more work to do, but there's always plenty of work to do with Star Citizen, so that's totally fine. No, we work really closely with the Player Experience guys to investigate those issues that come in from Issue Council. Like I said, those top 10 issues do come to us. We do look into them. We do make sure they're updated on the database. So you can rest assured we are definitely touching your bugs. We do see them and we do appreciate all of the info that you can give us about those particular issues, especially if it's something that's on and off. Sometimes having that stuff from the Issue Council is the key to us finding out exactly where to go and how to provide the right debug. If it's a particular thing that we didn't think of along the way, a step that we were missing, that's super useful to have. Outside of the Issue Council stuff, we do take things from the community, from the forums. If there are feedback things that we think are probably bugs, we do pick up those as well. Videos, for example, on YouTube, all of our content creators and streamers, we do get a lot of that content sent through to us saying, "Hey, have you seen this happen? Is there a bug for it? Help." And we'll usually trawl through our database for that. So yeah, it's really an interesting position here at CIG, especially in comparison to other QA roles I've done in the industry, where we are fully tight-knit with the community because we are releasing constantly. And it's an experience I've just never had before. When you're working on a project that is going to be released and shipped off and nobody else is looking at it, that's different; this gives you a whole other perspective, and you're able to do those big load tests of thousands of people, or 50 people to a server every single time, which we don't often get to do in QA. So that's really an experience I didn't expect to have when I came to this job, I guess, and has been really interesting. It is like having another crew of testers that could help us sweep everything that we need to do. How have you guys found interacting with the community?

It's really, really useful, because I know back in the day there was an issue we had at Levski where occasionally everything would go psychedelic colors. And we saw it three, four times in testing and we couldn't repro it. There was nothing we could do. It just happened every so often. And so we couldn't work out what was causing it at all. And obviously it then went to the PTU to be tested. And actually, because it gives you those extra people throwing at it, we could see what was causing it and pass that on. And it's so useful to have that information to be able to feed back. Certainly in situations like that, with things which are ultra-low reproduction, the chance of us reproducing them in standard testing is just luck, whether we get it and we can reproduce what caused it or even work it out at the time.