KaneTW
commented
7 years ago OK so:
I'm going to add a setting castTimes to the job configs, possibly with weights.
These are used to generate a step function for mapping real to effective SS, which then replaces SS in the objective.
By /u/iDervyi Here's the SS formula, which you could use to automate the tiers in your program:
=(ROUNDDOWN((ROUNDDOWN((1-ROUNDDOWN(((SS-354) * (0.13/858)),3)) * cast_time,3)) * (1-SSbuff),2))You can use it to check all of the tiers of 2.5, 3 and 3.5s casts (for nin/mnk you'll want to ensure to use huton/gl3), then use the remove duplicates function to see all the tiers and the corresponding SS values. Alternatively, you can use this: https://docs.google.com/spreadsheets/d/1UC503iaohJnz6JnnTtUEWe0z9nqWm9f8SpObE_xenXY/edit#gid=403936574 And go to the "grand sheet" tab. There, you'll see all the SS tiers. The tiers repeat from 361 -> 493 SS. So you can either take a mathematical approach, or a manual approach where your sim will read from a chart with all the SS tiers listed. If you're 1 SS V meld away from hitting a tier, that should take priority over any other meld. When it comes to relic, once you manage to fit that in, you can use the Relic to spec the required SS to hit the next tier by sacrificing Crit, rather than using melds. Any leftover SS after you've hit a tier is "dead weight", and should not be counted. As for Crit Tiers, no evidence to support it yet. Anyone claiming there are Crit tiers has 0 proof, as far as I'm concerned.