i'm not alone in this issue and there are multiple other threads with video proof, given the absolute lack of a response i assumed it had been fixed and went back just to waste yet another death at a boss. i have not been able to play the game since monday. is it really so hard to get as much as a bloody response anymore? is this being looked into? are you aware of this? literally anyone at jagex? HELLO?
External link →Hey, sorry, it is logged in our system as a high priroity bug, so we are aware of it. I only briefly looked at it the other day and can't remember the exacts deets but it was related to your buff bar resizing. As a temporary solution you might want to try disabling/resizing your buff bar and hopefully this will stop the disconnects. I'll chase it up tomorrow to see where we are at with it.
Hi idk if you’re involved with the buff bar at all but we’re like a month+ on I’m pretty sure and they are still substantially worse than old bars.
Seriously frustrating.
buff icons constantly shifting and rearranging making it pretty much impossible to find important icons
some fonts still unreadable
timers over an hour round down to the nearest hour instead of displaying an actually useful timer
stat boosting curses still display 4 separate icons when activated
Ty
Hey, I'm not but u/JagexPoerkie was collating feedback here https://twitter.com/JagexPoerkie/status/1174014971774197760 the other week should you want to add to that.
Hey, I'm not but u/JagexPoerkie was collating feedback here https://twitter.com/JagexPoerkie/status/1174014971774197760 the other week should you want to add to that.
To further elaborate on this, it doesn't mean Twitter is the only place we collect feedback from. We also go over the forums, Discord & Reddit. Twitter is a place where feedback is often scattered around. Hence the creation of a tweet to build a space for those who wish to provide feedback via Twitter.
[deleted]
Busy weekend an all with that thing called RuneFest, so haven't had chance to reply.
We had this fixed on Thursday in our test environments and it's been merged into your release build, so you can expect to see a fix on Monday. Apologies for the inconvience caused.
devtrackers.gg