Updates keep crashing works-in-progress

[amorgan]

The "save/load frame function" seems terribly useful, but this update (and most updates in general) reek havoc on a game that I have been working on for awhile, and which has extensive coding.

For example, build #245 caused some sounds to disappear and some key inputs to fail without any obvious reason. This happened with the 244 build as well, and after downloading the 244 I had to revert back to the 243 for the game to work, and then when I had plenty of time to waste I re-downloaded the 244 and fixed all the stuff it had changed.

I can't even tell why the 245 is fooling with my game, but for now the 244 will have to suffice.

Has anyone else had this problem with updates?

[amorgan]

One problem is that the following command no longer works:

IF
-Only one when action repeats
-Numpad "0" is pressed
-X Repeat "Shift" is pressed
-X Repeat "D" is pressed

THEN
Add 1 to Counter "A"

For some reason, this simple event stops working with the new build. The counter does not change, and there is no other code that would prevent it from doing so.

[Sarah]

I confirm there is a difference between build 244 and 245 with this event.

However - do you need the Only one action when event loops condition at all?

You also get a different result by making the OOAWEL condition the last one in the event - the event only triggers once and never again.

[Sphax]

In this event, you should not use "Only one action when event loops" because the "Numpad "0" is pressed" is a "one shot" condition.

[amorgan]

I'll try that, thanks. In the past though, if I didn't put in "Only one action when event loops" it would continue to add to the counter.

[00J]

it's your coding methods, you should read up on how to code your code. Some code events will cancel out others.

MMF executes events in a certain order, such as collision events, start of frame events etc...

MMF goes through (loops) through your events list from top to bottom, and some events always get executed before everything else.

[Francois]

About the bug.
I have found why it happens, and I'm afraid tehre is not much I can do about it. To restrict repeating actions in the events, I have to use internal counters in the group of event. I only have two counters.
Here you use two conditions restricted : Once when event repeats, and User presses key. They both share the same counter. I could make one of them use the other counter, but this would create other problems.
Anyway, there is no need to use the Once when event repeat condition, as the Key pressed condition is one shot. Just remove it and it works.

[Sphax]

Francois, "Once when event repeats" is a better name than "Only one action when event loops". You should change it int the event editor.