We’re disabling ranked while we clean up the current issues. For some context on what happened... 18.4 was the first patch since Set 18 launched where we shipped from the latest shared version of the game (what we call main) whereas for the first few patches of the set we were creating each patch from the one before it, so 18.2 was built from 18.1. While that live line of release was happening everything after 18.4 (patches, Set 19, modes etc) were being built in main. That meant devs had to work twice as hard and ensure they were making the same fixes in multiple versions, which was a messy process and made it harder to keep everything in sync. This sucks and we should have told you ahead of time that this patch had a higher chance of being unstable. Not communicating this risk is on us and this patch experience is on us. This was a big hump to get over for our release process and we should have shared what was going on. Patches going forward will be deployed from main again like it was for years. This should ensure we get back to the consistent patch-to-patch experience you expect and we need to deliver.

Hey folks- we know there are a host of issues with our launch of Enchanted Wilds. We’ve got a lot of work ahead of us to meet your and our own expectations. We have our team working on it, but it’s going to take us a bit to get there. We currently have a B-patch being tested internally right now with fixes to about ~24 bugs; here are a few of the bigger high priority ones: - Correct device spec & default graphic settings mismatch: right now some lower-end devices are trying to run TFT on the highest settings by default rather than the one that offers the best mix of performance & fidelity (make sure you check your settings as well to ensure they make sense for your device). - Clean up memory leaks: we’ve got a few VFX that are causing memory leaks resulting in hindered performance across mobile and PC - Responsiveness issues: fixing some bugs that are slowing down scouting/itemization - Fixed a Gnar interaction that could prevent combat from ending - Fixed an issue with overlapping music - Fixed an issue with incorrect placements at end of game - Improved start-up loading times - Finishers now abide by global volume/sfx settings The current ETA for our B-patch is tomorrow afternoon and we also have a mobile patch fix that will go out as soon as it’s approved by mobile stores. Unfortunately this isn’t a solve for everything y’all have reported, but it is the first meaningful step to shift us in the right direction (with many more to go) and were going to follow up with more micropatches and fixes ahead of our next full patch in 18.2 as we want to get these out to you all as quickly as possible.

yo- As most of you probably know TFT is going to PBE for Set 18, Enchanted Wilds in our new Unreal Engine build today. Since it’s gonna feel different and a bit crazier than a normal PBE cycle I wanted to jump in before it all opens up to set some expectations. The core gameplay loop of Set 18 is all there and we’re excited for yall to get your hands on it to start cooking up comps, playing with wisps, and telling us what works and what doesn’t. But I wanna be clear that there will also be a ton of weird and pretty janky bugs/interactions that we will need to iron out over the next month such as: •Button responsiveness: spam-clicking XP and reroll won't feel smooth and seamless yet. •UI delays: trait icons or augment panels/tooltips might take a split second to load information the first time. •Rubberbanding: units might visually jump back for a moment before moving into position. •Audio/Art: some audio hiccups that play too often or lingering VFX particles that don’t clear up after fights. and with TFT's endless combinations, there’s a ton more that we know about but also a ton that you all will help us discover in the coming days and weeks. All of that is why we’re on PBE for a full month instead of the usual two weeks. This isn't a typical cycle for balance and normal bug bashing. We’re gonna need time to knock out the stuff I mentioned above (and more) and also test a lot of under the hood stuff. A good example of that will be quite obvious when we turn on our Ranked queue on PBE (which I'm pretty sure we have never done) to make sure all of our ranked/matchmaking systems are ready for live launch. We expect things to break and your bug reports are what will get us to the most successful launch day possible in a month. Quick details for today: •Launch timing: Expect PBE to open later in the day (likely late afternoon PT) as it’s a massive deployment with all the new engine assets. There will probably be delays. Just expect it. •Downtime: Expect more instability and intermittent downtime throughout the month as we push necessary fixes, fix crashes etc.  •Bug reporting: As you run into issues plz drop them into the r/competitiveTFT Reddit PBE megathread or the bug channels in the TFT discord. Please include the full screenshot if you have them (don’t crop and instead show all the players/full screen of game etc) or even better if you have video to include. The more information the easier it is to track down. Thanks a ton for bearing with us through the initial days. They are gonna be messy, but helping us break things now is super valuable so we can get it crisp for live. This is a big and tbh kinda scary first step but we’re excited to have you gamers be part of this with us