JagexHooli

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.

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.

Hey everyone -

Bit of a non update, but just to pre-empt any concerns, we wanted to let you know the team are still working hard on this even though we're outside studio hours now. We'll hopefully have an update to share shortly.

Did some digging with the team on this. It's essentially a case of the individual circumstances around each armour's release rather than intent.

In terms of making changes to the Set Bonus in this Strike, the focus of Strike 7 was improving the viability of use than reshaping purpose which was the big point of feedback to address.

With the Ranged / Magic T92 sets already have the bonus of not degrading in Elite Dungeons, it doesn't really fall under the remit of what we set out to achieve in this Strike. On top of that, scope wise, this update took a ton of work to bring to life - even if the patch list makes it look deceptively more straight forward than it was!

Definitely drop your suggestion into the Dojo as a consideration for a future Strike though. Hope that answers your question.

Disabling authenticator is very much not recommended - we'd strongly suggest you hold tight here. We've also determined it's not the root cause of this issue even if it unblocked you in this instance.

Our team are working hard on resolving this asap and we hope to have more details to share on it very soon. We'll keep you updated as best we can.

This was actually inspired by some of the community feedback after we released the GE Ninja Strike. Ninjas snuck it in quick!

Having been privy to part of the development of this in my first month, it took some serious work to get the T92 changes delivered. Sometimes what looks smaller on paper is bigger in practice.

It's been flagged in the past - I joined recently so I have a limited knowledge of it - but it's always worth us reheating any conversation as it crops up.

Game Development is a constantly shifting beast and, through no bad intentions, sometimes things fall to the side or prioritizations come through. Re flagging stuff is a good opportunity to bring it back to the fore to be discussed.

Drop it in the Dojo too! Perfect place for it: https://rs.game/ninja