#0 - Sept. 20, 2010, 6:08 p.m.
You have entered too many instances recently
#41 - Sept. 20, 2010, 6:32 p.m.
Q u o t e:
I would like to entertain the pathetic attempts to dull my character by ridiculous remarks like claiming "I don't understand what it's intention is."
I fully understand. It was a great implementation five years ago.
The game is completely different. How many designer thinktanks from the previous team remain? The direction is different. Instance farming doesn't even happen anymore.
Furthermore, even if it did, it still shouldn't lock you out of raid instances. Much less Wrath of the Lich King raid instances, which have their own designations from Vanilla altogether (10/25/10h/25h).
Face it. It's an old, tireless mechanism and it has no place in the game anymore.
You're thinking about this from the perspective of an actual player, such as yourself, attempting to play the game. Not someone who has the intent to be employed by doing repetitive actions, such as instance farming.
It still has a place in the game. Also the little jab there attempting to discredit the designers is unwarranted. Just because someone is unable to see past the bridge of their nose, doesn't mean there aren't plenty of reasons within logical reach.
#64 - Sept. 20, 2010, 6:44 p.m.
Q u o t e:
Warranted. Do you, as a player or in the viewpoint of a designer, feel that it makes any sense that it should lock a player out of a raid that you can't do more than once due to instance ID saving?
It doesn't really lock them out it's just a timer, but that's splitting hairs I suppose, anyway, I'm not a designer but yes it still has a use because there is still plenty that you can do before being saved.
It stops a lot of issues that stem from people turning over instances, either legitimately or otherwise, and it's a pretty short timer - - something the vast majority of players will never even see.
#70 - Sept. 20, 2010, 6:46 p.m.
Q u o t e:
Yes, why is it based on your account, and not characters? I was running all of my 80s through Coren Direbrew, and when I got to my 7th, i did it once, I got the remote control, then couldn't use it because of "too many instanes".
Because you could just flounder back and forth to different characters to avoid the timer?
#84 - Sept. 20, 2010, 6:50 p.m.
Q u o t e:
No offense Bashiok, but that is an uninformative answer. You could have at least said something like "for the same reason as 5-mans."
Or are you actually trying to get a reason out of him? If so, good luck.
(Ideally) It's a conversation, I was hoping to find out what they thought so we could discuss it instead of just shouting reasons back and forth. :)
#95 - Sept. 20, 2010, 6:56 p.m.
Q u o t e:
I feel like you are just insulting us now.
Why? Feeling insulted? No I'm not insulting you. Unless you feel insulted, then, well I don't know what to say.
Q u o t e:
Why don't you make it lock you out of the instance you are farming then? Why does it need to affect every instance. You can farm SM but you can't so easily go to BRD and start farming that. Considering its a long way away from SM.
Because it would be a poor solution to base the entire system off of one example where we think it probably takes a long time to get from that instance to another. One solution to rule them.
Q u o t e:
So really you are hurting a lot of people by this, I see it all the time in pug raids. You just don't see all those people complaining on the forums.
I disagree it hurts a lot of people. I strongly disagree this hurts a lot of people. I would argue that in any given day very few people see this message that are playing legitimately.
#151 - Sept. 20, 2010, 8:02 p.m.
Q u o t e:
Instance lockouts are a VERY real concern ever since the content got to be so easy that it can be speed-cleared in a time-frame that is comparable to those who were instance farming for mats, hacks, ect in Vanilla. Yet the parameters of this lockout have not changed to accommodate this. Then, on top of that it is tied per character and to the raids as well making it a VERY draconian system. You WILL see this message if you have multiple characters (I try to maintain 4-5 80s and I know I'm not in the minority here), do your daily heroic, do the holiday event and then try to jump into a quick raid like, say, VoA or whatnot. Want to help out a lowbie friend with an instance run? Forget it, lockout punishes you for the ENTIRE ACCOUNT!
Correct. The entire account. That's intentional and necessary or else the system would be easily circumvented by just floundering characters.
Q u o t e:
Change the parameters. I know you have the equipment (what have you been doing all this time retrofitting the servers, ect) The game has been updated to reflect the present reality of the playerbase. This is one thing that has not caught up yet.
I apologize for being so upset but Bashiok's tone hit a nerve here.
We like the mechanic as it is and have no intent to change the amount or time of impact. If it looks like we do need to change it we'll let you know.
#158 - Sept. 20, 2010, 8:13 p.m.
Q u o t e:
EDIT: I have a better question for you, actually.
Is this doing more good than harm?
My assumption would be yes, but that's sort of impossible to prove as there's no metric available to me for how long people are made to wait before clearing trash in a raid while waiting for someone on a 'too many instances' timer. My assumption is yes because even though it may be an inconvenience at times to a few groups, it does infinitely more good by protecting the service as a whole. Again, an assumption, but I think an informed one nonetheless.
Q u o t e:
I find it acceptable that this restriction applies to all characters, and that it exists in the first place. However, when you go from a 5-man (which is now just a LFG click away and ignores this mechanic I believe) to a raid, you're holding up 9/24 other people possibly. If you're a MT or something along those lines, we all suffer because we have to wait for your timer to finish.
I do find this to be the one legitimate claim, and that I don't personally see any real drawback by having a separate 'too many instances' timer between raids and dungeons. That's just my personal view without a whole lot of information or knowledge on the issue. But I believe the rule intentionally doesn't differentiate as these are instances being kicked up by the same servers. There's no dungeon server or raid server, it's the same deal and so differentiating them would (theoretically) double the impact on the same piece of hardware.
#160 - Sept. 20, 2010, 8:14 p.m.
Q u o t e:
You keep using that word. I do not think it means what you think it means.
SHHHH! I'm trying to get it to catch on.
#162 - Sept. 20, 2010, 8:15 p.m.
Q u o t e:
Bashiok - You are by far the least helpful, most disrespectful CM since Tseric.
You will not last.
Good day.
What about Drysc? That guy was a jerk too.
#177 - Sept. 20, 2010, 8:32 p.m.
#221 - Sept. 20, 2010, 10:41 p.m.