Printable View
Can qualifiers be used in global events?
What I mean is, let's say I want to make certain events apply to all enemies in a game, I would apply the "Enemies" qualifier to all of them, but when I go into global events, there doesn't seem to be a way to set events for the qualifier, just for each individual enemy, which I'd rather not do because it makes too much of a mess, but if there's no way to do it, than I guess I have to.
Same goes for Behaviours... :P
"Can qualifiers be used in global events? "
No, (not yet, at least) ;)
Although everyone wants this, we cannot have it... =(
I'm not so worried about it in global events, but having it in Behaviours would be nice...
The problem with having qualifiers in behaviors and global events is that when a global event, or behvaior event is run and it involves a qualifer that doesn't exist in the current frame, MMF blows up.
Make it so that it inores that specific event.
But wasn't this possible in the old CnC/TGF?
They were pretty buggy with qualifiers anyway as far as I remember, so I dunno how many people would've bothered finding out. :P
Yes, but they took it out of MMF2 because of the bugs. I wish they would find a way to put it back in, as it would make creating a game with a global event engine a dream come true ;IQuote:
Originally Posted by UnknownMonkeyman
From what I heard, I think a big part of the problem was that a qualifier could refer to one object type in one frame, and another object type in another, so referring to their actions globally would be impossible.
I've always suggested one solution to it - to always call qualifiers stuff like Bonus.Active or Collectables.String so that the object type always goes into the qualifier name.
I cant really ever imagine a situation like that coming up. For example, right now in my project I have Group.0 the entire group thats affected by my platform engine. I'm never going to put like a string or a counter in that group, I can't really think of a reason I'd want to...
Yeah, but the point is that your "Group.0" is actually "Group.0.Active" because all the objects in it are actives. In global events, MMF doesn't know what kind of objects are in the qualifier, so it has no idea whether your qualifier is "Group.0.Active" or "Group.0.String" or whatever.
If qualifiers were restricted to only one kind of object (eg active) at a whole-app level then it wouldn't be a problem.
But then I couln't do my game... :(Quote:
Originally Posted by Dynasoft