That makes sense. Thanks, this game is intended for mobile so performance is a big concern.

I have been using arrays to save relevant room data for my generated dungeons. I had a thought though, and wanted to run it by folks who might know C2 under the hood a little better than I.

What if I just moved all dungeon objects outside of the layout when not using that level, then moved them back when returning to that level? Can you shift the view window or layout area around areas outside of the original layout position, or does that not make sense because locations in C2 are defined by the layout? What about making a HUGE layout and we shift the view window? Will mobs, etc still be active when they are outside the layout? I am trying to figure out the ramifications of doing things this way instead of saving them in arrays. Ultimately, the level data has to get stored in some form so that it's all preserved when C2 makes a savegame.

Anybody got any thoughts on this?

Thanks.

How do I view local variables in the debugger? I can find the globals, but I need to keep an eye on some of the locals too. Can't find where they are listed.

Autosave is on, the file I've been working on is a .caproj. Should be nearly instant, right?

Thanks, Ill check how it's set up. If it makes any difference, it's whatever the default is.

Just got personal edition. How come it takes a lot longer to save a project than it did with the free version?

Bought it on steam, don't know how to roll back on that... if its even possible.

Same issue.   Particularly sucks because I just bought the personal license in anticipation of the long (American) holiday weekend. Was hoping to get a massive amount of development done. :(

Ahh, great idea! By putting my 'prototype' instance of the object I'm working with in a different layout, it is not getting involved in any of the stuff I'm doing with subsequent instances. I was not looking forward to making each event screen out the prototype's UID.

Say your layout has an object. In your event sheet, you destroy that object first thing. Then you create some new objects based on that object. What, if any will the consequences be, if any? Erratic behavior? Nothing? I know that the object will successfully be created and manipulated, but while I'm trying to work out bugs, I want to make sure I didn't create any by doing that. Also, I realize that the IIDs and UIDs may change due to this action, just as they would if I destroyed any other object.

LittleStain

There is more than one collision being checked for in the function.

Arima

I originally had been using overlap, but overlap doesn't pick the colliding objects the way that colliding does, which hoses the rest of the script. It's an 'infection' type of script, similar to the 'evil sprite' demo.

Thank you both. I may have found a solution, though: Making the function enable or disable a group, and within that group is my script. The function also initializes some variables necessary for the script, and checks to see if the group is still running or not, returning an error if it is. This should get close enough to being able to use the script as if it were a true function. I'm debugging it now.

I wrote a block that involves some collision based events and once I got it completely working correctly, I tried to turn it into a function. However, C2 balks when I try to drag any events into the function that are triggered by collision. This is a real show-stopper. Is there some way to alleviate this? I don't fully understand C2's objections. All I get by way of error messages is "There can only be one trigger per event branch, so some events could not be moved here."