OG credit to: Henry Hinnefeld 2015: https://hinnefe2.github.io/python/tools/2015/09/21/mario-kar...
Mario Meets Pareto
141–150 of 177 posts
Re: Mario Meets Pareto
#142I 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…
Re: Mario Meets Pareto
#143Earlier quoted context omitted.
Very much so. It's one of the worst cases (but not the worst, not even the worst this week) I've seen around here.
What's broken about the scroll? For me it acts like basically any other scrolling presentation design used on hundreds of different websites.
This page has some elements that scroll and some elements that don't scroll. And some elements that switch between scrolling and not scrolling. And some animations are controlled by scroll position, meaning they bounce back and forth while I try to find my bearings on the scroll wheel. Everything is fighting for my attention all at once, which prevents me from focusing on anything in particular. Most of all, it prevents me from focusing on the scrolling itself - and scrolling requires extreme focus here considering you never know what will happen and how much you need to scroll for it to happen. Is text going to slide in? Is a picture going to suddenly pop up? Is an existing picture going to transform to something else? Will it transform gradually as I scroll, or is it going to do it all suddenly in one step?
In short - it breaks the UI metaphor of scrolling an infinite roll of paper, and that in turn breaks my brain. I just can't follow what's happening, there's too much non-scrolling action happening when I scroll. There's also too much empty space between paragraphs.
Re: Mario Meets Pareto
#144> You probably won't pick a driver sitting on the edge of the frontier because you want some balance between speed and acceleration for super mario kart speedruns go with bowser/dk: https://www.speedrun.com/smk/runs/zp68nr8m That seemed to hold up for Mario Kart 8 too going with Bowser at the edge of their pareto frontier, https://www.speedrun.com/mk8 needing acceleration is a skill issue
Adding skill is just another dimension to the calculation.
Re: Mario Meets Pareto
#145[0] A redshell wall break is when you point your vehicle near a wall to break a redshell without using a defense item. [1] Drifting style is either inward or outward. Inward drift has more intuitive controlls and is way better for intermidiate players, but pro players dislike it because is removes various difficult tricks.
I recommend yoshi on the yoshi bike with azure rollers and the paper glider.
Re: Mario Meets Pareto
#146I 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…
Fascinating! Do you still have any of the code or datasets/datasources laying around?
Re: Mario Meets Pareto
#147Earlier quoted context omitted.
there's something equivalent in the business world - mostly used by businesses not run by psychopaths - where you optimize inside 2 triangles with the points on the triangle being cost, profit, & user utility/happiness.
Are they conjoined triangles?
Re: Mario Meets Pareto
#148This is a really important concept for developers. One aspect for developers that I see quite often is the assertion that "We can't have X without giving up more Y", most commonly "we can't have more security without giving up on user experience". With the Pareto idea in mind, we can see that that statement is true, if and only if you are in fact on the Pareto frontier of security and user experience already. However…
"making tradeoffs" is an excuse for management to cut corners to get their feature faster at the cost of future developer pain and suffering you know how japanese oni would roll human souls into soba noodles? [1] that's what modern corporate software company management does :) [1] i learned about this from the very funny gintama funeral episode