I've seen this "bug" a few times commented here and on the unity forums.
Mostly, it's a Tag issue.

Check your Tags.
Check if you have "empty lines" in the tag list.
If so, delete them, if not, try making a new tag to refresh the list (maybe it got corrupted).

Good luck.

Hi,

 It's a work in progress, I haven't finished it yet, but yeah that's the plan

Let me work on this this week, I'll push a package with the actions to start working with that table now that you express the will to use it.

 Bye,

 Jean

Awesome
I got to say that I love finding this little "unfinished pearls". They give a great sense of future and development.

Well, that's way more "mathy" than what I would do if my intention was just to avoid moving a larger piece on top of a smaller.

The way I'd do it would be to just record the last (top)  disk in place (without doing the sums).
That way you'd only need to check the value of the disk to be moved against the top disk on the target "stick". (easy to do by, i.e., adding a var to each "stick" that gets updated with the disk size/value when a successful move is done on it. (by considering that an empty "stick" has a "top disk value" of 0(zero).

I realize I'm not answering your question at all but hope that this alternative way can help

Here's an image ( MSPaint skills..sorry ) showing the way I'd do it to get the 1/4 and 3/4 way (because sometimes 1 image is worth 1000 words)

I don't have a lot of experience with stans assets but I do own the android native one and used it a few times in the past.
IIRC while in the editor/runtime in unity, stans assets will fetch the "store data" from it's "dummy" values, that are there present for the sake of testing and such.

I had similar issues when I used it but it was all "editor". After build (and if everything is correct in terms of keys ofc) the functions would actually fetch data from the created google play project/store.

So in sum, while in Unity, the values you're getting are from the "testing elements" and not from Google Play itself.

Put another "Get Mouse Button Down" in the Mouse Over, that links to that same State 1.
That way you can still "mouse button down" while Mouse Over is the active State.

Yeah, it's a "weird" thing. I guess it's something about the "ease" functions behind the action. Maybe it's multiplying by it and the result is less than ideal.

I remember seeing a bunch of actions that have a condition in the code to turn "0" into 0.1f. Maybe those are there to avoid that same issue. Interesting catch nonetheless.

Someone asked around for how to get the midpoint between two object and that might have been one of my first Vector math questions, so I made a couple of small actions to get a midpoint between two objects in a 2D or 3D space.