MMF2.5 Error: Warning! Incorrect references

The Situation:

I opened up MMF2.5 from Steam. Standard edition with the + DLC.

Opened my .mfa file from the top of the most recent files list.

Then this error box pops up, stating the following:

Warning! Incorrect references to certain objects were found in Create, Launch actions or on collision conditions. These actions and/or conditions have been removed from the events. You will have to re-enter them.

Please login to see this attachment.

Extra Info:

After clicking OK, the mfa loads fine and I have full access to it without issue.

I'm no stranger to bad object references, but I did not find a single bad object reference when making a quick scan through the frames and events.

I have not attempted to run the application yet, figured I'd ask some things here first...

It's a fairly big and dense application so going through it with a fine tooth comb would take some time...

Questions:

Is there really no way to know what was removed as implied by this error? Do I really have to comb through the entire mfa and look for things that might be missing?

Is it possible my mfa is simply corrupted? Should I save myself time and just load up an older backup, taking a small loss in progress?

Or is the mfa potentially fine and recoverable/fixable if given time and vigilance in replacing what actions and/or conditions might have been removed?

For my own application I've spent a few days just brute force testing it to see if anything went wrong, in order to locate the missing events and/or conditions.

After that, it seemed relatively fine without further issues.

All the same, it would be nice if this error left some sort of marker indicating the incorrect references/removed conditions/actions. CF2.5 already does this with bad object data, so I'm unsure why this error does not, and why it's so ambiguous in its wording and actions. Alternatively, instead of deleting the conditions and actions, the error could amend a special null or error type condition that acts like a never condition. This would give us something to spot at worse, and something to search for with the search feature at best.

[MENTION=8114]Metal_Shadow[/MENTION] I do sympathize with your situation, but my advice would be to make a back up and continue working, not letting this error halt work on your application. Possibly take some time rigorously testing the application to look for any problems that could point towards the altered events. But I wouldn't wait up for a response concerning this, as I'm not sure there is much clickteam would be able to do anyway for the present situations. Hopefully however they will acknowledge the problems with an error that removes random bits of events and work towards a better system for the future.

There has been no reply from Clickteam on this subject yet. Though I remain hopeful for some acknowledgement from them at least.

In any case, I hope that your project is fairing well and that you have not let this mishap halt your progress. I've formed a good habit of making multiple backups a day as I work, especially if I intend to start work on a major change or system. When something like this happens, it may mean hours of work lost. But that is better than losing the entire project to a corrupted mfa.

The ambiguity of this error remains a problem though. Even if it is well intended, removing bad references for the purpose of preventing mfa corruption, it still leaves the user in a fog of uncertainty with no good way to rectify the situation. Removed conditions and actions should be flagged, or incorrect references should simply be flagged without removal. I hope Clickteam sees this thread and considers this.