JagexHooli

That's what we're saying about walking the line. We don't want everything to be a surprise, but we do want to talk about things at the right time in the right way.

The intention we are driving as a Community Team right now is provide ways to give better insight into what we're working on, provide regular development updates and so on - but not necessarily by just revealing and promising content. It's about keeping you informed while also talking about the right things at the right times.

We want to move away from our past hit-rate of announcement accuracy, but not at the cost of keeping you in the dark entirely about what's kind of things are in development, where we are headed and so on.

That's the goal.

The last three months have been a reflection of the impact to productivity that working from home has had on the team, as people work around their home lives - in less than ideal setups, managing childcare or homeschooling, the mental stresses of working where you live etc. I can speak to my own experience, moving half way around the world for this job only 6 weeks ago, to say how hard it is to do this from home vs the studio.

Simply put, sticking to the existing plans we had simply wouldn't work for either us as developers or you as players - the gaps on those bigger pieces of content would be much bigger than anyone would like to see.

Instead, the team took the initiative and adapted our approach to the reduced capacity. What this new approach does is minimize the chance of significant gaps between additive content, with a goal of delivering on a monthly cadence as soon as we can.

The team are throwing themselves at this challenge ...

We don't disagree on the leaving you hanging front. While I believe Warden made a mention here or there about moving away from road maps in streams a few months ago, it obviously didn't come across (which is on us, not you as players). That's the reason we made sure to tackle it head on today.

As we mentioned on stream today, this is what should be considered an opening of the door. This was intended to be a honest look at where we are development wise, indications of what to expect, what we are aiming for, and what we won't be doing. It's only a first step, but it's a step.

Moving forward, the goal is to offer a better level of transparency and access into what's going on around the game - but not in the form of a roadmap. There's memes around content announcements vs delivery in this community for a reason, and we want to leave that reality as a by-gone era for Jagex.

Again, this doesn't mean an intention to keep the curtain fully drawn. We'll just be meas...

Thanks for your report on this - the team acknowledge that 'put a' is a common part of standard sentences and we're going to remove this from the hard filter as soon as we can. We'll be continuing to monitor for similar reports and assess on a case by case basis.

We know the solution is imperfect, but as we mentioned in the post announcing this change, it's just an initial step we can take to help make our community a more inclusive and representative place to be - now rather than later.

Phenomenal.

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.

This post was our update on the investigation: https://secure.runescape.com/m=news/a=13/update-account-recovery-requests-june-13th-14th

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 wh...

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!).

More of a miss of the comment, sorry.

Feel free to PM me full thoughts on this.

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 proc...

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 st...

Update: June 30th 16:00 BST

Following our investigation, we have deployed an update for Runescape Mobile Android Early Access and the RuneScape iOS Closed Beta that resolves the log-in issues on both platforms.

Unfortunately, due to the way the RuneScape iOS Closed Beta operates, this fix may take up to 24 hours to take effect on Apple platforms. Once the update for iOS becomes available, you'll need to grab the latest version from the TestFlight app. If you have notifications enabled, you'll receive one as soon as it arrives.

Thanks for your patience while we got this fixed. See you out there in Gielinor.

Hey everyone. We've got another update on this for our Mobile Users as promised.

Following our investigation, we have deployed an update for Runescape Mobile Android Early Access and the RuneScape iOS Closed Beta that resolves the log-in issues on both platforms.

Unfortunately, due to the way the RuneScape iOS Closed Beta operates, this fix may take up to 24 hours to take effect on Apple platforms. Once the update for iOS becomes available, you'll need to grab the latest version from the TestFlight app. If you have notifications enabled, you'll receive one as soon as it arrives.

Thanks for your patience while we got this fixed. See you out there in Gielinor.

The RuneScape Team

The team have notified me this is generally something that occurs around a client release and should only have been a passing problem. Can you confirm you are able to Altscape again?

We've flagged this to our team to take a look at, though we're looking at tomorrow for any progress on this understandably. It's on our radar to investigate along with the mobile fixes.

Passing the report to the team. Thanks.

1 hour ago

There's another issue that I haven't seen mentioned elsewhere. I can't altscape anymore, multiple copies of the client can't be open simultaneously because they close themselves down. The command prompt says that it's treating it as logging out, even though the 2nd client never fully loaded in the first place.

Thanks for this report. Passing it to the team.

In case you missed our latest update in the new Reddit thread:

Update: June 29th 7:45pm BST

We have deployed an update to our Desktop Client to resolve the login issues impacting some users. If you were unable to login on Desktop, please close and re-open your client to resolve the issue. Thanks so much for your patience as we worked on getting a fix live.

This situation is ongoing for Android Early Access and iOS TestFlight. Over the course of today, it has become apparent the issue on Mobile platforms has additional complexities that require further investigation before we can reach a resolution. Based on the information available to us, no fix is in sight for tonight (June 29th). Our team are prioritizing this work and we'll provide any updates on our Early Access / TestFlight Clients as we have them.