Updating Game?

[PyroclasticMayhem]

Is there any script that updates a game? I am planning to distribute a game made in RPG Maker VX Ace, I currently release several patches a day and it is a huge download.

 

[Uzuki]

http://rpgmakersource.com/freebies/systems/save-file-doctor/

 

[Kes]

Several patches a day?

Something is seriously wrong if you are having to do that.  At the very least, combine them into one patch a day - but is this for a completed game?

EDIT

Perhaps this needs to be a bit fuller.

If you are planning to release a game, then you should not be releasing it in a state that requires several patches a day.  You should do all the debugging before releasing it.  Once released your players will expect to have a clean game that does not require patches.

If those patches are new content/changes to the game, then I still think that players will be hacked off if they have to have several in a short space of time.

 

[PyroclasticMayhem]

Several patches a day?

Something is seriously wrong if you are having to do that.  At the very least, combine them into one patch a day - but is this for a completed game?

The game isn't complete. I push the patch out so the testers try out new part of the game.

 

[Kes]

I've tested a lot of games, and as a tester I would not be expecting to get several patches a day.  You cannot work fast enough for each patch to have a lot in it.  Unless it is to correct a game-breaking bug, I cannot see that you need to be releasing them at such a frequency. You should be hoping that your testers will be spending their time playing the game, not having to stop and do lots of downloads.

It is, of course, your game, and you must do it the way that is best for you.  But on the face of it, I do not think this is a very productive use of time for either you or your testers.  I would strongly recommend that you combine your patches.

 

[PyroclasticMayhem]

I've tested a lot of games, and as a tester I would not be expecting to get several patches a day.  You cannot work fast enough for each patch to have a lot in it.  Unless it is to correct a game-breaking bug, I cannot see that you need to be releasing them at such a frequency. You should be hoping that your testers will be spending their time playing the game, not having to stop and do lots of downloads.

It is, of course, your game, and you must do it the way that is best for you.  But on the face of it, I do not think this is a very productive use of time for either you or your testers.  I would strongly recommend that you combine your patches.

In the long run is it possible to release patches directly via the game? Or create a custom launcher to distribute patches?

 

[Uzuki]

But why go through that process? You're just going to give yourself, and your testers, a bunch of work that probably won't be worth it in the end. Instead of trying to make the game piece by piece, why not work up to 25% or 50% of the project before you show it off? You seem really intent on showing it off, which isn't a bad thing- we like enthusiasm here, but make sure you have a idea and a direction you want to go. That way when people actually get to it they can be on the same wavelength as you.

 

[Kes]

In the long run is it possible to release patches directly via the game? Or create a custom launcher to distribute patches?

I think the point we are trying to make is that you should not be needing to distribute patches.  

As Uzuki said, make a decent chunk of the game and then give it to your testers.  No tester can adequately test a game in micro portions.  A tester needs to be able to see how things flow together (or fail to do so), how it feels to work your way through a whole dungeon, not just half a map which is constantly being updated so all your previous testing was a waste of time because things have changed.

Also, unless your testers are working full time on this, all those micro patches will just sit there waiting to be downloaded possibly for hours, maybe for a day or two.  So why bother?  Also, if you are sending this out in small doses, it means that you yourself will not have been able to do proper play throughs.  No one should ever send a game out to others that they have not thoroughly tested for themselves.  If you have been doing your own necessary testing, then you should not be needing to do lots of patches for your testers.

 

[PyroclasticMayhem]

I think the point we are trying to make is that you should not be needing to distribute patches.  

As Uzuki said, make a decent chunk of the game and then give it to your testers.  No tester can adequately test a game in micro portions.  A tester needs to be able to see how things flow together (or fail to do so), how it feels to work your way through a whole dungeon, not just half a map which is constantly being updated so all your previous testing was a waste of time because things have changed.

Also, unless your testers are working full time on this, all those micro patches will just sit there waiting to be downloaded possibly for hours, maybe for a day or two.  So why bother?  Also, if you are sending this out in small doses, it means that you yourself will not have been able to do proper play throughs.  No one should ever send a game out to others that they have not thoroughly tested for themselves.  If you have been doing your own necessary testing, then you should not be needing to do lots of patches for your testers.

I decided to end the test program as the game was nearly finished at the end of yesterday. However, at launch will there be a way to notify or tell players about updates or news?