Not a problem Corey, the vacation was a better choice!!
Glad to see you could figure it out, although I apologize for creating more work for ya!!
Thanks for tracking it down, I can actually see some benefits for spelling out the full variable names while creating some more complex formulas.
EDIT: While fiddling with my test tournament, I noticed something else minor I thought I'd mention. When viewing the result in the layout, the point totals for ranks that don't currently exist are still calculated and displayed.
For example, my current points for playing formula is :
if( totalrake=2, log((numberOfPlayers+1)/rank)*10 , 0)
[ I added the 10x multiplier simply for appearances sake. A couple of the guys complained that the point totals seemed too 'low', so I just multiplied everything by 10 and decided to be done with it.
]
For my test tournament, I have 4 players that I buy in.
So, with the layout using : <pointsforplaying orient="vertical" ranks="1-10" totalRake="2"> , I now see data and correct point totals for ranks 1 through 4, BUT I also see ranks 5 through 10 with point totals that are mathematically correct, but don't make sense. (IE, how can someone end up with rank 8 in a 4 man game?)
It's easily mitigated by changing the formula to :
if( (totalrake=2) && (rank <= numberOfPlayers), log((numberOfPlayers+1)/rank)*10, 0)
The rank check doesn't really affect the final points calculation, since in that case rank can never be larger than numberOfPlayers, but it allows for a more correct point display from the token.
Do you think it's worthwhile to extend pointsforplaying to ignore ranks that can't exist , or is it not worth the effort?
Thanks again Corey.