Back from the 60s one heavily used convention was: [major-version] dot [minor-version] dot [revision]

The dots are separators not unlike those in an IP address, not decimal places (of which more then one of doesn't make much sense)
Within the same major-version number the API would remain backwards compatible. New commands may be added in, but old existing commands should both still exist and still function identically.
Within the same minor-version (rev changes) the API would remain identical and data/file formats would keep the same structure.

This would allow the operator to assume a revision update can be installed at will and not worry much about breaking compatibility for anything not listed in the change log.
One could also assume any additional applications made to work with the upgrading app should still function without modification, at least if you follow the API docs and don't do anything too hacky.

For minor-version updates you assumed API using additions and apps should still work, but anything hacky by-passing the API due to limitations needs revisited and possibly edited.
An example is one program that creates input to the program in question via documented API calls should be fine, but your second program that is run after output being generated that goes to parse internal data files you "shouldn't" be touching likely will break until updated to parse the new data file structure.

For major-version updates, all bets are off. Pretend it is a brand new app and all interaction with it by other system components may need redesigned or be obsoleted.

Of course version numbers are only conventions. Those conventions can be changed to mean something more fitting for your particular software.
Or simplified to "Start at 1.0 and keep adding one" if you can predict not many updates being needed or for very simple one-off script type things.
Dates have turned out to be quite convenient version numbers with the time making a good developer compile/commit identifier that already keeps revisions in the correct order.

The only real rule is "pick a convention and stay consistent for the life of that software, else the wrath of dragons upon your head be"

It makes me not a worthless freeloader in exactly the same way as you using an ad network doesn't make you a script kiddie hacker trying to infect millions of peoples computers with malware viruses and keyloggers deserving of imprisonment.

But if you insist on going there, allow me to remind you that my actions of not watching an ad are perfectly legal (and explicitly stated so in law), while your actions of infecting millions of computers is explicitly a federal criminal offense...

Unless the "creative work" is a computer game, of course.

I presume, from the (rather thin) description that your favorite websites are ones you go to more often, so they'll get more of those little chunks of money sent their way, no?

And it's naive to assume that I-don't-know-you, never-heard-of-you, and who-are-you aren't just as evil, or at least as enthusiastically corruptible, as the scumbags we keep getting stuck with.

What about saying you won't because, in the end, you're not likely to see any appreciable difference anyway?

When the game board is made of toxic waste, going out and buying a new set of plastic tokens doesn't fix the whole "getting deathly sick" thing.

Of course not. Those are approved stereotypes.

Back in the day before the day, the tipline was free, except for LD charges.

Other than that, I have pretty much the same history, I just couldn't pass up the "get off my lawn" moment. ;)

Apparently, Lewis is/was a feminist. In the rational universe, we call that "begging the question."

Man, I somehow always suspected Perl would be the death of us all, but I didn't quite have this in mind!

Just how much control is given to the players? Creating our own quest lines and NPCs, etc is kind of obviously intended, but just how far down the rabbit hole can we go?

Can players define their own weapon/armor stats? What about models?
Can players modify their rulesets to add, for example, new loot drop tables? How about new crafting professions?

And, actually a really important question: Is the digital release going to be available without Steam?

There have been plenty of those: legitimate, technical complaints about design flaws, suitability, and downright broken shit. Yet, somehow, that all seems to fall under the "Lul Change-hating luddite uniz nekbeard" response. So I really don't think we can take any proponents of systemd seriously, either.

Since Debian's not going to protect me from this svchost-cum-kitchen-sink abortion after all, looks like we're going to FreeBSD!