As has been pointed out a PlayerMovement object is not a float (it seems). So without some operator overloading it won’t work BUT… I always look at the code surrounding a question.
You could create a method that would increment, decrement or otherwise set the value of a property on the class. Seemingly (but I don’t know what they are doing) the PlayerMovement class could have 3 such properties representing run, ump and climb (and any others that come along). You wouldn’t need to assign 3 separate objects to them and (should it become necessary) you can set all 3 of them with common methods. Think .Reset for instance or Save/Restore.