The ability to clone, delete, load, and save individual layouts during game execution.

[quote:kdtkumj9]Sometimes you only need to create an object to do something specific and after that you don't need it anymore. But unfortunately object loaded into a memory will stay there until next layout and of you have few that kind of object then this is simply a waste of memory.

I wonder: would the memory for deleted objects be reclaimed if we set the layout static, go to another layout, and then return to the static layout? If so, then we have a workaround that you need to have the user swap out to a different scene from time to time.

Personally, I would like the ability to create scenes and delete scenes during runtime. Again, quite useful for open-world scenarios.

So here's what I am imagining I want to do:

• Have an tilemap overmap reminiscent of early Ultima games.
• Give the players the ability to "look closer" at any tilemap on the overmap, doing potential things such as foraging for supplies, hunting local game, ect.
• "Looking closer" will pretty much take an existing layout, duplicate a copy of it that is set persistent, this layout would have all the code it needs to dynamically generate some cool terrain and things.
• After being generated, the "Looking closer" layout will leave a pointer between the overmap tile and this new layout, thus allowing the player to return there whenever they want.

I am mostly hung up because it does not look like Construct 2 has any means to dynamically create new layouts, let alone copy an existing layout.

The most obvious workaround is to simply recycle the same existing "looking closer" layout, but this would mean I am losing any persistence in that layout. That's what games like "Ultima" and "Oregon Trial" did, back in the day. However, in the spirit of trying to preserve come coherence to the virtual world, what I am looking for is more of a "Dwarf Fortress" approach, if possible, where the smaller "looking closer" layouts are saved and associated with their respective positions on the overmap.

Any ideas?

Hello everybody.

I've been gaming for some 30 years now, and let me tell you: there's not enough new under the sun to keep this gaming habit going. So that's basically my primary motivation driving me to see if I can't just leverage some of that experience by becoming a game developer. Plus, it's good creative and intellectual practice!

Though I've dabbled a bit with development in the past, I usually quit in a snit of cognitive dissonance before seeing the game to completion. I am hoping Construct 2's rapid prototyping capacity is going to turn that around by allowing me to decide what I want to commit to making before I run out of steam.