How to load c3 file to old stable release?

Not favoritedFavorited Favorited 0 favourites
  • 5 posts
From the Asset Store
[C2] [C3] Support C3 build service and Android 14
  • Hi, I'm not sure when it happened but one of the newer releases broke my project. The game corrupts on load when I change aspects of the original main layout. It didn't do that before, as I've been working on this project for over 2 years without issue. Now though, if I open a tool tip box (sprite) I have to destroy it before the game saves which is cumbersome. If I don't, on load, the game breaks. The box appears empty without text and other layers within the menu are broken. I've tried adding the no save behavior but it didn't help.

    So I'm wondering if its possible to load and edit my game with an older release. How would I go about doing that? When I try it says, "This project can not be opened since it was saved in a newer version of Construct".

    Tagged:

  • Yes, it's possible. Unpack C3P file to a folder, or save it as folder project.

    Then edit project.c3proj file with Notepad. Change the "savedWithRelease" value. For example, "savedWithRelease":42402 means r424.2

  • Try Construct 3

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

    Try Now Construct 3 users don't see these ads
  • How safe is this method?

    I found an export bug that I figured out first appeared in v425 beta. I’ve reported it, but not sure when/if it’ll be fixed.

    Fortunately, I don’t use betas, so I have a good project from just a few days ago made in 424.2.

    Since then, I’ve made quite a few changes but have saved the project file as a new version 11 times.

    I’ve used the above method using my very latest save (using 432.2) by changing savedWithRelease from 43202 to 42402

    Everything, including the export, appears to work when using the v424.2 editor but I’m afraid something might break further down the line!

    If there is any risk with this method, then instead, I’ll need to run a diff on those 11 versions and manually make the changes – not out of the question, but still several hours’ work.

    Either way, I’ll then stick with 424.2 at least until either the bug's fixed or I’ve published a new version of my game.

  • Going back one version should probably be okay. But sometimes Scirra makes changes to the file structure and then downgrading your project may break something.

    Since your project loads and runs fine in 424, don't worry about it.

  • Yes, it's possible. Unpack C3P file to a folder, or save it as folder project.

    Then edit project.c3proj file with Notepad. Change the "savedWithRelease" value. For example, "savedWithRelease":42402 means r424.2

    Thank you!

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