Guild Wars 2

I recently started play GW2 again after about 8 months of absence. I used to frequently run dungeons via the LFG system but now I’ve been finding a lot of EU players – I play on NA. (resultly, I get the 1006:9:7:388:101 network error for trying to enter an EU-hosted dungeon) This has never happened when I ran dungeons this way for months in the past.

I’ve been awkwardly hovering over party members’ names to see if they look “non-NA” but is there a way to filter between NA and EU players in LFG – aside from the flags? Or has the way dungeons are run changed in general… do people form groups from guilds?

Thanks in advance!

Odd.. I’ve never heard of this happening before. The LFG feature is supposed to be specific to each region. Naturally, since this is not supposed to happen in the first place, there is no way to “toggle” this bug off. I think your best bet is submitting a support ticket.

I’m in NA, and the only time my party has appeared in EU LFG or an EU LFG shows up in NA is when I’m partied up with someone from EU and one of us creates an LFG. Other than that, I’ve never encountered a problem the way you’ve described it

Its been happening for months. Nothing can be done about it.
I reported it. Got no response. Even posted on the forum.

https://forum-en.gw2archive.eu/forum/support/bugs/LFG-tool-not-functioning-correctly/

I had that happen a few times, too.
I noticed I was invisible when it happened, as far as I remember.

It’s a glitch that happens when you post LFG ads with any other status other than ‘online.’ I used to b*tch about this a lot around a year ago.

Any time I’d have status as either ‘invisible’ or ‘away,’ my LFG was using the opposite region’s and I’d have to apologize to any parties I joined only to get prompted with a network error.

Restarting the client fixes the issue when it happens but make sure you keep the status on ‘online’ otherwise the problem will persist.

Ahh ok thank you all so much for the replies! I actually have been on invisible this whole time and I reopened the client with “online” status – now everything is fixed.

It’s not a glitch. It’s an “Unexpected Feature”.