In the help file for contents, the category should be EVs and IVs, not EV's and IV's.
I always use apostrophes for making abbreviations plural, although I know there is debate as to what is the current "commonly accepted rule" for this. I suspect that "EVs" is the form prescribed in the Smogon style guide, so it is reasonable for the Damage Calc to follow the same convention.
There are numerous style problems in the help files (for example, I used "pokemon", not "Pokemon" or "Pokémon", all over the place) that should be corrected at some point. This doesn't just apply to the words and spelling, but to the structure of headings, bullets, bolding, linking, etc.
When I first started with the help framework, I planned to just write all the content, and then edit for style later. As the help system grew into a massive project unto itself, I changed my game plan and I wrote the styling as I went. By the end of the help sub-project, after writing and rewriting hundreds of pages of help, and programming a huge framework for auto-linking pages, highlighting widgets, auto-opening dialogs and menus, and tracking history -- I was worn out. I really just wanted to get the damn thing done. Overall, the help section was a huge pain in the ass and I seriously doubt many people even bother to look at it. So, I'm not real eager to spend much more time on it.
But, replacing "EV's" and "IV's" with "EVs" and "IVs" is a pretty simple global replace, so I'll make a note to do it.
I cannot find a way to get Unburden to activate, which matters for Gyro Ball.
Good catch. I'll probably link this to the "Ability Effect" checkbox.
"Typeless" should be an option for the Pokemon type, to account for things like a pure Flying Pokemon using Roost.
If a pokemon does not have a type, then set Type 1 and Type 2 to blank. You have to do this with the Type Dialog, not in the Type Field Text -- since a blank text will be interpreted as "no entry" and it will revert to the previous type(s). But, you can remove typing in the dialog. Perhaps a special "Pokemon Type Word" could be implemented to make it easier to remove the types through the text. Or maybe I could just allow a blank in the text (but this has other programming complications, if I'm not mistaken).
The use of a "mod" variable will lead to incorrect damage. You have to treat each element of the various "mod" variables as though they were individual multipliers (which is why I've argued against that form of writing in the article, as it leads to wrong conclusions).
I was not aware that each component of the Mod variables were calculated and rounded separately. So yeah, I came to the exact wrong conclusion that you refer to. I'll need to change up several things in the calculator to handle this properly. I will do it though, because math accuracy is very important to me for the calculator. Thanks for pointing this out, Obi.
Your calculator seems to take Reflect and Light Screen as always a 1/2 multiplier, rather than a 2/3 when 2v2 is checked. Quickly examining the source code does not reveal where the problem lies, unfortunately.
I totally missed this when implementing Light Screen and Reflect. It's easily fixed in the code. Good catch.