GreatEmerald
commented
10 years ago Fixed by using the alternative route. It's useful to have a single function from which to control the bounds, as they may change in the future. https://github.com/GreatEmerald/libarcomage/commit/cf1942baf6fe34470ed6d72febd9d6e7fcc60e7c
There should be never a reason to normalise; instead, don't go over bounds to begin with. That's much safer, and it's important now that we can see changes as they happen. Alternatively, normalise would have to be called from each Lua function.