Cutting and pasting events causing errors?

[Shawn]

I had an event that I wanted to move somewhere else simply because I wanted it more logically ordered when viewing things in the event editor. I didn't move it to a group or anything. basically it was set up like:

Line 30: do this
Line 31: event I want to move

Let's say I cut and paste 31 to be listed before line 30. Well it broke my events if I moved it. I had to keep it where it was, which isn't a big deal but it seems really strange because I wasn't missing any events at all, just simply inserted it before the other line. I tried other ways, inserting a line and redoing the events by hand then deleting line 31, didn't work. I'd post the mfa but it has quite a bit of stuff and with what I'm doing I can't really trim it down much to make it easy to pinpoint.

So it's not even really related to cutting and pasting because it didn't matter how I went about it. Basically just curious why that might possibly break things since I didn't remove any events, just moved them to a different line. With how MMF reads events it shouldn't matter what line they are on.

[Shawn]

Probably unrelated, but shortly after trying to cut and paste things I got an "Out of Memory" error. I rebooted my computer and tried again, same problem.

Edit: when I say "same problem" I meant cutting and pasting breaking things. I didn't get the Out of Memory error again.

Edit 2: the events I'm moving are "on loop" events. Do loop events need to be in chronological order in the event editor for some reason?

[gkinfinity]

It does matter how your order your events though, whether they're in a fastloop or not. If your program works while you have it ordered a certain way, leave it that way.

The problem you're dealing with is no doubt much more complicated, but here's a quick example I made that demonstrates the importance of event order.

[Shawn]

I see so when you are basically using the same event in two different lines (in this case Always) the order matters. My events are a lot more complicated, on the surface they seem unrelated but I'm sure there's a condition in there that's throwing things off. In my case I have two "on loop" events. I should go take a look at what exact conditions they are altering. Thanks for the info and example!

[gkinfinity]

Yeah no problem! It can pretty hard to find out why something isn't working quite as you expected it to. There have been several times where everything looked right to me but there ended up being something out of order that screwed it all up. I'm creating an engine for a game right now where the order must be extremely specific or it won't work at all. Troubleshooting it is going to be a serious pain lol.

[Jacob]

General Tip: Don't use spread value on the same event as you call a loop. I'm not sure why it doesn't work, but it breaks everything.