Rule being triggered when attributes are not appropriately true
ARC_Games
Member Posts: 78
I am encountering a strange situation where a Rule behavior that is nested inside of a couple of other Rule behaviors is being triggered even though the conditions for the outer Rules that contain it are not true. The condition for the nested Rule is true, but it should not be triggering because the conditions for the outer Rules in which it is nested are NOT true. I used the debugger extensively to locate and discover this being the root of the issue. This is in GS .82, not the newest update of today's release.
Anyone else experience anything similar? I have reported this to the GS team by way of the feedback for bug reporting. This is the kind of gremlin that can cause some serious damage to a project. It was very unexpected behavior, hard to diagnose, and it is causing very strange results in my game project.
Anyone else experience anything similar? I have reported this to the GS team by way of the feedback for bug reporting. This is the kind of gremlin that can cause some serious damage to a project. It was very unexpected behavior, hard to diagnose, and it is causing very strange results in my game project.
Comments
Rule A [
behaviors...
]
Otherwise [
behaviors....
Rule B [
behaviors.....
Rule C
]
and "Rule C" here is the one that is being triggered, even though the conditions of the containing rules are not logically true at the time that the nested "Rule C" is being triggered due to it's own logical condition being true. Being nested inside of the other rules however, "Rule C" should not be getting triggered in this situation, but it does get triggered, and hence, my project is acting strange. Apparently, GS is treating this "Rule C" as if it were not nested inside of the other two Rule behaviors, and evaluating it as if it were not nested inside the other rules at all. As far as I can tell, none of the other behaviors contained inside of these nested Rules are being executed in this situation, only the behaviors of "Rule C" when its own condition becomes true.
Very odd.
maybe if I delete the "Rule C" behavior, then save the file, close GS, and then re-open GS and put the "Rule C" behavior back into the project, it will then miraculously work properly as it should?
not sure what to do.... anyone care to share your thoughts?
But, when the "Rule C" is placed there to contain these behaviors, they shouldn't have been getting executed then either, because even though "Rule C" tests for a condition that is true, it is nested inside of the other Rules that have conditions that are false, so the code for "Rule C" shouldn't even be getting tested at all in this situation.
I am certain that there is some kind of strange bug in GameSalad related to this issue.
another thing that might affect the behavior here, although it should not, is that there is another Rule elsewhere contained in this actor that also tests for the same boolean attribute as "Rule C", but it is not nested in the other rules as described above and it contains different behaviors than "Rule C".
Instead of nesting rule c ,
Make a self.attribute - boolean , call it "trigger rule c"
Make rule C independent and wrap it in a rule :
When self.trigger rule c IS TRUE
DO rule C .
All thats left is to change "trigger rule c" to true when you want it to trigger .
Hope it helps (not sure)
Roy.
Nevertheless, I am now experiencing this same type of issue with another nested Rule that I have newly placed into a different section of this same actor's behaviors. Once again, I am getting the VERY STRANGE result that a nested Rule is being triggered when the conditions for the Rules that contain it are not true.
GameSalad should NOT be producing this kind of strange behavior. It obviously makes it impossible to use the software if the most basic logic functions are not producing the intended results. This is not good. I am very frustrated by this.
This particular actor is my game's main character, the game's hero of sorts, and he is a multifunctional character, which has resulted in this actor containing quite a large number of behaviors (even though I have made a concerted effort to streamline them as much as possible). Does gamesalad have some sort of limit on the number of behaviors that can be contained inside of a single actor, beyond which the actor's Rule behaviors will not properly function??? If so, please let me know.
It's not been a huge problem for me on my current game, just something I noticed when playing with someone else's project for them. I haven't had the time to play around with it to see if there were conflicting rules/the layer order was correct, etc.
Ace
I'm still on version .82, which is the first version that has ever caused me to have this problem with nested Rule behaviors that misfire. This is a critically serious issue, and one that if not addressed and fixed by the GS team, will result in me not being able to use GS anymore.
Please, I beg of you GameSalad team to fix this issue as soon as it is humanly possible for you to do so. Thank you :-)
This seems like a big issue if its not a problem with your code , i suggest you submit your project to GS so they can see the problem with their own eyes and solve this cause this is important!
Roy.
this bug with the nested Rules not working is probably causing a lot of other people to have problems with their GS projects, they just might not have debugged it as thoroughly as I did to discover that this is the problem. In terms of significance, this issue is equivalent to a processor's ALU giving a result of 2 + 2 = 7. It is IMPOSSIBLE for me to move forward on my game project until the GS team fixes this issue. It is a critical issue that needs to be fixed about two weeks ago!
SaladStraightShooter, could you please confirm for me brother that the programmers at GS are looking into this MAJOR bug issue, and that they are fixing it? Thanks mate. Until the problem is fixed, my project that I've been working on for over a year is on hold... there is nothing I can do until you guys fix this bug.
anyone else who is experiencing this bug, please comment here and also send a bug report to GS using the feedback system. thanks, let's get them to fix this before it ruins all of our projects.
SaladStraightShooter, can you please get some confirmation for me that the GS team is aware of this bug and making an effort to fix it???
I appreciate that a patch is in the works for some of the other bugs, but I would greatly hope that this bug will be fixed in the newest patch as well.