Quote:
Originally Posted by Bridget
Advertising isn't the problem. Doing a month's worth of work then waiting a year to release the patch is the problem. Continuously breaking the game and then waiting a year or two to attempt to address the issue (and miss horribly when you get around to releasing the "fix") all the while letting people have bad experiences and/or come to bad conclusions about the modification is the problem.
|
My steamworks argument still applies to this I think. Steamworks would allow them to be able to make/revert changes to this mod on the fly so that no users are really negatively effected by it. It downloads a new version(or older version if some new feature goes screwy or servers won't stop crashing, etc) automatically so people don't gotta fuck with it.
And yes, the devs have come up with a pretty clever workaround that basically notifies users when their FF version is out of date as well as notifying users when a server is out of date, but I think it can be much more simple than that.
Out of the slew of ideas out there to improve FF's small stagnant community, I think Steamworks would not only bring in the most users but also retain more users than a lot of other game changes so we can start getting and keeping servers full.
Maybe the devs want to wait till a certain patch or new version before trying to do steamworks, because steamworks I think could give FF a big boost of new players and they want to make a good impression on newcomers, but waiting for features to be completed with the full knowledge that there are not that many developers to begin with, not that much time gets spent on it due to people having actual lives(Yes I know, shocking), so that makes me wonder why not just release Fortress Forever on steamworks once the 2.42 patch comes out because who knows how long it's going to take for 2.5 to be released?