I'm looking for techniques to help me debug logic errors in my games. What do you do?
At the moment I'm using a display text rule to watch the value of an attribute, which is increasing is twice as quick as it should.
Now I need some way of tracing rules that affect this attribute.
I'm pretty sure the only way is to read through all rules one by one, but I'd love to hear from more experienced GS users about how they would tackle this.
In excel I can visually display dependents and precedents, if I'm writing something for a web site I can use the developer console / DOM inspector and it looks as though GS might be able to do something similar.
There is a good article in the knowledge base (http://help.gamesalad.com/knowledge-base/396/) and it shows that Gamesalad can do something similar,
but other than the use case mentioned in the article I can't see how to invoke this feature to make use of it for debugging.