A week or two ago I ran into a situation where I had an integer variable and wanted to use it to modify the difficulty of a wheel challenge. I used an "offset wheel difficulty" action to do this. I did some trial and error with it and it seemed to behave in these ways:

0 sets the difficulty to quite a hard value and causes the wheel to ignore the difficulty setting in the wheel action ('easy' and 'very difficult' will spin at the same speed following an offset)
999 and -999 both produce a very very slow spin
1 produces quite a slow spin, -1 produces a fast spin
The effect seem cumulaitve, running two "offset -1" actions seems to have the same effect as a single "offset -2" action
The change applies to spins within the encounter but then goes away

After a bit of tinkering running at
0 very hard
-4 hard
-7 normal
-9 easy
worked just fine.

Fast forward to today and the encounter is behaving differently. I've done a couple of SDK updates so possibly something has changed? The featuers I'm observing today are:

The difficulty seems to vary from the value set in the wheel. Offset 0 and 'easy' gives a slow spin, offset 0 and 'very difficult' gives a fast spin
A change of -1 can change the wheel from "spinning too fast to see" to "spinning so slowly it only moves one card" The function cannot take fractional values.
The offset is permenent and applies to every other wheel encounter the user encounters in the same challenge (possibly only the same floor?)

I'm guessing one of these sets of behaviours is some kind of bug?
How is this function supposed to behave?
Is it the best way to set wheel spin difficulty based on an int or should I use the variable some other way?