Another one that's relatively simple; I'm hoping for allowing for tiers to take more than just booleans:
Let's say someone wanted to look at all of the pokemon lower than NU with HP greater than 90.
Short of doing
My syntactic recommendation would be:
or
Abstractly, it'd be
or
This would ultimately be an extension of already having
This would consolidate a potentially large amount of tedious writing for users, be relatively intuitive, and it should fit rather nicely with the scaffolding already present through the stats-searching modifiers and the tier-searching modifiers.Additionally, it'd help with users for Tier Shift
I'm open to ideas if anyone has any!
Tagging Thinkerino because for some reason we think very alike
Let's say someone wanted to look at all of the pokemon lower than NU with HP greater than 90.
Short of doing
/ds hp > 90, !uber, !ou, !oubl, etc., there's not really a way to do this.My syntactic recommendation would be:
/ds hp > 90, <NU, allor
/ds hp > 90, tier < NU, allAbstractly, it'd be
/ds {modifier}[tier]or
/ds tier {modifier} [tier]This would ultimately be an extension of already having
[tier] and ![tier], but with more flexibility. This would consolidate a potentially large amount of tedious writing for users, be relatively intuitive, and it should fit rather nicely with the scaffolding already present through the stats-searching modifiers and the tier-searching modifiers.
I'm open to ideas if anyone has any!
Is there a reasonable way to sort these by tier, a la
By extension:
I was thinking of building the array through the standard tier order, with the bottom of the stack ordered like:
This might require some new tier variables and/or logical construction, given that (to my knowledge) there's no easy way to look for {mons that are below PU} beyond
Ultimately, I'm not sure any of this would be necessary, but I thought I'd mention it for the sake of completeness!
ascending and the like? Not a big deal either way, but I thought I'd mention it.By extension:
I was thinking of building the array through the standard tier order, with the bottom of the stack ordered like:
<all the tiers above>
PU
(PU)
<ZU's banlist>
ZU
<everything else, if necessary>
This might require some new tier variables and/or logical construction, given that (to my knowledge) there's no easy way to look for {mons that are below PU} beyond
ZU, which aren't necessarily the same, given some mons might be banned in ZU and (if it ever becomes a formal tier) others might not even see usage there. Ultimately, I'm not sure any of this would be necessary, but I thought I'd mention it for the sake of completeness!
Tagging Thinkerino because for some reason we think very alike