[Cataclysm Classic] Moonglade Guards attacking on teleport

When I teleport to Moonglade, the guards attack. It happens as I am loading so I am not accidently hitting any spells.
Someone said to unflag pvp, tried, didn’t change. Then someone said to teleport from outside capital cities, didn’t help. It isn’t just me, as the carnage at the zone in spot has bones all over.
Friends are saying it even happens when they use the death gate on their Death knights.
Please, I am just a Druid and I just want to visit my family from time to time.

3 Likes

Same issue, have happened few time to me.

1 Like

Having the same issue in moonglade and gadgetzan. Guards attacking on loading screen finish.

Same issue in Isle of Quel’Danas

Happens when you teleport from a contested zone I believe.

This never happened before to me. No matter where I teleported from. Never ever happened. TBC, wrath, cata, mop, legion, BFA, dragonflight, classic TBC etc…

But now every time i use teleport moonglade I get ganked by guards.

If i run away and de-aggro, I can come back and no issues. It’s like the teleport makes them attack you at first always.

How the hell is this bug still live after months of people reporting it? A private server with unpaid devs are more competent than this.

2 Likes

I am not sure if this was how I fixed it, but after I used teleport moonglade WHILE inside moonglade, it teleported me to the graveyard in there and now the guards do not attack me.

Still happening, happens in Nordrassil and when teleporting to moonglade.

1 Like

Still happens likely to everyone who starts the intro questline to get to Hyjal…

Happens in DK starting zone after Death Gating, Moonglade, and taking the portal from SW to Hyjal. Those are the ones I’ve personally experienced.

It’s still happening all the time. It happens when I use Death Gate on dk or hearthing. There is no pattern that I can discern that causes it to happen, it is seemingly random. I’ve been training archeology and have effectively used both in every zone in eastern kingdoms. I have played this game since OG TBC and have never had this issue its insanely annoying.

2 Likes

Simply took the SW port to Hyjal and by the time the loading screen ends:

Furious Hyjal Warden’s melee swing hits you for 28707 Physical.
Furious Hyjal Warden’s melee swing hits you for 10604 Physical.(18588 Overkill)
Furious Hyjal Warden’s melee swing hits you for 10604 Physical.(25200 Overkill)
Furious Hyjal Warden’s melee swing hits you for 10604 Physical.(Crushing) (32821 Overkill)
Furious Hyjal Warden’s melee swing hits you for 10604 Physical.(Crushing) (41806 Overkill)
You died.

Small indie company. Thanks.

Furious Hyjal Warden’s melee swing hits you for 36,935 Physical.
Furious Hyjal Warden’s melee swing hits you for 29,423 Physical.
You died.

Day 23 of Live Beta.

1 Like

This is still a problem. Please fix.

Same issue. Poor druid had a long walk back

I genuinely am baffled that this isn’t fixed. This isn’t just happening in Moonglade tele, this happens when you land almost anywhere with guards now. Even I, as a DK, using death gate, can sometimes be killed by the guards when teleporting.

They can implement PLATFORM WIDE SSO with proprietary MFA but, can’t fix this? Seriously?

1 Like

Furious Hyjal Warden’s melee swing hits you for 39,701 Physical.(Crushing) (11,261 Overkill)
Furious Hyjal Warden’s melee swing hits you for 39,701 Physical.(Crushing) (9,249 Overkill)
You died.

Day 35 as guinea pigs.

This is happening anywhere with guards that is neutral territory, when you zone into it via a teleport or after a dungeon now. :frowning:

Hello Blizzard, please fix this massively egregious bug - it is very frustrating every time I log onto Cata and get ganked by a guard in town. I’m sure this has bug has contributed to many a player deciding “I don’t feel like playing this…” and “like… are you serious? How is this bug possibly public still?”. Honestly, it’s a little pathetic for your dev and qa teams to let this garbage out in the first place, but to let it run this long?? C’mon man… fix it…

Still not fixed.