*Note- This tutorial *might* be useful to someone out there until ORK creates a method for linking variables and stats directly. Always check the updated features list.
There are various ways to do this in ORK, but this simple trick has proven for me to be the best, and most stable work around. At the beginning of your formula, create a 'Status Value' node and set it to what have you. Next, Create a 'Check Formula Value' node and have it see whether the current formula value equals zero. Connect the 'Failed' outcome to a 'Change Game Variables' node (I suggest making it a local variable, but it shouldn't matter).
Value Type- Value
Value- Your Variable Name (name it whatever you like. Do try at least to keep it PG.)
Remove- Nope, don't check this
Value Type- Value
So, what you've done then is you've created a new variable inside your formula and assigned it a value of 1. Next, create a plain old 'Value' node and set its 'Operator' to 'Sub', its 'Value Type' to 'Value' and give it a value of 1. This node subtracts 1 from the formula value itself. The 'Change Game Variables' node does not effect the formula value because it's isolated to effect only the specific variable that you've assigned. Anyway, moving on, your final step here is simply to connect your 'Value' node to your 'Check Formula Value' node, creating a loop. Unless you've somehow ####ed something up in following this procedure, it shouldn't be an infinite loop.
*DISCLAIMER: Neither the author of this post, nor anyone connected to the ORK Framework, are accountable for your infinite loops or any other ####-ups, and may not be held liable in a court of law. You may, however, at your discretion, post a query to the forums looking for support, which in general I've notice seems pretty good.
Where was I? Ah, yes-If your still reading, you should probably stop because there isn't really anything more to say. All you've done really is to create a looping procedure that transfers the assigned status value from your formula to a variable, and now you can simply move on and do what needs doing. If you had a good time and are sad that the party's over, by all means then go ahead and repeat the process to create another variable. The world is your oyster. I just wanted to share a little trick that's helped to keep me on many an occasion from beating my head through the wall, because I don't really have the time these days for re-plastering work and I'm assuming that neither do you. And If you're still reading by this point then I really do suggest that you stop, because that's all there is to say (and more) about this little procedure. Have fun, but remember to keep it safe. Always look to be in compliance with standard OSHA programing safety protocols, and double-check to make certain that your helmet and safety goggles are firmly secured before typing on any keyboard surface, and wear your neon vest at all times.
*Final Note- character's wearing neon receive a -8 to their stealth checks initially, plus another -2 per every additional article of neon clothing. Character's decked out in a full neon jumpsuit, or body armor, receive a +10 to all of their rolls, including saves and damage, against Lycanthrope type combatants. None of the above mentioned penalties or bonuses apply if said articles of neon clothing are worn beneath any form of non-neon cover, although various mojo related benefits may be ascribed depending on house rules. Character's wearing a combination of helmet and safety goggles are immune to critical hits.