AAO25.com
Assist => Feedback & Suggestions => Topic started by: The Mentalist on Monday, April 20, 2015, 10:58:02 AM
-
Maybe it's a good idea to patch more often, but with smaller patches. I know it's nice to release a patch that fixes or adds a lot of things, but frequent updates show that the game is still improving. Also, it might improve the players satisfaction and encourage them to come up with suggestions to improve the game or to report more bugs.
At work, I work on a few projects. And I notice that the frequency of responses to feedback encourages the employees to keep on giving feedback and continue to support the project.
What does the rest think about this? And what do the DEV's think?
-
Considering all the hassle involved in each update, no.
-
Considering all the hassle involved in each update, no.
That's something I don't know offcourse. Thanks for the quick reply. :up:
-
Talking from experience, the users would throw a shit fit. Back when ELiZ first ported the SAI, there was a problem that only happened under certain conditions and it caused the game to crash. Over the course of a few days, many updates were put out to try and find the direction of the update. Users went berzerk, complaining about the amount of updates. They didn't really care that ELiZ was trying to fix a serious problem that caused the game to crash. Another problem was a lack of beta testers but we finally got enough people together to fix it.
Plus, as ELiZ was eluding to, each time there's an update, the game server usually lags behind the client for updates. This means that you open Assist, it updates but then half or more of the servers in the list are outdated and you can't join them. When the servers do finally update, they restart which kicks players out. ELiZ tries to do updates at a time with low player count but there's always somebody that gets hit.
-
Talking from experience, the users would throw a shit fit. Back when ELiZ first ported the SAI, there was a problem that only happened under certain conditions and it caused the game to crash. Over the course of a few days, many updates were put out to try and find the direction of the update. Users went berzerk, complaining about the amount of updates. They didn't really care that ELiZ was trying to fix a serious problem that caused the game to crash. Another problem was a lack of beta testers but we finally got enough people together to fix it.
Plus, as ELiZ was eluding to, each time there's an update, the game server usually lags behind the client for updates. This means that you open Assist, it updates but then half or more of the servers in the list are outdated and you can't join them. When the servers do finally update, they restart which kicks players out. ELiZ tries to do updates at a time with low player count but there's always somebody that gets hit.
Thanks for the background info.
-
Another note might be that are small updates that can be done (and sometimes are) without requiring a version update. When all of a sudden you get a new file being downloaded without a Assist update, this is what it is.
Those are, in their own way, an update/fix as well. Although they might also be something fun like Christmas maps or whatever.
However, most things can't be updated this way and even this causes file mismatched between client and server so minimizing the times it happens seems like a good idea.
-
Another note might be that are small updates that can be done (and sometimes are) without requiring a version update. When all of a sudden you get a new file being downloaded without a Assist update, this is what it is.
Those are, in their own way, an update/fix as well. Although they might also be something fun like Christmas maps or whatever.
However, most things can't be updated this way and even this causes file mismatched between client and server so minimizing the times it happens seems like a good idea.
Maybe post release-notes on the FrontPage with those updates?
-
Maybe post release-notes on the FrontPage with those updates?
Most of the time ELiZ does this.