Adventure Game Studio

AGS Development => Editor Development => Topic started by: Crimson Wizard on Mon 13/06/2016 15:45:11

Title: Templates distribution process
Post by: Crimson Wizard on Mon 13/06/2016 15:45:11
So, there is this problem which I need an advice (and possibly help too) with.

We ship number of game templates along with AGS Editor. When we upgrade Editor, some templates may refuse to compile and need certain fixes (like switching backward compatibility option, or renaming script functions).

How do I organize this process?
Should I report this in the template thread and wait until template maintainer fixes it? What if they never do that - should I remove template from the package to let users download templates on their own if they want to go with the trouble fixing it themselves?

The worst thing is that I am already so overwhelmed with various tasks, that I keep forgetting things. The templates are not part of the Editor nor engine, they are contributions by other people, so I am logically not the one who should be caring about these. While I am trying to ensure that there is always a compatibility switch, and sometimes even make Editor turn this switch automatically if it loads an old game project/template, that does not always work (for example, currently we are lacking a proper script API version selector, so there is no way to fine-tune the version of script functions game is using).
Title: Re: Templates distribution process
Post by: Billbis on Mon 13/06/2016 16:09:35
Here my humble opinions:



Title: Re: Templates distribution process
Post by: Crimson Wizard on Wed 15/06/2016 13:30:00
One thing that we should certainly do is not accept any new templates or even template version upgrade unless at least several users confirmed that it worked for their game...