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
..
236 - Tyrogue - 88A5A8BF7345.pk6	Port tests to .Net Core (#2156)	2018-11-06 15:25:35 -08:00
263 - Zigzagoon - 2746E8288E7E.pk6	Use less efficient IsLevelWithinRange, for clarity	2019-09-19 22:54:53 -07:00
280 - Ralts - 4732E9FE3B34 No Nickname Trade.pk6	Port tests to .Net Core (#2156)	2018-11-06 15:25:35 -08:00
357 ★ - Walker Mower - 0272CF40335F.pk6	Port tests to .Net Core (#2156)	2018-11-06 15:25:35 -08:00