Global objects not preserving data between frames?

[Jocastus]

Hello! Having a little trouble again and hoping somehow can help me out.

Shouldn't global objects always preserve alterable values and behaviors and such from one frame to another? If, for example, I store an alterable value of two in an instance of an object in one frame, shouldn't that same two appear in all instances of that object in all frames? I'd thought this was the case, but now I'm not seeing that.

My specific problem: I've got an active object that I'm using as a monster in a game. I've given him an alterable value for HP and some behaviors to code movement and such. But if I make a change in one frame (if I alter his HP or give him a new behavior), that change doesn't register in the others frames.

Even if delete all the instances of said objects in a frame, then copy the original over from another frame, no changes made in one frame are applying to instances of that object in the other frames despite their "global" status.

If I'm totally misunderstanding things, could someone correct me on what effects the global object status includes?

Otherwise I guess I'm looking for a way to just be able to stamp down the exact same object in different frames, and have all instances of that object in all frames change when any one instance changes. Is that possible?

Thanks for any help you can give! I appreciate it!


UPDATE:

OK, I found a work around. If I create a brand new active object and mark it global from the very start, then it behaves the way I'd expect it too. But the old object to which I referred above maintains it's stubborn unwillingness to update changes across frames.

I think this all has something to do with the fact that the object in question was not originally a global object. I made it one AFTER I had copied it to other frames (forgetting it wasn't global yet). Somehow that made each frame protect it's own version, I guess?

I'd still like to hear any thoughts you have on what I did wrong originally, although for now it looks like I can just delete the old stubborn objects and replace them with new ones.

[Yves]

This is a bug, which is not yet fixed.

I think this problem happens when you copy/paste a global object with behaviors. For some reason the content of the behavior is slightly different in the pasted instance, so MMF thinks it's a different object and no longer reports the changes from/to other instances of the object in the application. This issue is not yet fixed.

In a future version I'll probably add an option to force a global object to be updated even if it's different, to get rid of this issue.

[Jocastus]

Ah, thanks for explaining. It's nice to know it wasn't just me. For the time being I'm making things work, but I'll be eagerly awaiting any updates for this issue in the program.

Thanks again!