It would previously refuse to format anything starting with >>, but
now it specifically filters ">> " and ">>> " to match the server, so
other lines starting with ">>" such as ">>>>>memeing" is formatted.
(This is, if you were wondering, in preparation for an implementation
of greentext)
This gives one pixel of horizontal space as overflow buffer for the
stats button in the teambuilder. It doesn't seem to improve the range
of zoom values in Chrome, but perhaps it'll help Firefox or something.
We now support searching by first letter and second word, so for instance
"rslide" in addition to "rs" will match "rock slide"
We now also support "mega" and "m" as the first word, so "mega scizor"
and "mscizor" will match "scizor-mega".
Created a new line displayed in a pokemonToolTip which mirrors the line showing the pokemon's stats. However, this new line contians stats mulitplied by their respective boosts, following Pokemon's in-game formula.
Update client-battle-tooltips.js
Update battle.js to include Unburden as a volatile. Previously, there was no way for the client to know that a Pokemon had boosted speed from Unburden. The Unburden volatile is added to a pokemon regardless of that Pokemon's ability. This is because the Pokmeon object passed into Battle.runMinor in battle.js does not have an Ability so there is no way to check if the Pokemon has Unburden.
Made all changes suggested by Zarel: Only show modified stats if there is a modified stat; bold any boosted stats; re-structure findBoost into the improved calculateModifiedStat which finds the whole group of stats rather than just one stat; include modifiers from: paralysis, burn, unburden, pure power, slow start, defeatist, swift swim, unburden, choice items, iron ball, light ball, and a rock type's Special Defense boost in the sand.
The code written does not support Gen 1 methods of stat calculation. That is a feature which requires far more research on my end in order to implement.
I am an inexperienced Javascript developer (I had never written anything in Javascript prior to starting to work on this feature a few days ago), so feel free to let me know how I could do things better.
