Perhaps the naming is misleading and they should be called something else like "ANY" blocks, so people don't approach it with the mindset of a logical OR.
Yep the name is misleading, as for me whenever I wanted to use the "Or" condition is for as simple as:
+A overlaps b
or
+Spacebar is down
These are two totally independent conditions therefore each condition check should reset from zero the Picking. The conditions above of the current condition being checked can never affect the ones below. Each runs 100% independently as if you had them in separate events instead of all in one "Or" Block.
As a result, I never use "Or" blocks for 6+ years unless in very specific cases which are clear (black or white). I have now gotten used to not using "Or" I dont need them but sometimes I miss the simplicity to make an "Or" block to tidy up the code.
In my first years, I studied how it works and I had my notes etc... But if you stop using it for some time you keep forgetting and always have to look at your notes and make a quick examples test etc... it was too much of a hassle trying to remember how it works each time you need to use an "Or" Block so I stop using them at all and I was very happy to be honest as now I dont even have to think to make the equivalent of an "Or" block as it comes naturally.
Though Would be nice if you could add a true "Or" block.
Maybe we should create a suggestion feature and see how many users want the change?
That will give you the motivation to revisit this "Or" block condition hopefully.