GDEVELOP version for each project

Hi guys, after the last update, in gdevelop, that some new features, break up the old logic of my project.

I was thinking about if could be possible, have a version of the engine for each project.

Inside the gdevelop, like when you start a new project, you link the project to a stable version of gdevelop. And the possibility of upgrade the version in case you want test one of the new features.

I know we r free to download the older versions in GitHub. And we can make the install of many versions of gdevelop on our computer. By the client side.

My wish is something more automatic, and organize inside the gdevelop area.

That’s help a lot people that already have a publish game, or a medium, big project.

1 Like

I doubt any1 would be able to keep track what version have which features and break what so that option would not make sense in that case

But imagine i did not update my gdevelop i do not have latest version
A notification am gonna to run this project on out of date version could help

But then again no one would know with what version he would get what

And even worse where you would get info of what will get broken between versions?

Or am i missing some use case?

I’m just suggesting, a way to avoid crash the logic of a already made game.

Is the same in that unity deal with their engine versions.

Have no problem you run a project made in a old version, run intro the same version as Was made.

The problem that break the game, is you take a game in version 1.1(for example) and open the same project in a version 3.5.

My suggestion, is in a way the project save a info of what is the version the project was made.

And don’t let you open the project instantly in the new version, instead show you the info that, maybe something cin the events can be wrong, bc the version that project was made is out dated.

(Sorry if my English isn’t in the best form)

I’m try to make more easy to understand that I can In the moment.

The idea is have something same as unity deal with versions of engine. And projects.

That is a good way to help the both type, people that prototype, in the lasted version.

And people that already have a projets of 1 or 2 years.

Info with which project was created would be useful

But then what if i started on version 1.04
Then i updated to 1.05

Then i went on vacation and meanwhile gdevelop went from 1.05 to 1.08
So there were 3 version by that time

I came back from vacation i am at 1.08 and my project is broke
Only info i have right now is that project started at 1.04 and not that it was also working at 1.05 where it could MAYBE also work on 1.06 and 1.07

You see the problem here?

And just to be clear
I am not against your idea i think its pretty good
I am just looking for better implementation of it

Cause right now i would have info on which version i created it which does not need to be version on which i added some features
And actually going backwards could break it also

BTW i am not 100% sure but i think only thing i saw that breaks projects are outdated extension

But maybe i am wrong

Anyway again i think your idea is good but could use some brainstorm to be polished

i get it, so instead of the creation version maybe could be the last version used.

in a case of gdevelop dont make the upgrade of the version automatic.

like you are you create the project in 1.05 you and go to 1.08 with no problem in a range of 1 year. going version to version, adding more content to the game with no problem.

but in the 1.09 the main core gameplay breaks, can just back to the last stable working version of the game.

i totally agree if more people get involve we can brainstorm to get a better version of this idea.

in the case of outdated extensions.

i don’t know since when you work with gdevelop, but i use to work with the “old” way of the events where you need to call the variable in the action like

"GlobalVariable(“variable”).

and my pc broke, so i spend like 8 months out saving cash for a new.

and when i back the new system you can already call only the variable like:

“variable”

and the system reconize if is global scene, etc.

is not a problem i think this upgrade was realy awesome, but i was struggling to find the version thats fits with the old project.

so i choose to re make all the project from scratch instead to passing tape on an improvised project.

right now i work like with 2 versions of gdevelop in my pc one i always upgrade and other i only use in a project with more 2 guys, of racing game.

i choose that bc i saw alot of mainstream people that make medium games in unreal/ unity dont upgrading the version the engine.

like arena breakout infinity that unreal 5 was in 5.4 ,and the main game is in the 5.2 ( is visible for the way that lumens works).

My understanding is that GDevelop explicitly does not have any long term support versions, at all. Meaning that the only supported version of the engine is the most recently released one.

For what you’re looking for, you would have to remain on the version released that you want with your project, and disable updates.

As far as I can find on other engines like Construct and Godot, this is true there as well.

One simple solution would be GDevelop create in the FIRST line of evenment of the first scene, a remark that user can not use and delete. In this remark, GD would put a concatenation of all versions where the game has been run.

Game can run perfectly fine even if some part of it don’t work
For example your game can run perfectly fine but on new version yarn will not work at all
And so by your idea this version will be added to list as working version

Yes but i don’t know if it’s possible to te GD team to put this possibility in the editor.

My idea is before all, to give the GD’s user to see by example, the five or ten last version (if any) of GD used for the project’s user.