Red Post Collection: Mystery Skins available July 25 - July 28th and upcoming Thresh E Bugfixes

This afternoon's red post collection is short and sweet - featuring CertainlyT commenting on upcoming fixes for Thresh's E and the announcement that Mystery Skins, being able to buy yourself a random 520 RP or better skin for 490 RP, will be returning between July 25th and 28th.
Continue reading for more information!

• 7/23 PBE Update: Debonair Vi and Ezreal updates, New Sona Ability Icons
• Red Post Collection: Doom Bots Q&A, SRU Still in Works, Lyte on Restrictions, Leona and Diana portraits, and more!
• Champion and Skin sale 7/25-7/28

Pick Up a Mystery Skin for a short time!

Mystery Skins, being able to purchase yourself a random skin of 520 RP quality or higher, is back between July 25th and July 28th!
Here's Udyr with more info!

"Mystery Skins are back for a limited time so get them while they are hot! 

Purchasing a Mystery Skin will unlock an unowned skin worth 520 RP or more. As with the previous rounds of Mystery Skins, you can only unlock skins for champions you own. 

Mystery Skins will be available in the Skins tab of the store for 490 RP and are limited to five per day. Check out Mystery Skins from July 25 to July 28!"

Turkey does not seem to have this promotion as they already have another.

EDIT: As it is sure to come up, here is what you could get in a Mystery Skin:

"A skin for any Champion that your friend owns is eligible for Mystery Gifting, as long as it’s worth at least 520 RP and is available in the store. This includes Legendary and even Ultimate skins! Legacy skins will also be obtainable as a Mystery Skin EXCEPT Achievement skins, Collector’s Edition skins, PAX skins, Rusty Blitzcrank, Urf the Manatee, Championship Riven and Riot Squad Singed."

Thresh Flay Bugfix in Works

Over on reddit, CertainlyT chimed in about upcoming bug fixes for Thresh's E after a user commented on it occasionally not CCing or dealing damage.

"Quote

It's so annoying when his e doesn't cc, doesn't deal damage, or both.

Yeah, this bug is awful. I take personal blame for this. I should have spent more time trying to simplify the script and, honestly, shouldn't have taken so many liberties when making his abilities (which strained the limits of my and our department's design knowledge at every turn). 

Unfortunately, we have had a hard time stably reproducing it. I'm adding a suite of "insurance policy" measures to the spell in patch 4.14 (the patch after next) to ensure that the knockback happens reliably when it should. These changes should be on the PBE tomorrow. 

No guarantees that this will fix the problem, since we don't actually know that the cause is, but I have no longer been able to cause it to occur with them in place. That's a good sign."