Hi MeanDelay,
I still am running into bugs with the point comparison requirements. I have no idea why they are so funky. As an example: If I have a Point feature which is currently set to "4", I can add a requirement that a choice is only selectable if the point value is "less than 8" and this works fine. In fact, as long as the two numbers being compared are both less than 10, everything works as expected.
However, something funky happens when one of the two numbers is at 10 or more. Using the same example above (a point value is currently set to 4), if I change the requirement from "less than 8" to "Less than 10" it will make the choice invalid.
Here's what I think is happening based on my tests. When evaluating point values in the single digits, it causes this error because it's ordering numbers thusly:
1
10
11
12
...
19
2
20
21
22
...
29
3
30
31
etc.
A bit of experimenting shows that this appears to be the case. It is slotting single digit numbers just before their 10-fold bigger brother. If I do a test with a requirement to be 'less than 3', then the requirement is met for point values of 1, 2, 10, 11, 12, 28, & 29. But it is NOT being met for 4, 5, 6, 31, 32, 33, etc.
For my current project I'll simply bump the point values up by an order of magnitude (things which used to give 2 points will now give 20 points) so that everything evaluates correctly. Hope to see this fixed in the next version!