Set 17 Meta Comps

Okay, I think the site is mostly updated. I’m patching up issues as I see them, of which there were quite a few, but the obvious ones have been patched. If you see any major issues, feel free to let me know (Discord is the best place, but can also comment here). I am going to take a break for a bit, then maybe start working on Set 17 content later tonight.

New day. Making good progress. Here’s what’s on the agenda for today:

1) Custom Champion Creator — Turns out Shen’s Relic doesn’t exist as a champion. I don’t know it counts as, but either way if I want to show it on the board, I need to add it to my champion data and have it exist as a set entity. Unfortunately, my entire pipeline for this is automated and so just manually adding a new champion is not the easiest thing in the world because several scripts write automatically to the places where champions are stored and their job is to make sure those places represent exactly what’s in game.

In other words, if I just go manually adding some nonsense champion on my own, it will get overwritten. Sooo that’s where the Custom Champion Creator comes in. It basically makes my pipeline aware “hey, this is a custom champion I added – Don’t get rid of it. Also here’s a bunch of default values that you probably don’t want to write every time you add one of these.” Or something like that. Anyway, it’ll be good to have regardless. It means I can now introduce ideas as champions that are addable to the team builder. For example, I could add a custom champion called “Tank” to represent a tank should go into an opener. Or a custom champion called “Level 8” and then make it a flex champion that shows multiple slots that could go in that slot.

This is an example of “finding extra work” while doing other things. My goal was to just add Shen’s relic when you added Shen to the board and this came to light.

2) Need to double check that a few recent changes like custom champions, summoned units (6 Dark Star, 3+ Shepherd, Shen) all work on team builder and comp pages, etc. work. Probably a lot of double checking to be honest. Making sure the change log looks good, Riot change log looks good, comp pages look good, interactability looks good, no bugs on the tier list, etc.

3) This is for AFTER I push existing changes to live, but I do want to think about figuring out all of the Space God options and programmatically creating a page for them similar to the current Unlocks Guide that just shows their options and boon. Right now I think most resources that show the Space God options are manually put together, so they won’t update as Riot makes changes. I would like to have a source that always updates as patch changes are made.

4) I think that’s it. I mean today looks like a lot of double checking and it might actually be time to push to live. Note that pushing to live is going to be a big undertaking. Git handles 99% of the work, but it won’t handle everything this time because there are database schema changes that, while I have migration scripts, will need manual checking to make 100% sure that the schema of my live site matches the new schema on the development environment. There are also a bunch of small little scripts I’ll need to run once (like updating the team builder page), small edits I need to make (e.g: special Item Categories for set items like Anima items), etc. that I have written down, but I might have missed some stuff and will figure it out as I start working through the live site.

All of this is to say is that either today or tomorrow is push day and I would be patient if there are problems on the website as it is radically changing on the backend. Absolute worst case is I botch something up and get some fatal error that takes the site down for a few minutes. Obviously going to do everything I can to avoid that, but just trying to give some warning now.