Decimal values are acceptable in RAIL; not acceptable in pyRO-RAIL

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Manually set a skill PriorityOffset to 0.5 in the state-file. This is 
acceptable in RAIL.
2. Load the state-file with pyRO-RAIL.
3. pyRO-RAIL gives an error message that it must be a whole number integer.

What is the expected output? What do you see instead?

I expected the GUI to allow me to use decimal numbers. Instead, it wants me to 
use only whole number integers.

What version of the product are you using? On what operating system?

v195.1

Please provide any additional information below.

All numbers in Lua support floating point. Also note that actor priority has a 
minimum limit of 1 now. This is due to the way RAIL plots monster priority onto 
its chase map.

Original issue reported on code.google.com by faithful...@gmail.com on 10 Dec 2010 at 11:10

[GoogleCodeExporter]

I have all text fields that accept numbers force an integer; are there other 
fields that are designed to accept decimal/floats?

The next release will fix the minimum for actor priority.

Original comment by landstei...@gmail.com on 10 Dec 2010 at 11:11

[GoogleCodeExporter]

Since Lua only has one datatype for numbers I think it's acceptable to have 
decimal/floats for any number, even where it doesn't quite make sense (like 
with MaxDistance).

Original comment by faithful...@gmail.com on 12 Dec 2010 at 4:23

[GoogleCodeExporter]

That's fine by me; in fact it makes the error checking much easier. As long as 
you handle the strange entries that users enter, I'll have pyRO-RAIL write them 
to the STATE file.

Original comment by landstei...@gmail.com on 13 Dec 2010 at 7:08