The title speaks for itself but was this intentional? It’s not a big issue so don’t get me wrong here but it does make VoA less fun to do as you will always have ppl flagged and a few who isn’t if you summon them inside. Messes up heals.
Any info or confirmation on this will be appreciated.
Best of Regards!
EDIT:
3 days later and 85 views without someone making even a little mark.
I got my answer then, people don’t care and Blizz not interested telling why adding this all of sudden without any word about it with the last patch.
Guess I’m done as well then fishing daily in WG or farm Eternal Life being flagged the milisec you enter that area. If I want to gank (or get ganked) I would play on a PvP server and before the trolls or such will type “pve scrub, don’t care”.
I’ve played mostly on PvP servers tbh, played the game since the betas 2005. Heck I even remember my first server back in Vanilla called “Burning Blade” and yes PvP server but today I’m 43yr old with family etc and don’t care about that anymore so I decided to play on a PvE server and PvP when I want but then comes Blizz and change something that was not there from the start of Wrath.
I need to start to care less about things too it seems.
Despite I noticed immediately and was asking myself this question as to why did they change it, it has no impact basically. People on PvE realms are usually well behaved and with the exception of absolute dushbags, players of both factions will just coexist despite having the pvp enabled. I usually do my daily fishing and meet horde players who are mining around me at the same time, sometimes we wave at each other and usually just ignore each other. As it should be.
“Pvp activity/zone flags me for pvp.”
No it’s not an issue. If you struggle to buff or hea flagged/unflagged then tell everyone to flag or reroll to a pvp server where this flag/unflag nonsense doesn’t exist.
Pve has had trouble with buffs/heals on flagged/unflagged targets since day 1. Takes 1 second to fix yourself.
You got that right. Imagine spending 10 minutes on a thread expecting people to reply or care when all your raid has to do is type /pvp
This is how it always used to be, I was suprised when farming on a PVE server that I wasn’t flagged. To be flagged in a PVP zone even on a PVE server is the correct blizzlike way this should be. It was how it was back in original Wrath and looks like they just fixed the error.
On PvE servers, atleast on mine, Mirage Raceway you did not get flagged in WG. Only when you signed up for the fight itself each 3 hours but between those fights you could go there and do w/e you fancy. But again, after last update you get instant flagged the milisec you land in WG area.
However, I’ve seen other people telling it’s always been that way and if that is correct, then Blizz simply forgot to have that system activated and did so now. But you’ll have to agree that it’s strange that at first you weren’t tagged, then up until now suddenly you are ^^
@Bigbazz
Then explain to me why we didn’t get auto flaged before and now we do. Yes I’m fully aware WG is a zone ment for PvP but I rest my case.
Noticed the same, though since there was no VoA this week I guess it flew a bit under the radar. It is new, you get flagged for PvP now.
Not on PvE servers, we’re talking about the outside world. Not the instanced battleground. It did not do so before, and since instanced WG is a wotlk remastered thing there is no standard of ‘normal’ compared to the original.
When I played during 2008 onwards and did the fishing daily there I did get flagged for PvP, they must have changed it for Classic. It is possible I went there during the fight.
Yeah… as I said this isn’t original wrath, it’s wotlk remastered. WG is now an instanced battleground, so it’s very possible that lead to different design choices in the area that is left. This has nothing to do with original wrath, and leaving that in for 5 months gives the idea it’s full and well intentional.
Again, it DID exist as a PvE Zone, and again this wasn’t in Wrath, so there is no way to know if it was considerd a ‘Bug’ or a design choice. There is no precedent on the matter, so unless they made a mention of it somewhere recently, it remains unclear.