Week 20 Developer Update

Focus: Summons and Bug Fixes

A majority of week 20 was spent setting up the structure of displaying banners/summons.

I did a couple of iterations when storing the data for summons. Reason being is that I wanted to give myself as much flexibility for the future (summon simulator) while still making sure everything was working fast.

A summon has a few sections of data that are kept separate, but have to be joined together on the page: the banner information (image, title, etc), the courses (single summon vs multi summon), the featured units, the steps (3+1; different summon steps could have different rates), the rates for each rarity, and the list of cards belonging to each rarity on the banner.

Initially, I only was focusing on the information required to just display the summons and what’s included. However, since I eventually want to have a summon simulator (even letting users “create” their own summons), I decided to spend the extra time and implement all parts now.

I also wanted the structure in place as soon as possible so that the server could start collecting data on the current banners, even if I’m not quite ready to use that data.

Getting the summon list layout was pretty easy. The animated banner images look good all going together. For the sake of time, I’m going to skip adding banner search, but keep it planned (with news search).

Patreon supporters got a quick peak and I’m almost ready to release. It probably would’ve been released already but…

Bug fixes and performance updates! yay.

One that bugged me was previously, when a new DDL update happened, a tweet would go out with an image of the new/updated cards. What happens when a DDL update happens and no new or updated cards come out? A crappy blank screenshot tweet!

My solution was to take a snapshot of the cards and a snapshot of EZA’s before the update. Then compare to another snapshot after. As I add additional things to the update screen shot, I’ll have to remember to flag them in the snapshot (I won’t remember).

I learned some new oddities with how the Dokkan leader system works (thanks AlternativeForce and MERGED), and with that knowledge, I finally fixed 200% leads showing up incorrectly on some category pages. I also learned that Dokkan can apply a leader skill to a set of characters, 170% to Goku’s Family with +30% to any Goku Card? Sounds fun.

Another fun Dokkan oddity: did you know that if a specific part of an animation is missing, Dokkan just ignores it and continues to play the animation? I sure didn’t!

For site performance, I tweaked a few things (Content Encoding priority and utilized io-uring) to hopefully improve site load speed. Has it worked?

I can’t wait for the next weekly update to talk about all the bugs and screw ups I did for the summons page release!

If you want to support the site, influence its direction, and get perks like ad-free browsing, support Dokkan Wiki on Patreon.

If you have questions, suggestions, or just want to chat, join the Discord Server.