Came in here to ask about unusual prioritization of leech for my druid, but I think I solved it. Along the way, however, I found some aspects of the interface I think could be improved.
The gearing strategy that initially produced the question is this one. In the stat weights box, it does clearly place a high value on leech, but that box is apparently disabled because I’ve selected machine learning. If those values are still relevant, even when machine learning is chosen, they should be shown as such. Leech is also not included in the machine learning examples, which is defensible (how would you farm for it?), but it furthers the impression that the leech weight below is not being used.
Selecting the current default Ursoc script and converting it to machine learning produced results more in line with my expectations. The only difference between these two strategies are the version number and the stat weights. I doubt that the minor version difference produced the difference I see, so I’m left thinking that the apparently disabled stat weights do, counter to my intuition, matter very much. I would have thought that machine learning disregards all user input except for the rotation, boss, and so on at the very top of the page.
That leads to my next concern. Why can’t those values be chosen on this page? The current design forces the choice between the default Mythic+ and Ursoc scripts on the character page, and then requires each to be opened on a separate gearing strategy page to enable machine learning. I feel like the choices of script and gearing strategy are part of the same workflow and should occur in same place.