1.11 Small Request and some bugs.

[Esmo]

Originally Posted by Gryzx

I think some instances (BWL?) are even saving you on trash mobs, which seems a little excessive.

It seems even more random than that. All those saves certainly can't be helping the latency either.

[Keltan]

Originally Posted by Gryzx

I think some instances (BWL?) are even saving you on trash mobs, which seems a little excessive.

We were getting "You are now saved to this instance" everytime something died in BWL last night. Didn't matter if it was a boss, or trash like technician packs. Anytime something died we'd get spammed again.

[ZyrKx]

Player dies. You are now saved to this instance.
Pet dies. You are now saved to this instance.
Warlock sacrifices pet. You are now saved to this instance.

Fun spam :/

[Furism]

We had the same thing in BWL yesterday too. - on player death, but also on boss and trash mob death. But we didn't experience this in MC, we were saved only after a boss died.

[Talzar]

Copy and paste this into WoW: This will stop your raid window from popping up and from you getting the "you are now saved to this instance" spam each time trash is killed:

/script i=1 frame=getglobal("ChatFrame"..i) while frame do frame:UnregisterEvent("UPDATE_INSTANCE_INFO") i=i+1 frame=getglobal("ChatFrame"..i) end

[DiscW]

Originally Posted by Asmadai

If you are referring to this as a bug, it's not. You now get 'saved to the instance' after every boss. This was implemented to prevent people from cascading instances.

Shit I was saved to the instance a good 10 times just during vael.

[Salizar]

Originally Posted by Maxxius

I dunno, they really need to think some of their patch changes a little more. By far the worse one was the world-wide LFG channel. Didn't they realize that the kids would just use it as a chat channel? So now when I am lfg I have to use the general chat channel, since I have the lfg one off due to spam.

Also who came up with these retarded symbols that group leaders can mark over people's heads? So now in PUGs I have to endure the kiddies plopping these symbols which makes the game look like someone spilled lucky charms on the monitor.

The Lucky Charms symbols have one GREAT purpose,
Garr add targeting...
The number of symbols just happens to match up perfectly with the number of adds garr has.
Sure we were using garrtarget, and manually setting assist with ct raid, but this shaved about 10 minutes from this fight, just from setup...
Thumbs up...

[Ukerric]

Originally Posted by Salizar

The number of symbols just happens to match up perfectly with the number of adds garr has.

Yeah. Not only did we shave 10mn assigning adds, but we can check if everybody has its correct target, and they can lose it without problem for whatever reason.

Plus the death's head symbol seems tailor made for "this is our first target, everyone on that one".

[Zinke]

The symbol system is really quite good. It basically eliminates the need for an MA on most fights. It just takes a little getting used to. Setup a standard kill order for symbols (skull, circle, triangle, x etc..) that you use for every pull. The MA can just set the symbols up before the pull, no it doesn't add setup time unless your in a zone that is super easy for your guild and your chain pulling. Even then, it hardly does. I tried setting symbols on mobs in ZG in between pulls, and I could always get them symboled before we pulled one. We weren't using them for the actual kill order, but it wasn't hard to get them up in a few seconds.

Some might say 'bah, that's pussy mode, your MA's must suck'. Whatever. It just avoids the errors of MAs targeting one mob accidentally, having people assist right then, then he switches and they all don't notice for a few seconds. Or, if the MA actually dies, there's no in battle confusion over who to assist. Set the symbols and forget.

Plus, there's been many times where the /assist command has gotten bugged and assist macros have not worked properly.

Of course, there's still many fights where you need an MA, Death Talon Overseers and Anubisiths for example, as you don't know the kill order at first or where you have to switch targets a lot.

I love the symbols, and I've been seeing a lot of reluctance from people to using them, which I just don't understand. They all love using hunter's mark, but having a bunch of different looking symbols that do the same thing but better, is stupid? wtf..

[Northerner]

We had a running joke going in BWL last night. Vent was full of "Careful guys, if we wipe I don't know for sure that we've been saved to the instance yet!" and so on ad nauseum. It was strange though, we'd get a "you have been saved to this instance" in spammy bursts and not just during packs or the suppression room or something. It seemed like whenever something died, was looted or even when a hunter FDed it wanted to trigger the script.


The symbols exist (as far as I can tell) so the manginas can fight over who gets to be the shiny moon. The red X is a great way of marking the last person to do something stupid as well. Annoyingly, the alliance seems to also like to use them to mark me out as: "squishy mage that needs to die quickly or he'll piss us off". I walk into a BG and get the blue diamond of death on first contact.

[Presarc]

In the fashion of my jboots are feeling slower....

lol

[Zinke]

Originally Posted by Northerner

The symbols exist (as far as I can tell) so the manginas can fight over who gets to be the shiny moon. The red X is a great way of marking the last person to do something stupid as well. Annoyingly, the alliance seems to also like to use them to mark me out as: "squishy mage that needs to die quickly or he'll piss us off". I walk into a BG and get the blue diamond of death on first contact.

Whoa whoa.. you can use these in BGs? I mean.. that makes sense to an extent, but I hadn't thought of it really. That's potentially overpowering. I assume it doesn't work on a character that is stealthed? Common sense would dictate no, but that might have slipped by them. Even then, it still sucks because the symbols are viewable through obstacles. Now everyone knows exactly where some other player is, or is heading, in a BG. In small scale BGs like WSG and AB that really changes a lot of tactics.
It makes NE defenders even better. Alliance will know where half of the horde team is at all times. Horde will only know where the non-rogue and non-NE defenders are.

[ValkyrieIsAboutToDie]

Doing a complete 180 degree turn from the "You are now saved..." bullshit, my guild popped that new whacked Skeram 2.0 tonight, but only 5-6 people were actually fucking saved to the instance. The result? 3/4s of the raid staring at a fresh instance after a wipe and run. We tried everything to get the proper instance loaded up, from disbanding the raid and making one of the people with the instance properly saved raid leader to having the entire raid log for an hour. Nothing. Nada. I sure as fuck wasn't going to kill Skeram again and get called for cascading. Waste of goddamn time. Bug Trio is apparently fucked also.

It's almost like there's a huge neon sign right above the gate to AQ40 that says

Just Fucking Go to Naxxramas Already. This Place is AIDS.


P.S.

Blizz knows about the no-save bullshit. GMs give nothing but an automated respone. Anyone else get dicked over by this shit recently?

[Zehn - Vhex]

Originally Posted by Zinke

Stuff about symbols

BUT IT RUINS THE IMMERSIVE FEEL! WoW sucks because I can't be gladelf the wizard who defends the animal people! I can't wait for VG so I can roleplay a fiesty bar wench who craves halfling cock without having WoW's convenient gameplay get in the way. 8(

[Digo]

Originally Posted by ValkyrieIsAboutToDie

Doing a complete 180 degree turn from the "You are now saved..." bullshit, my guild popped that new whacked Skeram 2.0 tonight, but only 5-6 people were actually fucking saved to the instance. The result? 3/4s of the raid staring at a fresh instance after a wipe and run. We tried everything to get the proper instance loaded up, from disbanding the raid and making one of the people with the instance properly saved raid leader to having the entire raid log for an hour. Nothing. Nada. I sure as fuck wasn't going to kill Skeram again and get called for cascading. Waste of goddamn time. Bug Trio is apparently fucked also.

It's almost like there's a huge neon sign right above the gate to AQ40 that says

Just Fucking Go to Naxxramas Already. This Place is AIDS.


P.S.

Blizz knows about the no-save bullshit. GMs give nothing but an automated respone. Anyone else get dicked over by this shit recently?

Word on the street is that the raid ID thing is being hotfixed. When you guys got split up, did you try putting the people that got the raid ID in group 1, and then move anyone that didn't have into group 1, then zone in? I've heard this works.

As for AQ40, the Skeram clones porting to the same platform was fixed. The triplets are still very doable -- they just aren't the complete joke they used to be. Seriously, with a little practice, the standard Kri -> Yauj -> Vem order was ridiculously easy. It should still be totally manageable if you have warriors outranging Yauj and just intercepting to interrupt heals. Either that or keep a warrior fear-warded if you're alliance.

I've heard some wacky shit happening with the Twin Emps though, where Vek'lor is immediately charging the warlock tanks on switches, or Vek'nilash immediately uppercutting the warlock on the port. I'm pretty sure this is a bug. All it means is that warlocks can't take over tanking with proximity aggro, so they just have to steal aggro with searing pain instead. Still much easier to just use warrior tanks the whole time, assuming you're alliance. Not sure if horde can get away with it.