All alpha values etc now use 0-1 (in fact anything that requires a percent), unless it explicitally uses a percent value in the property such as MXML:

height=”100%”

or in Flex where the property name states percent such as

percentHeight=100;

When expression percentages as numbers

-100 is 100 wholes, which expressed as a percent is 10000%.
- 0.5 is half a whole, which expressed as a percent is 50%.

Yes you could use the roll() method only if you want to save yourself a method call. The xSided() methods are just added for convenience and to make code look more clear.

The idea with returning an array with rolled ints surely is useful for certain operations. Maybe I’ll add that later. Thanks for pointing that out!

I think Adobe made the right move in AS 3.0 using 0 to 1 for all percents unless the % symbol is tag on. 1 is clearly the whole and therefore 100%. 100 is 10000%.

Because of the roll() method I don’t see any need for methods like tenSided(2). Am I missing something.

It would also be nice if the result was an Array showing the int for each dice that was rolled so these could be mapped to visuals if required instead of it totally all dice in the result.

Just some ideas