Okay, so if a beta build messes up the configuration that an installed stable version is using, causing an issue or even data loss in the stable version, who's going to be responsible?
This is actually an end user question, not development I guess, indeed there is no need for portable on the PC that is being used for mosly development and not enjoyment where the integrity of the configs and saves matters.
Change of question then: Should the "betas" have that.
In the GUI there's:
Stable
Beta
Development
But I've never seen Beta, so I just called the daily development ones "beta", probably not correct.
And then there's the Development Dirty.
Development daily ones are on the mains site, I just clicked a big button, so those are shipped, those are the ones I mean should have portable.txt.
So it's confusing, they're development and shipped.
This is actually an end user question, not development I guess, indeed there is no need for portable on the PC that is being used for mosly development and not enjoyment where the integrity of the configs and saves matters.
Change of question then: Should the "betas" have that.
In the GUI there's:
Stable
Beta
Development
But I've never seen Beta, so I just called the daily development ones "beta", probably not correct.
And then there's the Development Dirty.
Development daily ones are on the mains site, I just clicked a big button, so those are shipped, those are the ones I mean should have portable.txt.
So it's confusing, they're development and shipped.