Well, that's a nifty little bait and switch then. After two years of this, I guess we shouldn't be even remotely surprised anymore. Those bastards still reel me in every time, though. I'm such a sucker.
This happens EVERY time they don't put something on the PTR before making it live. /sigh
I am sure many Paladin will disagree with you about being overpowered with a 6 second CS ;). At least the Pally class has a temporary power increase to collect more honor.
Yah, they haven't learned that you have to test to a big group before release, but good they released something, even if Pallys are imbal.
That was a little joke ;-) - I actually raid with a paladin. The point is nothing at all has changed from the PTR. :-(((
This happens EVERY time they don't put something on the PTR before making it live. /sigh
I am sure many Paladin will disagree with you about being overpowered with a 6 second CS ;). At least the Pally class has a temporary power increase to collect more honor.
Yah, they haven't learned that you have to test to a big group before release, but good they released something, even if Pallys are imbal.
That was a little joke ;-) - I actually raid with a paladin. The point is nothing at all has changed from the PTR. :-(((
That sucks balls. I spent an hour or so trying to figure out my talents.
Yay, PTR version went live, I just feel Blizzard have some serious issues when it come to internal communication considering Blizzard have stated that we would get newer code than both the PTR and the current beta.
Originally Posted by Drysc
The talents released with the 2.0.1 patch will be more recent than those seen on the current PTRs; however as the beta talents are in a constant flux there will likely continue to be some discrepancy until the release of the expansion.
This happens EVERY time they don't put something on the PTR before making it live. /sigh
I am sure many Paladin will disagree with you about being overpowered with a 6 second CS ;). At least the Pally class has a temporary power increase to collect more honor.
Yah, they haven't learned that you have to test to a big group before release, but good they released something, even if Pallys are imbal.
The trouble is joe blow Paladin does not follow Beta patch notes etc. So in a week or when TBC is released they will be "bug fixed" according to blizzard but nerfed to 50,000 Crusader strike Paladins back to beta build. Trust me the will scream very loudly. The reverse side of this of course will be a month of reading wow general posts about Overpowered Paladins should be nerfed.
But as far as I can tell at least regards Paladins it is exactly Ptr build ,Bugs to holy guidance and all.
Yay, PTR version went live, I just feel Blizzard have some serious issues when it come to internal communication considering Blizzard have stated that we would get newer code than both the PTR and the current beta.
Originally Posted by Drysc
The talents released with the 2.0.1 patch will be more recent than those seen on the current PTRs; however as the beta talents are in a constant flux there will likely continue to be some discrepancy until the release of the expansion.
I know it shouldnt, but this kind of stuff pisses me off... Its like anything they say now is either incorrect or misinformed. I wish i could be wrong at my job all the time and it be no big deal.
Yay, PTR version went live, I just feel Blizzard have some serious issues when it come to internal communication considering Blizzard have stated that we would get newer code than both the PTR and the current beta.
Originally Posted by Drysc
The talents released with the 2.0.1 patch will be more recent than those seen on the current PTRs; however as the beta talents are in a constant flux there will likely continue to be some discrepancy until the release of the expansion.
I know it shouldnt, but this kind of stuff pisses me off... Its like anything they say now is either incorrect or misinformed. I wish i could be wrong at my job all the time and it be no big deal.
Well I suspect it isn't actually Drysc and Slouken being wrong, they're likely doing their job fine in relaying information to you - the fact that several of them said it seems to imply there was some internal source supplying the info. Who ever was wrong was probably some bunch of techs deep in the bowels of the beast who promised a later version build could be deployed and it turned out it couldn't - which again may be understandable given the scope of the deployment. Basically they need to tell their marketing/CM types "tell the players they'll get the patch when it's ready, and they'll get whatever is ready at the time, no promises". Instead, somewhere along the way someone decides more specific commitments need to be made.
I know it shouldnt, but this kind of stuff pisses me off... Its like anything they say now is either incorrect or misinformed. I wish i could be wrong at my job all the time and it be no big deal.
Sounds like politics is the perfect career path for you!
I was glad to get on and play around with 2.0.1 but it was pretty disappointing. Mostly because I ended up fighting premades with tier 2/3 gear on my Warlock, who is but a shadow of his former self in the gear curve :( Shadowfury was REALLY REALLY nice in Warsong though, I'll give it that, it's fantastic shutting down 7+ people in one spell. It honestly looks like something you'd genuinely die for on a WSG team. An AoE ranged stun on seperate DR from fear is just useful as all god.
Yay, PTR version went live, I just feel Blizzard have some serious issues when it come to internal communication considering Blizzard have stated that we would get newer code than both the PTR and the current beta.
Originally Posted by Drysc
The talents released with the 2.0.1 patch will be more recent than those seen on the current PTRs; however as the beta talents are in a constant flux there will likely continue to be some discrepancy until the release of the expansion.
I know it shouldnt, but this kind of stuff pisses me off... Its like anything they say now is either incorrect or misinformed. I wish i could be wrong at my job all the time and it be no big deal.
Well I suspect it isn't actually Drysc and Slouken being wrong, they're likely doing their job fine in relaying information to you - the fact that several of them said it seems to imply there was some internal source supplying the info. Who ever was wrong was probably some bunch of techs deep in the bowels of the beast who promised a later version build could be deployed and it turned out it couldn't - which again may be understandable given the scope of the deployment. Basically they need to tell their marketing/CM types "tell the players they'll get the patch when it's ready, and they'll get whatever is ready at the time, no promises". Instead, somewhere along the way someone decides more specific commitments need to be made.
If i were in charge of something like this, i would check, then recheck, and recheck again before I released info, just for the fact it doesnt look good on them as a whole when things like this happen.
Someone posted this Drysc quote from a few days back in the druid piss 'n moan thread on the WoW boards:
Correct, as commonly we work from a build candidate. I could easily tell you what's in the build candidate we're working with now, but the question is will that be the build candidate that is released? Maybe, maybe not, but by telling you what you may see I'm creating expectations for something that may change.
What would be gained by you knowing exactly what is in the current build candidate? You could plan out your talent spec beforehand or complain that x, y, or z is not included. What could be lost? The entire player base could be disappointed when the information we released doesn't turn out to be true. We take full blame for releasing information that ended up changing and creating expectations over something that didn't pan out. We're called dirty liars, etc. etc.
I'm sure you don't mind but we don't really appreciate even entertaining that outcome. We're more than content to have a big curtain over the patch with a shiny question mark. You don't NEED to know exactly what's in the patch to continue enjoying the game, and we would much rather not be called liars for trying to help by giving out information that really isn't necessary that we give out.
Teh Irony, she is a bitchy little mistress sometimes...poor Drysc. He got hung out to dry, and it shows:
I post the information I'm given, and unfortunately the information I gave doesn't seem to be what happened. At all times we attempt to give information that is solid as giving glimpses into an uncertain future sometimes turn out with different results, and that's what happened (to my dismay) here.
If you want to believe that I maliciously mislead you then there's not much I can do to change your mind. If you jumped to that conclusion I would be led to believe that I wouldn't be able to.
I'm in the process of trying to find out what the situation was and what ended up occurring. In any case the post I had made before wasn't mean to imply that the very newest talents on the beta realms the day of the patch release would be included, simply something newer than what was on the PTRs; however even that didn't seem to end up happening.
I'm still awaiting some further clarification on what occurred; however at this time I am making an educated guess that the information I related was based on a well intentioned mistake. The plan for how the patch was pulling data may have been changed, wasn't planned, or it was just a possibility that it could pull updated info and didn't. I'm not sure at this time.
I can't say I'm upset as much as disappointed that information I gave ended up to be false, regardless of the steps leading to the post. We try extremely hard to ensure that information and expectations are controlled to avoid this type of situation, and... it's just a disappointment.
From the information I have been able to glean, the current talents are what is going to remain in the game until the next patch, which is currently planned to be at the time of the release of the expansion.
Hooray! I'm 2Mb from finished with the download, so I guess it's time to log in and get used to playing with month-old talents for the next few weeks. "Disappointment" sums it up quite well...
One thing im very curious of, if we have this old redundant version of the PTR, are the 40 debuff slots which were promised (see http://blue.cardplace.com/newcache/en/89610960.htm) to be going in... actually in? or does it fall short like the majority of everything else blizzard has said.
Also there is the glancing blow reduction which I was never sure of (down to 24%)... would be nice to know if that made it in =/
Basically they need to tell their marketing/CM types "tell the players they'll get the patch when it's ready, and they'll get whatever is ready at the time, no promises". Instead, somewhere along the way someone decides more specific commitments need to be made.
Ironically, making vague statements and refusing to make specific commitments (even when they should be specific) is exactly their usual modus operandi.
This debacle will probably encourage even less communication from Blizzard to the players, which is a shame.
Basically they need to tell their marketing/CM types "tell the players they'll get the patch when it's ready, and they'll get whatever is ready at the time, no promises". Instead, somewhere along the way someone decides more specific commitments need to be made.
Ironically, making vague statements and refusing to make specific commitments (even when they should be specific) is exactly their usual modus operandi.
This debacle will probably encourage even less communication from Blizzard to the players, which is a shame.
While that is true the only thing worse than a lack of information is false information no matter how good the intentions behind it are.
I would prefer that they improved their communication instead of cutting down on how much information they will provide but I agree that the latter is a more probable event unfortunately.
Basically they need to tell their marketing/CM types "tell the players they'll get the patch when it's ready, and they'll get whatever is ready at the time, no promises".
Emphasis mine.
Wrong angle, I feel. The plain and simple truth is, this patch wasn't ready. They knew it wasn't ready, because there's newer, more balanced stuff already on Beta. They knew it wasn't ready, and they released it anyway. That is a very, very bad precedent (only matched by the release of the game itself, ironically).
Is every patch going to be released even when Blizzard knows it's not ready, now?
Before you start to drift, and your soul begins to scream.
I just wanted to tell you, that you're listening to a dream.
Wrong angle, I feel. The plain and simple truth is, this patch wasn't ready. They knew it wasn't ready, because there's newer, more balanced stuff already on Beta. They knew it wasn't ready, and they released it anyway. That is a very, very bad precedent (only matched by the release of the game itself, ironically).
Is every patch going to be released even when Blizzard knows it's not ready, now?
I suspect the issue was that due to the holiday season and end of year stuff (people have use or lose leave time), that next week there were not going to be enough support staff to release a patch.
So Blizzard very likely had a choice, release with potential bugs (but have support staff to fix issues) or release later (and not have the support staff to be able to fix the invitable patch bugs and having to wait until Jan 2 to get the staff back up to force, which would be lying about giving a Christmas present).
I believe they were stuck between bad choices, and to be honest I have picked the same choice, but it would have been nice to inform the player base about their plans.
Millions of words are written annually purporting to tell how to beat the races, whereas the best possible advice on the subject is found in the three monosyllables: 'Do not try.'
I can't wait for the first Nefarian kill that drops two Ten Storms chests.
Chance at DE into Void Sphere!
lol.
Our server was messed up so we ended up running some ZG with 12 to 15 people. Our MT was pissed at the 41 prot talent and seemed to have a lot harder time holding aggro. I was stuck healing with the default raid UI and discovered that the self-cast checkbox in the default UI sometimes makes heals go to you even if your target is in range. Burning a natures swiftness full HT on myself for no reason :/
Anyhow, One of the Shaman ZG blues dropped. I'd never seen them before. Mail healer boots I think. They DE'd into a level 61-70 small shard (forgot the name).
If that happens with ZG ilvl blues, it should happen with most Ten Storms / Judgement pieces that guilds don't want.
Basically they need to tell their marketing/CM types "tell the players they'll get the patch when it's ready, and they'll get whatever is ready at the time, no promises".
Emphasis mine.
Wrong angle, I feel. The plain and simple truth is, this patch wasn't ready. They knew it wasn't ready, because there's newer, more balanced stuff already on Beta. They knew it wasn't ready, and they released it anyway. That is a very, very bad precedent (only matched by the release of the game itself, ironically).
Is every patch going to be released even when Blizzard knows it's not ready, now?
I'd imagine that they had higher priority of getting the majority of the changes out ASAP, to lessen the pain later of other changes. It was such a huge change, that even an incomplete release was worth the risk in order to have it out in the wild before the holidays.
We'll probably get a 2.0.2 or 2.0.3 variant on Live before TBC hits, in 1 or 2 weeks. At least on that one most of our UI mods will work and it will be bugfixes and cleanup rather than major changes.
Though, It certainly does appear as though there were intended fixes that didn't make it in due to a mistake in deployment or a last minute bug in the updated version that could not go live.
12/05/06, 10:55 PM
