Are you nuts?!?! I think this one definitely falls in the "nasty to implement" category. :-)
In situations like this, the problem is usually that the author is focused on solving things in a particular way - one which just won't work. However, there are often other approaches that can achieve the desired results.
So please outline to me the game mechanic(s) that you need to solve. I'll then see if I can think of a different way to accomplish that objective.
-Rob
At 06:55 AM 5/21/2006, you wrote:
Quote:
OK, I suspect this would be pretty nasty to implement, or it would be in there already, but you never know until you ask...
I want a user definable rule scope.
Something along the lines of a tag that an entity would have, so if an entity had the tag rule.one, I could on the scope of a rule set it to check entities and the children of entities that had that tag.
Possible?
|