Kurt 3c50983afd Use less efficient IsLevelWithinRange, for clarity ... See previous commit for discussion; it's easier to read and maintain this rather than have the precomputed min/max comparisons. LevelMin - minDecrease <= min && max <= LevelMax + maxIncrease; See EncounterArea7b: Since we know min and minDecrease (0) before doing the linq filter we can precompute the lowbound, same for highbound; but this isn't immediately obvious to the reader. The perf cost is pretty much negligible in the big picture, so leave it in the more readable state. Thanks @fattard & @ammako ! #2389		2019-09-19 22:54:53 -07:00
..
PKHeX.Core.Tests	Use less efficient IsLevelWithinRange, for clarity	2019-09-19 22:54:53 -07:00