Adam

That's just what RS3 says if there's any connection issue at all, nothing to do with the launcher. Could be on your end or theirs. On Tue, 31 Dec 2024,...

A mechanism like that would have to assume that everyone is using flatpak for everything, which they may not be. It would also go against flathub's app guidelines which say...

Bolt is very much designed to manage its own packages. The "custom jar path" exists for people who might want to make source builds on their own PC, but even...

By "filter" I mean deleting every item that matches some condition. I don't need to extract them. Resetting the loop each time might be the best method for now (and...

Yeah, that'd work for me. The only other option I could think of would be if, internally, you could do multiple deletions at once without moving anything, them do all...

That would incur at least one or two new heap allocations, which doesn't seem necessary here. Your loop-resetting solution would be more efficient than that.

The only way to do this would be in the C++ CEF code - it wouldn't be possible to do this from the svelte UI. That part runs inside a...

It just does that sometimes. The official launcher is the same (i.e. issue on Jagex's end.) All you can do is close the launcher and try again after a few...

PULSE_LATENCY_MSEC is the usual fix, not sure what else to suggest. I suppose if you're using pulseaudio you could try changing to wireplumber? It's usually much better.

Sorry didn't respond sooner, I would suggest setting this env var only for RS3 instead of system-wide if you don't have the issue anywhere else, because setting it anywhere else...