Start LT encounter: Get volcano icon (High Server Load). Fellbeast picks a person with an eye. 10 seconds later he flies up and drops a puddle. I love buggy Encounters. *Salute (Oh and AF+GE never went on when I used CB).
Printable View
Start LT encounter: Get volcano icon (High Server Load). Fellbeast picks a person with an eye. 10 seconds later he flies up and drops a puddle. I love buggy Encounters. *Salute (Oh and AF+GE never went on when I used CB).
really with all that can happen in BG I would really like to hear developer justification for respawning trash.
don't put us on artificial timers unless content is 100% working.
Oh! Can I play?
Trash respawns are another gate -- a dedication gate.
Since anyone can get enough radiance to get into BG in an afternoon, clearly the radiance gate isn't enough to keep people away from this content. So let's give the raid 2-3 attempts at each boss before all hour's worth of trash comes back and you get to do it all over again.
Is your raid group dedicated enough to slog through trash multiple times while learning an encounter/dealing with buggy pulls/crippling lag/linkdeath? LET'S FIND OUT!
(How'd I do? ;))
I don't mind the trash respawning so much, but it would be nice if the timer was a little longer. combined perhaps with spawning at the beginning of each zone or the prior boss room after retreating (though a run up the tower takes long enough that you have less time on dread and cooldowns, so I guess there's a silver lining to it :P)
Annoying, but in fairness, that has happened once out of a hundred or more Lt encounters. It seemed to be correlated with a very noticeable server hiccup and may have nothing directly to do with the encounter itself.
Stuff happens.
(*Awaits -rep tick from Roov*)
I've had this happen to my raid and there was no High server load icon. Started fight, put eye up, moved a few steps, breathed fire, moved a few more steps, and then flew up. We had barley put 40k damage on him and we had 2 hunters and 2 rks. Was the weirdest thing I've ever seen.
Great. I was (personally, I don't want to speak for my kin) very frustrated the other night. We had 1st lock, had a very smooth trash clear, and got in the best Twin HM attempts I've been on. I was up for another try, but the timer was up, so we went EM. It should be up to us how many cracks we get.
Would if I could. I can't wait til what has happened multiple times to other groups happens to you where the beast never dismounts and you can't restart the encounter without reclearing the trash. I will be thoroughly amused.
My time should not be wasted by buggy encounters (Don't forget the time the add walked through the gate and reset the raid on us). The "Group of experienced raiders" on the test server should catch this stuff. John Anthony gets +1 in my book, wherever he is.
Here's his swan-song thread warning everyone about BG. Let's see how high we can retroactively boost j_a's forum rep.
Well it's my opinion that terribad loot is also a key issue of raiding. It removes a major incentive (for many people, the primary incentive) to participate. In the long run and across servers, it reduces foot traffic into the raid, which I'm certain is a primary metric used by Turbine to evaluate and prioritize resource allocation for future raid content.
None of this should be taken in any way to insinuate that it's more important than fixing bugs/respawns/class balance/resists etc. It's just another reason why it's very easy to dislike BG. Didn't mean to derail your topic.
One conspiracy theory I came up with along these lines was that BG was intentionally implemented to reduce foot traffic in to raids -- forcing data mining to show reduced numbers in the raiding community so that resources wouldn't have to be allocated toward raid clusters and they can take that data and put the resources toward skirmishes.
Now that said -- I'm not at all convinced this was deliberate, but the more the raid gets debunked I"m starting to think I'm not so sure it wasn't deliberate.
Bugs are annoying. You deal with them and move on - that's what I do. I file my bug report and move forward. Providing it's not a game breaking bug (door bug) I don't worry about it too much. It serves no purpose.
I still feel respawns serve their purpose. I don't necessarily say "keep them forever!'. But they accomplish their purpose. Personally speaking, the respawn has never affected me too much. As I've said in other threads, if you've wiped on a boss 4 or 5 times (more than enough attempts in a 2 hour window) then you really need to re-think what you're doing. Which, for myself at least, means time away from the raid re-thinking things.
My experience is all I can comment on. That's why we pool opinions. No one opinion is more right or wrong than another.
edit: Since we're talking about opinions, I'll throw another one out there. I do think respawn makes you a better raider. Everyone knows their on the clock. There will be no playing around - because if you do, you might not get any loot. It's a motivation that doesn't exist if respawn isn't on the clock, unless your group has a hard cut off time.
So if respawn doesn't bother you, because it never affects you, but it does bother a large number of other people, because it (a) directly affects them, and/or (b) discourages participation/reduces foot traffic, wouldn't it make sense to change it to extract the maximum amount of utility?
Unless you think removing respawns will make your raid group perform worse due to a newfound ability to slack off? I mean, you're always free to run a stopwatch and /disband the raid after 3 hours...