Not a glitch, it's a feature!
I'm not sure how many times this has been asked, but why are qualifiers not supported in object behaviors? I'm aware it has something to do with the glitch, and not working properly in MMF2, but anything in particular that's making it not work correctly? The only workaround for this is the object naming glitch, which some people seem to frown upon around here. Quite frankly I find this really useful for when I want to do games that require qualifiers & global objects. But originally this is not supposed to work, since the original qualifiers can't be used in object behaviors. Even though it's a terrible glitch, and should not be considered for use, I have not had any problems with it as of yet. Everything seems to work okay on my end using them.
So.... I want to know...... What are the chances of actual REAL qualifiers being able to work in object behaviors in future builds of MMF2, without the glitches? If not MMF2, what about them being able to work in whatever MMF3 is going to be called? If this was a feature in a future release, I'd definitely make use of it, and I wouldn't have to resort to using the glitch method for my projects. Qualifiers really help me organize my games. So I don't see why it's a problem to have them work inside object behaviors. Maybe since MMF3 is being built from the ground up (so I heard), is there a greater possibility? Or are we still going to be limited to qualifiers only in frame events?
I don't mean to sound rude, or trying to advertise the use of the object naming glitch. All I'm trying to do is understand the possibilities of programming, what could be fixed, what we can do to prevent such oddities in the future builds of software for game & multimedia development tools.
