
Originally Posted by
irishron
I'm not going to quote your full post for this but personally I'll take a "We're working on a patch" now as a positive step versus the dead silence I am used to receiving from them.
http://steamcommunity.com/app/4700/d...93781577390838
"That's a known issue (by the development team). They are working on a patch for that."
Yeah, it was at the Steam Community's main Medieval Discussion site, and they have an official discussion there. One guy, he must be just like you except paid and doing tech support, and he's getting hammered with tons of the exact same question, and trying to be patient with canned forum posts, and as it grew to eighteen pages of complaints, these posts got increasing terse! I actually felt sorry for him because he has his picture in the avatar and it's the face of abject failure.
If I hear any more, I'll keep posting. I check it a couple of times a day.(Punchy as I write this. Hope it makes sense.)
Edit: New Patch Update
http://steamcommunity.com/app/4700/d...93781622507729
"ETA on the patch is in the next couple of days. Just going through final QA and sign-off."
Posted three hours ago 2:58 Eastern
EDIT2: Folks, because of the huge number of posts I've been reading to assist the community with this, I'm going to add a PM I just sent to a concerned member. Please communicate with me mostly through this topic if you want more information. That way whatever questions I answer will end up answering the question of another. Or else I'll have to start sending canned responses in order to concentrate on the Steam update. I don't want to do that. PM response follows:
"I'd say that based upon the many hundreds of posts I've read about this (literally done to help the community), that to get the vanilla Steam version of M2TW and the Kingdom campaigns to work, a complete removal of the game PLUS editing of the registry with a program like IObit's Uninstaller or ccleaner to remove the Steam and M2TW entries, was necessary to get the game to operate. [Registry values tell Steam that it and M2TW were once on your system. Unless a real installation of the game was done, and registry values removed, then Steam makes errors when reloading the new Steam version of the combined M2TW + Kingdoms exes.]
Players who attempted to 1)download the Steam patch, 2)delete local content 3) reacquire a corrupted game integrity due to a failed integrity check, all failed to get a game that wasn't hopelessly buggy.
Now, even after getting the vanilla game and the basic campaigns reloaded, then there are all of the documented issues with the new Steam version of the combined M2TW + Kingdoms.
Then on top of this, people doing four different methods for getting a mod to work.
All of which is going to be a technical troubleshooting nightmare as thousands of people have been affected.
Wait, there's more. See that update topic. Steam is supposed to release a new patch; I'd guess in the next 48 hours. So this means a lot of people might have to go through ALL of that again. Then after doing so, then STILL troubleshoot and see what bugs are there and what new bugs might have been introduced."