tatiangMember, Sous Chef, PRO, Senior Sous-ChefPosts: 11,949
Make sure the rule conditions are set to ALL conditions rather than ANY conditions. (The default for rules is to evaluate conditions with an OR operator rather than an AND operator.)
@tatiang I found out where the problem is. I forgot to mention that "1" is actually changeable to "2" when condition A is achieved. However, in a matter of 0.00 secs, the engine also check for the second condition where [something] is not equal to "1", so I can't really judge condition 2, because it's already change to "2" and "2" is not equal to "1" at 0.00 secs. So, I fixed it by putting a timer "After 0.15 secs" on condition A.
@tatiang said:
Make sure the rule conditions are set to ALL conditions rather than ANY conditions. (The default for rules is to evaluate conditions with an OR operator rather than an AND operator.)
Thanks for mentioning that tho, that is also very important, too. but I didn't forget that part.
ahiung
Member Posts: 36
Comments
Make sure the rule conditions are set to ALL conditions rather than ANY conditions. (The default for rules is to evaluate conditions with an OR operator rather than an AND operator.)
New to GameSalad? (FAQs) | Tutorials | Templates | Greenleaf Games | Educator & Certified GameSalad User
@tatiang I found out where the problem is. I forgot to mention that "1" is actually changeable to "2" when condition A is achieved. However, in a matter of 0.00 secs, the engine also check for the second condition where [something] is not equal to "1", so I can't really judge condition 2, because it's already change to "2" and "2" is not equal to "1" at 0.00 secs. So, I fixed it by putting a timer "After 0.15 secs" on condition A.
Thanks for mentioning that tho, that is also very important, too. but I didn't forget that part.