Party Finder issue with normal and vet

iTz_Ryzr

I queue up for a normal random dungeon. When the queue pops, normally everyone gets teleported in, but the issue I've been having/ seeing is that the dungeon is in normal mode, but the party finder says it's in vet. This results in people under level 50 not being allowed to enter the dungeon. This has happened to me today and to other people in my group yesterday, we aren't teleported in and can't join as a result of the dungeon mode being set to veteran even though it's a normal dungeon.

When I was on my level 40, I queued up for a random and was put in one, but not teleported. I couldn't join the group in the dungeon because it was set to vet mode in the party finder despite being a normal dungeon. On my CP character, other players (not level 50) were not teleported into the dungeon when others were. This is quite a nuisance.

fits96

This just happened to me. Was in que with a low lvl toon and when our group was formed me and another were not allowed into the dungeon. Message was CP lvl too low, for a normal. Had no choice but to leave group, very aggravating considering that ques are already 30+ min. and having to suffer an additional time out for leaving group and then wait another 30 min.in a new que.

Faylestar

I've been getting this since the patch on one specific character.

Queue for normal, get in a group with Dungeon Mode: Veteran, be unable to zone in, cant teleport to the group, cant zone in. Groups even say its not actually a vet dungeon.

The character is 44. It cant even queue for vet.

Makronette

I had this happen to me earlier, queued for normal on my lvl 35, got a group for Eden Hollow l, game told me I wasn't eligible to get in to the dungeon due to my lvl/CP and was unable to teleport in, I know it wasn't a vet because someone else in the group was lvl 40 and they along with the other 2 people were already in the dungeon.

kriger09

I think I know why this happens (at least sometimes):

If the person who is assigned group leader has their default dungeon settings set to "veteran" but was queued for a normal dungeon, the group menu will show that the dungeon is veteran, even though it isn't (the map will say normal, and the content/drops are still at normal). So the players without the appropriate level for the veteran version of the dungeon cannot enter, despite the fact that everyone queued as "normal" and the dungeon is in reality normal.

Since any given person will usually not end up as group leader, or maybe there won't be a lower level person in the group, it's not an obvious problem to the person causing it (ie the one who has their setting to "veteran") because it won't trigger consistently. And the person affected can't do anything to fix it, because it's other people's settings (which can't be changed once the dungeon starts, so there's no way to fix it on the fly to let them in).

This really needs to be explained more widely, because the people causing the problem have no idea because it won't happen to them every time and it's hurting others and not them.

But it also needs to be fixed, because once people DO know about it, some jerks will do it intentionally to keep low level players out of their run (I KNOW that most mechanics mean that having a low level player isn't worse than no player at all. But never underestimate pettiness).

Scion_of_Yggdrasil

I've had a similar, but different, scenario. My dungeon load screen was vet (I queued for normal) then halfway through it blinked and was normal (not vet).

I've also had issues with others, or myself, not being allowed in the dungeon ("instance full" message).

This is the first I'm hearing about this particular problem.

abelsgmx

2 times here, queue for normal dungeons with no vet toons and placed in a vet dungeon group and need wait 15 minutes to queue again, kinda annoying bug

zaria

kriger09 wrote: »

I think I know why this happens (at least sometimes):

If the person who is assigned group leader has their default dungeon settings set to "veteran" but was queued for a normal dungeon, the group menu will show that the dungeon is veteran, even though it isn't (the map will say normal, and the content/drops are still at normal). So the players without the appropriate level for the veteran version of the dungeon cannot enter, despite the fact that everyone queued as "normal" and the dungeon is in reality normal.

Since any given person will usually not end up as group leader, or maybe there won't be a lower level person in the group, it's not an obvious problem to the person causing it (ie the one who has their setting to "veteran") because it won't trigger consistently. And the person affected can't do anything to fix it, because it's other people's settings (which can't be changed once the dungeon starts, so there's no way to fix it on the fly to let them in).

This really needs to be explained more widely, because the people causing the problem have no idea because it won't happen to them every time and it's hurting others and not them.

But it also needs to be fixed, because once people DO know about it, some jerks will do it intentionally to keep low level players out of their run (I KNOW that most mechanics mean that having a low level player isn't worse than no player at all. But never underestimate pettiness).

Now this makes some sense, lots of players farm random normals for cp but stay on vet because easy pledge runs, vCoA1, vWayrest 1 is easier than many of the normal dlc.

CanAPanda

This has happened to me countless times and according to others its been happening since launch, curious if they even care at this point

ForeverJenn

kriger09 wrote: »

I think I know why this happens (at least sometimes):

If the person who is assigned group leader has their default dungeon settings set to "veteran" but was queued for a normal dungeon, the group menu will show that the dungeon is veteran, even though it isn't (the map will say normal, and the content/drops are still at normal). So the players without the appropriate level for the veteran version of the dungeon cannot enter, despite the fact that everyone queued as "normal" and the dungeon is in reality normal.

Since any given person will usually not end up as group leader, or maybe there won't be a lower level person in the group, it's not an obvious problem to the person causing it (ie the one who has their setting to "veteran") because it won't trigger consistently. And the person affected can't do anything to fix it, because it's other people's settings (which can't be changed once the dungeon starts, so there's no way to fix it on the fly to let them in).

This really needs to be explained more widely, because the people causing the problem have no idea because it won't happen to them every time and it's hurting others and not them.

But it also needs to be fixed, because once people DO know about it, some jerks will do it intentionally to keep low level players out of their run (I KNOW that most mechanics mean that having a low level player isn't worse than no player at all. But never underestimate pettiness).

That's exactly what's happening. I'm glad to see I'm not the only one understanding why this happens.

Diva_Naoko

kriger09 wrote: »

I think I know why this happens (at least sometimes):

If the person who is assigned group leader has their default dungeon settings set to "veteran" but was queued for a normal dungeon, the group menu will show that the dungeon is veteran, even though it isn't (the map will say normal, and the content/drops are still at normal). So the players without the appropriate level for the veteran version of the dungeon cannot enter, despite the fact that everyone queued as "normal" and the dungeon is in reality normal.

Since any given person will usually not end up as group leader, or maybe there won't be a lower level person in the group, it's not an obvious problem to the person causing it (ie the one who has their setting to "veteran") because it won't trigger consistently. And the person affected can't do anything to fix it, because it's other people's settings (which can't be changed once the dungeon starts, so there's no way to fix it on the fly to let them in).

This really needs to be explained more widely, because the people causing the problem have no idea because it won't happen to them every time and it's hurting others and not them.

But it also needs to be fixed, because once people DO know about it, some jerks will do it intentionally to keep low level players out of their run (I KNOW that most mechanics mean that having a low level player isn't worse than no player at all. But never underestimate pettiness).

I've had this happen to low level alts, and I believe this is the most likely explanation. That said, the person causing it should notice that the group has one or more players missing. Next time it happens we should ask crown to check their dungeon settings and to please disband group and queue again, so as not to penalize other players with 15 min timer.

abelsgmx

2 times today and i need wait 15 minutes to try again for a developers mistake, nice thing