[Solved] Boolean Issues
KickingBehinds
Member, PRO Posts: 49
I'm currently halfway through very detailed game which I have been working on for over 18 months now, however all of the sudden I am having a big issue with new booleans.
Basically, only when A is false, B should change to true.
But the opposite is happening, when A is true B is not changing to true.
Has anyone else had this happen to them?
Comments
Can you post a screenshot of the rule(s) that affect A and B? Are there other actors that change their values? How have you logged their values (either via Display Text or Log Debugging Statements)?
New to GameSalad? (FAQs) | Tutorials | Templates | Greenleaf Games | Educator & Certified GameSalad User
I don´t really understand this part. Or is there a typo?
You´re saying that when A is false, B should be true.
But now when A is true, B is not changing to true?
...I don´t get it...
Mental Donkey Games
Website - Facebook - Twitter
It was poorly worded on my part. I can't screenshot at the moment as I am on a different computer.
The game is a football game, where the rule (this is a simplified version) only when Boolean A is false (when the ball is in play) and the player walks to the ball he can pick it up. Therefore, when Boolean A is true (ball is not in play) he cannot pick the ball up.
However, what is happening is when Boolean A is true and and he walks to the ball he is picking it up.
It's doing the exact opposite of what I am asking. As I said, I have been working on this game for a long time and in the last few days I have noticed a few things like this happening (in some cases I have had to re-write rules exactly as they were for them to work), maybe I'm just going crazy?
Actually, now that I think about it, I don't get it either. Does B start out false? If so, then when A is true (and assuming you don't have a rule about when A is true), B should remain false.
New to GameSalad? (FAQs) | Tutorials | Templates | Greenleaf Games | Educator & Certified GameSalad User
Only when A is 0 then B should become 1.
But when A is 1 then B does not become 1.
Non-sequitur !?!?! Screenshots are needed.
Just a quick update, I got it working but this is the strange part, I deleted then re-wrote the rule exactly as it was before. Not close to, but exactly the same as it was before and now it is working.