u/Tslat

Yes yes, I know for most people "just scrap it" is going to be your immediate response. I'm not really interested in that discussion, it's been had plenty of times elsewhere and isn't relevant here.

If we ignore that for a second and just focus on the idea that Jagex seems to be proposing - that Reignited is the future and it's coming whether we like it or not; I'm confused as to why I would invest time into that.

As it stands, Runescape is a significantly long journey, with thousands/tens of thousands of hours of time investment involved. That's always been ok, because there's always been an unspoken understanding that no matter how long it took, your progress was always there and always relevant.

With Reignited, that promise is forever broken. If Jagex is saying that they'll happily throw existing accounts into the recycling bin in exchange for a new player base when they need new players, how could I ever trust that if I started on Reignited, they wouldn't just do the same again in 5/10 years when they want more players again?

The very premise seemingly kills the entire trusting relationship between Jagex and the players, and I'm not sure how to reconcile that, even in the event that I decide that I've moved into the acceptance stage of grief and begrudgingly accept Reignited's existence.

Normally I'd say I'd want some kind of promise from Jagex that they'd never do it again, but at this point I'm not even sure how much a promise means?

Ever since last week's update, I've been having constant issues with some of my keybinds.

As an example, I have one key that is bound to Shift+R, and another that is bound to just R. It's been like that for a long time, and has never been a problem - if I hold Shift then press R, it triggers that keybind, if I just press R, it just triggers that keybind.

However, starting last week, doing shift + r will also trigger the r keybind. This is particularly notable when you have one bound to something like dive, where it changes your cursor to show that it properly triggered the keybind. So I can see that it's triggering the shift+r keybind, but also triggering the R keybind at the same time.

I've also noticed that if you rebind a keybind in the keybind settings menu, and hold the key a fraction of a second too long, it'll automatically trigger that keybind instantly. So my guess is something is not capturing the key input properly and it's cascading to following actions.

Has anyone else been having issues with this particularly niche thing since last week?