Understanding the constant "cannot find object type named" error when attempting to open a project.

Not favoritedFavorited Favorited 1 favourites
  • 2 posts
From the Asset Store
Hand-painted tiles, objects, animated objects, and background to build a colorful Mayan civilization environment.
  • The "main.js:29 [Project] Exception opening: Error: cannot find object type named '[object name]'" error is so constant that I want to understand it once and for all.

    (I could be wrong, but I suspect online backup solutions are to blame for this, such as pCloud and Icedrive, despite that they're supposed to help, not hinder, because they so often create "(conflicted)" (pCloud) or "[conflicted]" (Icedrive) versions of Construct 3 files. Why do they need to do this, when my local files are garanteed to always be the ones I want, not some outdated online backup's? And then I'm working on a project or event sheet that isn't even the latest one, and I don't realize it til later, and need to consolidate the two. I hate online backup services, but I can't risk not using them either.)

    What's the fastest and easiest way to fix "Cannot find object type named [object name]" errors? I see the object exists in both my project.c3proj file, and in the objects folder where it belongs, and that the name is the same in both. Why can it claim to not find the object, when it's clearly there in the right objects folder? Because of online backup services, there are two versions of the project.c3proj file, but I assume C3 uses the one that doesn't say "[conflicted]", which is the one that I confirmed has the object name in it.

    EDIT: For anyone else who gets this error, one thing I did just now, that at least opened the project (but I'm unsure about if I'm missing anything--everything looks okay so far, as being my most recent work), is that in my C3 project folder, I made a folder called "(conflicted file backups)" and simply dragged in the versions of the files that Icedrive created "[conflicted]" versions of, in this case these 3...

    objecttypes.uistate [conflicted]

    project [conflicted]

    project.uistate [conflicted]

    ...just in case I ever need them again, and then opening the project worked. Which suggests, as strange as this seems to me, that C3 was actually opening the project based on the files named [conflicted] instead of the ones not named that! If such a thing is possible? But all I know is, when I separated the files with [conflicted] in their names, it opened, and, at least from what I can see, seems all well.

  • Try Construct 3

    Develop games in your browser. Powerful, performant & highly capable.

    Try Now Construct 3 users don't see these ads
  • That error basically means the project has been corrupted. The solution is to stop doing whatever is corrupting the project.

    If you have some cloud storage system that keeps coming up with file conflicts, I'd guess that's likely to be the cause. If you're doing something like saving a folder project directly to a synced folder, maybe try saving it to a regular local folder, and setting up backups to copy to the synced folder (possibly using Construct's built-in backup options).

Jump to:
Active Users
There are 0 visitors browsing this topic (0 users and 0 guests)