Skip to main content

Browse GamesGame JamsUpload GameDeveloper LogsCommunity
Indie game storeFree gamesFun gamesHorror games
Game developmentAssetsComics
SalesBundles
Jobs
TagsGame Engines
bojjenclon126 days ago

I have a question and a suggestion. :)

Question:

Meaning v1 projects won’t work on v2, and vice versa.

Will there be an import process to get projects into the v2 state, or will we have to move all our data over manually?

Suggestion:

Working on multiple machines has always been a bit of a pain point, if there was some sort of “portable project” option that allowed us to - for instance - keep the DB data in a Git repo that would be spectacular. Right now I just export the DB as a backup and reimport the data when needed, buts its pretty tedious and sometimes error prone.

Reply
baj123 days ago

Hello bojjenclon,

For the import process, so far most of the data works. The main idea on not “supporting” V1 is not to worry about backwards compatibility when adding more features. But I guess we will need some sort of “migration plan”. Unfortunately life got in the way so V2 is taking some time…

About the portable project, this is something I’ve been thinking for some time. The main problem with this is that the current database lives in the browser and we would have to “dump” it to have it in a file. I have A few ideas but not quite solid as a solution. Maybe… the db gets ‘dumped’ to a file by default on project/app close. And a special flag on each project like “auto import from dump” would do this reimport thing automatically on load. Git operations like pull/push/merge would be responsabily of the user outside of the scope of the app . This would make a project also work on a file share or Dropbox-like app. Thanks for the feedback!

Reply
AboutFAQBlogContact us
Copyright © 2024 itch corp · Directory · Terms · Privacy · Cookies