[SOLVED] Consumable Stat Not Changing
Forum › ORK Scripting
So question: Under what circumstances would a consumable stat not change when using a Combatant>Change Status Value node in an event?
I have a status value that is at 100% of the max stat when the game begins. For testing purposes, there is a global event set to auto run that checks the status to see if it is greater than 50% and, if so, subtracts 1 from the stat roughly every second. If the check fails (because the stat not greater than 50%), then the fail fork from the check is linked to a node that is supposed to set the stat back to 100%.
The problem is that once the game starts the consumable stat is at 100% and stays at 100%. Any idea where I might be going wrong? I have other stats that I've gotten to work perfectly fine, both in my custom UI and in similar global events. With this stat, it just stays at 100% in the combatant component of the player.
I have a status value that is at 100% of the max stat when the game begins. For testing purposes, there is a global event set to auto run that checks the status to see if it is greater than 50% and, if so, subtracts 1 from the stat roughly every second. If the check fails (because the stat not greater than 50%), then the fail fork from the check is linked to a node that is supposed to set the stat back to 100%.
The problem is that once the game starts the consumable stat is at 100% and stays at 100%. Any idea where I might be going wrong? I have other stats that I've gotten to work perfectly fine, both in my custom UI and in similar global events. With this stat, it just stays at 100% in the combatant component of the player.
Post edited by dragoonleaph on
Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Categories
Latest Posts
- Equipment duplicated itself on collectionSylwester on April 19
- Leveling up equipments & Abilities with items or currencygamingislove on April 19
- I want to use Combatant's MoveAI to follow Makinom's WayPointPathgamingislove on April 19
- attacking targets 2 targets in the front or 3 targets in the front?bigman on April 18
Who's Online (1)
- kickat3000 2:02AM
If that's not the issue, check your event's setup, e.g. is an actor set up and do you use the correct actor in the nodes, etc.
If that seems correct, check the event's execution setup, e.g. in the global event or event interaction component you're using.
If you're enjoying my products, updates and support, please consider supporting me on patreon.com!
I, for some reason, had the minimum of the normal stat set to the initial value of the consumable stat. I think that kept the consumable stat from going down. But I'm now sure if that's how the minimum value on the normal stat works... seems like it though, because everything works now.