Destroyed objects won't paste or fade

[Shawn]

No, random(9) returns a random number in the range [0 to 9), aka 0 to 8 inclusive. This is why I believe it is a design flaw on MMF2's end.

That's my fault LB. I knew it was 0-8 I just screwed it up when I typed it :P

My first post said, "For someone just starting if you had something like random(9) they most likely think the results would be 1-9 and not 0-8. Though all you have to do to switch it to a 1 based index is random(9)+1."

[Grim_Jester]

There are many of these inconsistencies, but at least MMF2 actually tells you in the title bar:

That's a good point, but this helpful tip is not universally displayed in MMF2. For example, if I have a condition where something happens at a certain frame, no tip exists.

[Grim_Jester]

I'm glad you found the issue and corrected it. Is this really correct that the frames in an animation are 0,1,2,3 and so on!? I thought it was 1,2,3,4 and so on!? If that the case, that explains issues I've had in the past with animations not doing what they are supposed to do! Maybe a small update with the animation editor to show 0 as the first frame if what you say is correct. If it starts at 0 wouldn't it make senses that the animation editor frame window also start at 0 instead of 1..!!?

Absolutely. If they had simply labeled the frames in the editor starting with zero, I would have caught "my error" sooner. I'm going to take this to another thread. This topic needs to be discussed as a design issue. Programmers think starting from zero is normal. Non-programmers start with 1.

[KLiK-iT]

Grim_Jester,...That's why I posted it, because I had these issue and had to find out for myself what was going on,.but I got so use to it that it doesn't even bother me any more. I gotta say this though, to someone new at MMF and sitting in front of it that doesn't know,.yes to me that's a problem. 1, they might scrape the project over it,.. or 2, get pissed off and destroy the PC!!..LOL.