OP Conditions
+1
Patch Insights
- NewRecently UpdatedPatch 17.8 made some fairly major changes. The largest change is Morgana is now a Conduit. Keep that in mind when playing around AP; she slots into even more boards now than before arguably.
- NewRecently UpdatedSamira and Akali have fallen off a bit after getting nerfed. Both are viable still (especially Akali), but are more situational than before and have seen decreases in overall play rate.
- NewRecently UpdatedMiss Fortune reroll comps have drastically increased in play rate thanks to the buff to Conduit and Replicator Miss Fortune modes. Try out Replicator reroll or MF + Viktor Conduit reroll (especially with the new Morgana).
- NewRecently Updated5 Anima got significantly nerfed. It's no longer an auto-win like it was in Patch 17.7.
Default
Meta
Hi all,
Quick update – It will take a bit of work to get Set 18 on the website. I do have a semi-working version of Set 18 using my existing pipeline, but it is missing a lot of data as I mentioned in my last comment and more importantly might be using some different identifiers for some entities than the new Unreal data. If I go forward with using this “legacy” data version of Set 18, I might end up making Set 18 comps with legacy data and then try to update them with new data. Without knowing how compatible they are, that might break my Team Builder serialization. It would be easier if I could just use the new Set 18 data and allow the Team Builder to use the legacy data for older sets, rather than mixing both into one set and having to deal with unintended behavior.
So what does this mean? In short, it means I want to build the full data pipeline that I need for Unreal before updating the website for Set 18. That’s going to take a bit of time, but thankfully it’s not just me that’s working on it. The community has been hard at work with figuring out the Unreal file structure and how it relates to the old data fields we understand. And truth be told, the new data formats are much better. The old files were like spaghetti code and the new ones are organized incredibly well. So even though I have to build a new pipeline, it’s not really from scratch since I already know what data I want and it’s easy to find AND the community is working together to find it all.
Lots of words to say: Please continue to be patient, thank you 🙂 Besides, PBE is all about having fun anyway so cook away!
Thank you for your continued hard work Blue, we all appreciate it!
Made some updates to the site for the last patch of Set 17. Might be a few more changes in the coming days if some major developments are made in the meta, but for now that’s mostly wraps for Set 17.
On the topic of Set 18: As of right now, it looks like getting the data will be possible using my existing data pipeline which is very good news. The bad news is that there is a lot of data missing that used to be in older sets. Some items that are exclusive to Set 18 such as Emblems do not have any data about their descriptions or the stats they provide. So you’ll probably see some “broken” tooltips when I get Set 18 onto the website. But that’s still much better than I was expecting. Of course, the larger pain point might come when they shift the client itself over to Unreal.
I am working on it every day as usual. I’ll try and post updates here occasionally as I make progress on getting the site updated for Set 18.