There is no limit imposed by Construct.

I have been having some project export issues (project file size is about 1.2gb), when I try to export my project at the moment via nw.js desktop build i get a "out of memory" error at the end of the project export (my computer has 32gb of ram) and if i try to export an android cordova project I get a "Build Failed" with no errors. Would you by any chance know what may be causing this? I assumed it was file size as it was working fine before the project was over 1gb

Hello,

I just wanted to know if there is an actual file size limit for Construct 3 as I don't really see any mention of it at all. I have been having some troubles exporting my project and am thinking it may be because of the file size.

This is for a fairly large mobile game project using Construct 3 as the engine and PlayFab for the backend, please message for additional details.

I just also tested this in a new project and the same issue happens. Can't bring the depth of an array past 100 on the array editor

Don't break up the event. Check for touch then as a sub-event check your condition and use Else for the alternative.

Thanks, that worked!

Essentially I'm loading in data into an array and some data will be skipped, causing there to be some rows with 0's as values and I'm trying to get rid of those. Everything seems to be working fine aside from the array sorting function.

The code im using

The Array's data after loaded into array

I Pop the data from the Y axis to remove the categories (which i add back at the end)

I then sort by Y axis which -almost- works in that the 0's are properly pushed to the top however the values in column 2 and 3 are now mixed up.

From the array documentation page it says that its suppose to preserve the contents of the column but it doesn't seem to be doing that here?

You need to remove "Else" from event 17. Leave the condition part empty.

Also, your project is crashing because While loop becomes infinite. If there is even a small chance to create an infinite loop, you should always include an "safeguard" exit condition to it! So add condition "loopindex<1000" to the while loop. It will stop the loop after 1000 iterations.

Ahh interesting, I'm assuming the issue was caused then because the function under else only will be triggered if the last function is false?

Thanks for the help!

Your events work correctly. However, the Adventurer is only destroyed at the end of the tick. So even if you destroy it in event 59, for all remaining events it will still exist. So in event 78 enemies re-acquire it as a target.

You can add another condition to event 78 "Adventurer health>0" to fix this. Also, it will be a good idea to disable adventurer's collisions when destroying, it may prevent other similar issues.

By the way, you don't need to use "System pick by evaluate" and "For each" in this case. You can simplify your events like this:

Thanks so much for the help! That seems to have been the cause of the issue, Ill be sure to be more careful with events conflicting with each other.

And thanks for showing me how to simplify those events, I think with that I can actually simplify a lot of the events I've created.