Why are these platforms moving so wrong?

[N64Mario]

Okay, say I have 3 different colored moving platforms. I gave them their own qualifiers to keep from having to make multiple copies of the same events for different moving platforms. They should only move when I need them to. But instead, if one colored platform hits an arrow, it applies to the other colored platforms. Why is this happening?

Here's the DL link of my .mfa file to show the problem.
http://www.sendspace.com/file/cb1nxk
One platform is hitting the arrows, but making the others move awkward when they are not supposed to.

[Dynasoft]

There is definitely a bug in MMF there.

Seems comparing an alterable value of a qualifier after a collision test on that qualifier in the same event is screwing it up. It might apply to other conditions too.

I've made a much simpler version, which works fine. I'm just posting it to the file archive.
Basically I replaced:
Collision with arrow
+alt value is wrong
-multiply alt value by -1
with:
collision with arrow
-set alt value to correct number

I also got rid of the flags, and just set the alt value to 0 for not moving up/down or left/right.

EDIT: http://www.clickteam.com/epicenter/ubbthreads.php?ubb=showflat&Number=147245&#Post147 245
I also posted your broken file there in case it gets removed from "sendspace" before clickteam get a chance to investigate the bug.

[N64Mario]

Hmm...... This fix is nice, but you set an absolute value in these events for the platforms. Doesn't that lose the purpose of me setting a default velocity x and velocity y of my alterable values?
In other words, I set their velocities of X to 2 and Y to 2. But in your fix in the event editor, you set them to 1. Maybe I can make it so it still reads the fixed velocities, but change in direction when needed? Or will that bug up the movements again?

[Dynasoft]

Have a 3rd value for speed, and add X * speed and Y * speed to the position (or set the x and y to +/- speed instead of +/- 1).

[N64Mario]

So... what you're saying is, make an event to set Alterable Value A (Vel of platform to Alterable value C (Speed) to whatever I set this to? Or do I use the events in your fix, but replace the 1 with Alterable Value C (speed) of platform?

The always command is using alterable value A for velocity X, and Value B for velocity Y. And the arrow flags are just saying "set alterable value A to 1". Would't I have this say "set alterable value A to Alterable Value A *-1" or something? Or was that the very reason my version had the bugs.

[Dynasoft]

Yours had bugs because of the "Alterable Value .. of Qualifier > 0" line after a "Qualifier collides with ...". That combination seems to be broken in MMF. Your code should have worked.

Or do I use the events in your fix, but replace the 1 with Alterable Value C (speed) of platform?

This.

[N64Mario]

What is really "odd" about this is, my code seems to work well if all my platforms are copies (duplicates) of the very same platform active object. While it seems to have a bug on different kinds of moving platform objects. It's like what you said, it must be a MMF bug. X_X

But yea, I did what you said. I have Values A & B named 'Move X' and 'Move Y', and Values C & D named 'Velocity X' and 'Velocity Y' seems to work. Although I don't see why this was needed if there already is a velocity x and velocity y value from before. But I suppose since Values A & B are used to actually "move" the position of the platforms on the screen, while Values C & D are the speed/velocity values of how fast/slow they go? That's the only explanation I can come up with. @_@

[Dynasoft]

You could get away with only one "speed" (alt value C), unless you want platforms that go up at a different speed to across.

But yes, A & B are for the current movement, while your C (& D) are for the speed it CAN go.