Okay.
It was just a suggestion, as a rules based version will be a bit long winded.
I use "in memory" commands to store almost anything, monitor the values and process all kinds of things.
So in theory...
You'd need an in-memory command and sensor to set, store and recall your value
Another 3 to trigger increases, decreases and an action.
(A status command to monitor, an ON command to use on your button, and you can use the same ON command in a rule, but assign it an OFF state. ExecuteCommand"button_pressed","OFF" )
Then you'd need 3 rules to do the following...
(Probably each with a debounce timer of ~300ms)
Increase button & value = turn off increase button and increase value
Decrease button & value = turn off decrease button and decrease value
Action button & value = turn off action button and send value somewhere.
There are plenty of topics on this forum about all these subjects.
A good hunt around will find you what you need.
I'm away until Monday now, so if you are still stuck next week, I'll try to hash something together for you.
Unless one of the real rules magicians steps in and offers some more accurate help.
Good luck