Just a quick solution, I was too lazy to report this. But since you've done it, I'll post the simple solution here:
Cmon it's never a insect
The image is replaced via regular expression. So whatever image is there we try to scale it up. It could possibly be an MCM issue or caching issue.
I'm aware of the bug, the problem is QuickFire will run JavaScript as soon as it can, but the panels that contain those images load asynchronously and live post-execution. We're attempting a new solution via XHR interceptions.Just a quick solution, I was too lazy to report this. But since you've done it, I'll post the simple solution here:
You can fix it by requesting the large version of the instead of the small version, done as shown here:
![]()
The picture structure (for avaters) here on MCM is like this:
Let's use this image as an example: http://www.mc-market.org/data/avatars/s/25/25942.jpg
You can request a "S" or "Small" by putting a "s" in between the /avatars/ and /25/ in the url.
You can request a "M" or "Medium" by putting a "m", and a large by putting a "l".
So:
Small: http://www.mc-market.org/data/avatars/s/25/25942.jpg
Medium: http://www.mc-market.org/data/avatars/m/25/25942.jpg
Large: http://www.mc-market.org/data/avatars/l/25/25942.jpg
This is because of the fact that Onyx just scales up the small version of the image, which would normally be there, instead of scaling it up and requesting the large version.
EDIT: I think I misunderstood what the issue was, it was not the quality but the wrong image. lol.
