Thanks for the thoughts here - definitely something for us to go away and think about.

There is an upcoming 'PAG' branded Ninja Strike which will give you a clear look at some PAG-inspired changes. PAG Team members are also permitted to discuss anything they were involved in after it releases too, so extra details on the process around those items will trickle out beyond just what we talk about ourselves.

To provide some context, the current approach is in part to be respectful of the process of development. As Kalaya mentioned, we have over 2 years worth of Ninja Fixes via a combination of the Dojo and our first PAG alone.

The Ninja team works super hard to release as much as they do on a 2 week cadence, but game development is a constantly shifting beast - especially for a living game like Runescape. Something weeks away today may be much further down that 2 year Ninja hit list next week. We also think Ninja being able to be nimble and reactive is a big strength of their setup (personal note: so is their passion to do as much as humanly possible every update, it's kind of insane!).

The other factor we have to consider is expectations. The more we expose specifics of what came out of the PAG, the more expectations are built up that these things will happen at some point.

In the same way we can't always say we're going to change something based on online feedback until it's very close to or actually released - just in case anything goes wrong or the scope of the issue is actually much bigger than expected - the same applies here.

With two years worth of suggestions directly from our players to balance against, the desire is there to address all the PAG feedback in some way, but the reality is that the nimble nature of Ninja means we can't be sure when or if every single thing raised will be acted on. It's a valuable part of a bigger picture, as is the Dojo and as is the conversation we read online every day.

PAGs are new and we'll always be looking at how we can improve our communication around it - please keep suggestions like this coming. Hopefully this post just offers a little insight into why things are the way they are today.

PAG is very much part of a bigger picture rather than something that dictates direction or overrides the entire community. The intention is to add even more depth to the voice of our players rather than altering or detracting from it.

PAG provides the chance for the development team to have immediate conversations in a way that's difficult to have effectively at scale - and do so directly inside the development environment with a group of eloquent players that represent relevant player groups.

(On that latter note, TheRSGuy talked a lot on stream about the lengths he went to in order to recruit passionate representatives for as many types of players as he could).

Due to the process being under NDA, it also means the developers can focus on getting the most out of the PAG without having to worry about the reality of communicating in a public environment - ie. something being misconstrued or accidentally setting expectations. In the future, having the NDA process in place may also mean we can use PAGS to bring a level of player feedback into the development process earlier than we maybe could otherwise. Lots of potential here.

As I mentioned in my other post, this is very much balanced against all your amazing Dojo requests, what we see you talking about online every day and internal feedback from the team. This is just an added layer to all of that.

Right now, the team is primarily working on the next quest, with Ninja also working really hard on their beefy player-inspired Strikes every 2 weeks.

Unveiling our new quest is the next focal point of what we'll be talking about - and you won't have long to wait to hear about it (read: SOON!).

Thanks for your thoughts Rubic.

With any element of feedback, designers will always want the broadest spectrum of perspectives so they can use their design expertise to solve or embrace as many of them as possible (especially given the many different ways people play Runescape!).

From my experience so far, many JMods here (especially Ninja) are really plugged in to the community already on top of being very active players themselves. Even when you don't see a post, I can guarantee you that multiple JMods have read it as well as the CM team. There's a lot more internal understanding of the nuances of our community throughout the team than you might expect.

What this means is, when we approach a PAG, the expertise is there to be cognitive of these divisions in our community - if not already with the JMod Developers then through us as a Community Team.

I touched on this a little in my other comment, but PAG feedback is not gospel, nor does it dictate what we should or shouldn't do. The purpose of PAG is to help us to bring an added layer of player feedback in a format that we couldn't do at scale. It forms part of that bigger picture of community voice rather than defining it entirely.

I understand if you don't necessarily trust the process right now, but the end result should hopefully speak for itself - as the saying goes, the proof is in the pudding.

Thanks for the feedback on this. Fixing elements of our past communication is a focus for the team all up, so hopefully we can win back the trust around the word 'soon'... uhh... soon.

This Quest announce will be a good demonstration of that, unless something suddenly goes horrifically wrong because I jinxed us in a Reddit comment.