OH! I just realized the bug, bourne, when you reload the scenario, to avoid loading a user that didn't set values, as soon as you start the scenario with all red I store the red values.
This isn't a problem with the classes I'm provided, it's a bug in the world class I use, I'll try and fix it later, but I think I'm going to retire for the night, I'll probably work on it in the morning.
Fixed the 13 bug, and the limit is now 50,000 instead of 128. Just a tiny improvement. XD.
Solved it by mapping 13 to 50,001. Going to fix the 92 bug too by mapping 92 to 50,002
Sorry, didn't see your comment, but it only doesn't work past 128 if you're casting it to a byte first. Or so my theory goes (I really have next to no idea).
Oh, 16 bit translates to a maximum value of '1111111111111111' which converted into base 10 gives 65,535. I had thought that not every two-byte value combination results in a java character?
Wait, that makes sense why values higher than 57344 don't work.
bourne, when you say the range of values [55296, 57343] are bad (is bad), do you mean that values between 0 and 55296 all work when casted as characters?
2013/12/30
Reusable UserInfo Support Classes
2013/12/30
Reusable UserInfo Support Classes
2013/12/30
Reusable UserInfo Support Classes
2013/12/30
Reusable UserInfo Support Classes
2013/12/30
Reusable UserInfo Support Classes
2013/12/30
Reusable UserInfo Support Classes
2013/12/30
Reusable UserInfo Support Classes
2013/12/30
Reusable UserInfo Support Classes
2013/12/30
Reusable UserInfo Support Classes