jamyskis: Funny, because I saw those initial developer announcements, and there was never any talk about the expansion being free to existing users. What the initial announcement did say was that the entire game would get the engine update, and existing owners of the base game/Pirates of the Flying Fortress would get that engine update. There was never any talk about enhanced textures or existing users getting Call of the Tenebrae for free.
Well, then, you did not see the announcement that I did. I assure you I saw it and "Cot will be free for everyone who already owns the game" is pretty much a direct quote of what I saw that you didn't see.
In what I saw, the "engine upgrade" was to be rolled into CoT--there was only one download mentioned.
I get that the "in thing" right now is to bash Reailty Pump and TopWare for all their worth because of the microtransactions debacle, but if you're going to spread shit, at least stick to the truth, yeah?
It's not the "in thing" at all--I'm just disappointed they didn't do what they originally promised. Please don't think for a moment that simply because you missed it that you know what you're talking about...;) I'll accept that you didn't see it--fine. I won't accept your insistence that because you didn't see it then neither did I. That's flatly untrue. Guess we will have to agree to disagree, then. I *like* this game--which is why I bought it. I'm not trashing it at all, just stating my personal opinion based on what I saw.
Now I get that trashing people with idiotic comments simply because you missed something they didn't is the in thing, but if you're going to spread shit, at least stick to the truth, yeah?
FlynnArrowstarr: Didn't catch the notice until after the 1.3.7 (2.0) had akreadt downloaded. Thankfully, it didn't break compatibility with Worlds Merged. Rollback looks to be an option if needed in Galaxy. I do still have my original installer from 2015, heh.
Flynn
Honestly, I can't tell if it's patched to 2.0 or not. And I've been alternating between the two to try to see. It *seems* as if the Steam version, which ID's itself as "2.0" on the initial game settings screen is
rendering differently than the GOG version, at the moment, which ID's itself as the same old 1.3.7 version even after the installation of the 1.3.7_(2.0)_(13261).exe GOG version.
What I really don't understand is why is this issue so muddled here at GOG--it's very straightforward in the Steam version. Is it the 2.0 version or is it not? Seems like a very easy-to-answer question.