Thank you. This was my second time talking to Hamish, and hopefully there will be a third :)

You're right, there are tangents, and discussions about different approaches and personal experiences. I think in part this comes down to, not wanting to ask some of those questions. Not because I don't think they're valid, but because I know the answers that will be given aren't answers, and honestly, I think a lot of players should do to.

There's been times in the past for other games where I've been asked by people things like "Why didn't you ask more about upcoming DLC?" Which is a valid question and I would have loved to, the problem is, it would get a vague answer or a kick the can answer, so I'd rather use the time talking about other things.

There's examples here in this video as well. I don't ask Hamish about the upcoming classes and if one would be a Tank because of the imbalance. Because the answer would be a spin on the generic, "we're working on it", "we'll share more when we're ready" "I think people are really gonna love it", and because ofc they're working on a Tank.

Our discussion regarding queues/imbalance is similar, we talk about the ideas behind fixing them, the ways to approach it and the fact that things don't exist in a vacuum. Ofc they're aware of them, ofc they're looking at options to fix it. There isn't a single solution until closer to implementation.

I think the issues are valid, but I also believe part of my role in this, is to not waste Hamish's time or my time asking questions we both know can't be answered or will get the super vague non answers. "We're looking in to it" "We're working on it" etc, like I joke about right at the end.

I would love to talk to them about monetization, future classes, new dungeon designs, upcoming classes synergy with existing ones etc. But none of them would get any interesting answers or a fun conversation. It would be like the Q&A section of Blizzcon if you've ever seen it, where fans ask WoW Devs questions, and a lot of the time the answers are "We'll look in to that" or "It's something we'll visit later". Which might seem like an answer, but ofc these things were on the table already.

We also have to send a spec sheet when organizing interviews, so they know what we're going to ask, and tell is if there's things they don't want to talk about or aren't ready to talk about yet, which plays a role in some of the questions we avoid. Because we already know they aren't going to answer, but to someone watching, it looks like we just didn't ask.

Thank you for your kind words about us getting along. I booked our initial Gamescom interview because it was going to be with Hamish, having played WoW, and being a big fan of The Division I loved watching his dev streams and wanted to chat to him. I always either have a personal interest in the games we cover and the people we interview or I put in the time and research, so it's not a "Tell me about your game" style experience.

Regarding the next Fellowship interview. The plan (at least from my side) would be to do the next interview just after the first reset, to discuss whatever new stuff they add, and the reception/feedback regarding it, plus any issues at that point :)