hedwards: If the developers don't understand the difference between alpha, beta and RC releases, then it's not exactly a good sign about how they view the customers.
A price change is understandable, but doing it _before_ the final release and of this size doesn't make me want to give them any money at all. It smacks of greed. Finish the release and then increase the price if you're going to.
amok: not sure what you mean. The game is finished now, it is leaving alpha, beta, early access, whatever-you-want-to-call-it, which is why the the price hike. The next update is version 1.0.
That's largely my point, if the developers don't know what alpha, beta and release candidates are, then that's not a good sign. A designation of .17 is typically alpha, it typically indicates that it's not feature complete or stable and as such an alpha release. A beta release will usually have a larger number like .9 and be feature complete, and largely stable, but not necessarily complete.
Regardless of how slavishly you stick to the convention, completely skipping a release candidate phase is a sign that the developer doesn't know what they're doing as the RC is the last chance to catch bugs before the 1.0 release. Often times the RC will wind up being the final release, but not always, sometimes you have to go through a couple.
This is how professionals and people asking for money in exchange for a product are supposed to deal with this. It communicates to the user what state the code is in and if they're skipping milestones, that's not a good sign.
This wasn't really a common problem before about 10 or 15 years ago. People knew what the convention was and they used it to communicate what state their code was to other programmers and random users. About that time, you got asinine things like Google's practice of having huge numbers of major version bumps without cause and various other deviant numbering practices that just served to confuse the users. Before that, they might refer to something by a year, but there would also be a version number that followed the convention in most cases because it's a really helpful way of keeping track of changes between versions and how closely you need to check when evaluating upgrades to newer versions.