‹ BackHN Continuity

Thread

Mario Meets Pareto

739 points · 136 comments · theanonymousone

  1. uzerfcwn · · focus · HN ↗
    I did similar analysis a couple years ago for optimizing item builds in WoW classic. The tricky part in WoW is that there are 15ish item slots with hundreds of item choices for each slot, so the total number of builds is well over 100^15.

    I ended up using a divide-and-conquer style approach, where I 1) pruned items that weren't on the Pareto frontier individually for each slot, 2) took the two slots X and Y that had the least items after pruning and grouped them by calculating Z:={x+y|x∈X,y∈Y}, 3) pruned items that weren't on the Pareto frontier in Z, and 4) repeated steps 2-3 until there was only one group remaining, comprised of the full Pareto-optimal item builds.

    This ran in a couple of seconds, as opposed to the other solutions I tried that took somewhere between minutes and years. The downside was that including set bonuses into the model took extra work.

    1. r3trohack3r · · focus · HN ↗
      Fascinating! Do you still have any of the code or datasets/datasources laying around?
Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.