Rejected - Inactive Expanded /coverage commands

[Adeleine]

If you use, say, /coverage fire, ice, you will be shown the best possible matchups for this combination against every single type. This is a logical extension of what /coverage does for single items, and useful sometimes, but what is usually desired is which Pokemon do and do not resist the combination. If you do /coverage fire, it is easy to tell how dual types would interact with the coverage, but with multiple items it is not so simple. Here are some ideas, some or all of which may be useful:

/resists: shows you what Pokemon could resist or be immune to the given coverage, using both typing and factors that can be active immediately (particularly abilities). Whether pokemon could be found by this would be the same as for /ds, etc.

/resiststype: shows you what Pokemon would resist or be immune to the given coverage, using type only.

/coveragecheck target, coverage1, coverageX: shows the best possible effectiveness of the coverage against the target, including innate factors. could also have a type version as above.

/coverageoptimal target, coverage1, coverageX: shows which move has the highest power against the target. flagging moves with a symbol (Is this something we can do?) designates them as STAB.

 

[PartMan]

Have you tried /coverage Fire, Ice, all?

 

[Adeleine]

I uh... did not see that. Oops. The bottom two could still be useful but are the more situational pair.

Honestly the top two could still be useful, because they more directly show the actual specific Pokemon, and you can apply parameters like ou, natdex, etc. to them. Up to whoever reviews this, whether these are still worth doing.

 

[PartMan]

resiststype is also implemented in DS, but only for single types. It's the only one I feel could be added from the top 2 - probably as something along the lines of resists Fire+Ice, which also has competitive usage. The first one - resists that factors abilities, is probably not doable, since most abilities are possible - you don't know whether an Azumarill is gonna have Sap Sipper or Huge Power, for example.

 

[Adeleine]

if implementing the first were possible, it would probably be via assuming worst-case scenario. for azu, it means assuming it has sap sipper. so you could have full confidence in results from the calc. especially because people would probably use this to ensure that abilities are accounted for. bronzong would be awkward, though.

 

[Zarel]

Have you tried /coverage Fire, Ice, all?

Looks like this should probably be a hint in the regular `/coverage` results. Looks like its output is already HTML, so it'd be easy enough to add a button for "dual-type coverage".