Array Level Builder (variation on my old editor that used ini)

**Shawn** · 17th November 2013, 08:32 PM

Yeah that should work fine if you're just using the "restart frame" event, the paste object is set to global so it will remember your value change when restarting. If you want, you could also just put the loading events in a group that you activate and deactivate as needed, but that will require additional events to clear the pasted objects and reset whatever values you need to reset upon loading the next level. I think for most purposes, simply restarting the frame is probably easiest, just depends on what exactly you're doing and if you don't want to reset everything by restarting.

**Jocastus** · 9th December 2013, 03:46 PM

Unless I've consistently made the same mistakes, global objects do not preserve their data when a frame is restarted. They do when it changes from one frame to another, but not if the frame they're part of ends or resets. I can work around this by using global values instead, but in case anyone else has had a similar issue, here's my experience.

**Shawn** · 9th December 2013, 04:17 PM

You are correct, sorry about that. Using the restart frame event does reset a global active's values.

**Jocastus** · 17th December 2013, 10:49 PM

A possible workaround that I have not tried yet: Instead of resetting the frame, "jump to" a frame whose only start of frame command is to jump back to the last frame. This would effectively reset the original frame without using the resent command.

**Shawn** · 17th December 2013, 10:56 PM

I did a quick test, and jump to frame actually works. So you could jump to the same frame and it doesn't reset the value on a global active.

**Jocastus** · 26th December 2013, 07:29 PM

Wonderful. Once again, this is an extremely useful piece of code to me, and I appreciate your sharing it.

One additional note: I use this code a lot more for pasting objects in as active objects, sometimes pasting the object into the background after and destroying that object, sometimes not. In your example the code to change the position and layer of a newly pasted object occurs in that specific object's column, but it can more conveniently be placed in the Group.Obstacles column. If you do so, the repositioning of the newly created object will still apply only to that object, and the code itself can be more easily reused for addition objects. This way, only the create object line, which must stay at the top of the action list, needs to be changed for each new object coded in.

**Shawn** · 26th December 2013, 08:02 PM

That's a good idea. One of the things I like about MMF, there's a lot of different ways to do things and optimize them. I'm glad you are getting use out of this and finding even better ways to do things!