Tracking Averages, Percentages, +/- Points
| Averages | Averages are a common tracking mechanism in sports - batting averages in baseball, save percentage for goalies in hockey, etc. To make an average work for your pool, simply enter a sufficiently large multiple of the average to produce the number of points you want it to earn. For example, if a save percentage is .850 put in 10 to make it worth 8.5 points, or 100 to make it worth 85 points. Negative values can also be used. |
| Percentages | Percentages are basically the same as averages - see Averages above. If percentages are expressed as whole number instead of decimals (ie 85 instead of .850) you can use decimal point values to accommodate - for example to make a save percentage of 85% worth 8.5 points, use a value of .1 (decimal 1) for save percentage |
| +/- Ratings | +/- type points generally require a
positive multiplication to work, since the +/- figure itself can be
either positive or negative at any time. For example, putting a 1 for
+/- gives a player with a +5 rating 5 points, or -5 points if he has a
rating of -5. Using 10 instead yields +50 or -50, etc.
If you're using hockey +/- points for defensemen and you don't want any player to go negative, it may not work - there is a "Point Minimum" setting you can use but that simply prevents all players from going into negative territory based on their total points, but it won't operate specifically on just one stat type like +/-. However, if +/- is the only point category in your pool that can possibly go negative, you can enter each defenseman twice, once as position DEF and once as position PM (plus minus - make a custom position) and give all non +/- points to the DEF entry, and only +/- to the PM entry in your scoring profile. Then set the "Point Minimum" to zero so the PM entry can't go below zero. Ugly, but will work if your pool insists on it. |