What about bounty hunting and the Pro Tem missions? A lot of times when folks accept these missions, the targets they're meant to go after don't seem to spawn.
TL;DRMissing targets are bugs the team wants to fix, and because missions depend on many subsystems the cause varies, so players are urged to keep submitting Issue Council reports, which also help prioritization.
Oh, that's sad. [...] But we look to fix them. These are bugs that we really want to smash. And as long as the community continues to use the Issue Council and help us out with that, we'll be sure to thwart all of these issues.
The last time you and Luke were on, you guys made a good point about how the missions themselves are actually dependent on multiple subsystems. A mission doesn't exist in its own ecosystem. A mission is a set of goals, but some part of those goals needs this system to function, some part of the goal needs that system to function. And the mission itself can be fine and can be functional for weeks if not months, but then when an issue happens with one of these subsystems, a part of that mission breaks, and it's actually not mission related at all. It's related to one of those subsystems. So when a mission like a Pro Tem mission breaks, one week it can be because of this system, and another week it can be because of that system, and in another patch it can be because of another subsystem. So while they always manifest in a similar symptom, the causes can actually vary from patch to patch and even from instance to instance.
Yeah, very eloquently put, I must say. That's exactly it. That's one of the really interesting things about Star Citizen. A lot of these things happen behind closed doors. We make a mission, test the mission, we get feedback, we get to improve it. But during all of that time, you guys also get to play the game in alpha. So you get to experience this ebb and flow of development firsthand. And it's really helpful, because you guys get to send us these issues too, issues that may have been missed, issues that only happen when there's 50 people on a server, all of these kinds of things. So moving forward, we love to find these bugs.
That's one of the reasons it's so important to continue to submit to the Issue Council, even if you see what seems like the same issue. Your cause may be different from Dan's cause, which may be different from Gareth's cause, even though the visible symptom is the same. Because these things touch so many subsystems, your individual occurrence may lead us down a whole different path.
It helps us prioritize too, because if enough people are reporting the same issue, we've got an internal review process where we look at the feedback that's coming in, and that helps us when we're doing our quarterly planning, and when we're doing feedback reviews and feature reviews in general. It helps us look at what the most egregious issues are, especially as we shift towards this quality of life focus. What are the things that are the most bang for buck? Well, let's look at what the feedback is and use that as a tool.