Guild Wars 2

Here is what I mean, if the “opener” leaves the dungeon or disconnects, the entire party will leave the dungeon as well.

This happens plenty of times and there are trolls out there leaving the dungeon before everyone gets our rewards. THIS IS EXTREMELY FRUSTRATING WHEN YOU SPENT 2 HOURS IN LEVEL 50 FRACTAL AND THE OPENER LEFT THE FRACTAL AT FINAL STAGE BEFORE THE REWARDS. At the end, we have to redo our fractals again.

Suggestions: Do not let fractals control by one player. Make it the entire team. THANKS!

I think it should just re-assign a new party leader, or perhaps not assign any at all and just have it stay open as long as someone is inside

In the case of Fractals it would need to revamp the whole entrance system and change it to the smallest PR level instead of the current highest PR available.
If this opener requirement is gone, that way it could be exploited. Ask a friend with personal level 50 to open and enter the instance. After that he / she can leave and you have a lvl50 fractal opened, even if you aren’t even close to that PR lvl.

However i agree, this whole dungeon host system needs to be looked at.

On the other hand, this is the one feature that protects you from being kicked at the end of a run so that others can replace you with a guildie.

Yea it’s a give and take removing that feature opens up opportunity for people to harass you via the crap kicking system.

If they did this what would prevent people from jumping in a group and kicking the whole group and stealing an instance? naw, the griefing is bad as it is, no need to give them more.

Dalanor.5387:

In the case of Fractals it would need to revamp the whole entrance system and change it to the smallest PR level instead of the current highest PR available.
If this opener requirement is gone, that way it could be exploited. Ask a friend with personal level 50 to open and enter the instance. After that he / she can leave and you have a lvl50 fractal opened, even if you aren’t even close to that PR lvl.

However i agree, this whole dungeon host system needs to be looked at.

You are aware that something similar was possible already before the fractured update? You invited someonw with a high level into the group, opened your fractal instance while he was in the same zone, he left, you could continue to do the higher level even if no one in the group had a character that high.
Currently I’ve heard from others that the fractal level snaps back to the highest personal level still present if the level-crutch provider leaves the group. Can’t confirm that myself though because it was never an issue for me. So take that with a grain of salt please.

Oh and just for the record, yes, we need an overhaul of the dungeon owner system and the votekick system. Badly.
But if we want to be cynical, the past has shown that this is unlikely to happen until there is a new living story instance where these two things becomes an issue.
Not being so cynical: it ight be trickier to change this than we think. I don’t know anything about the coding of these aspects of the game and how much of an effort to change those ist might be.

Still, doesn’t change that an overhaul is rather necessary.

Yeah you use to be able to do a lvl higher than anyone in the party by getting someone to come to the same overflow as you when you opened. Then they could leave and it wouldnt revert back.

Currently it switches to the highest remaining PRL in the party on instance change. So if you got someone to open 50 at the start, if they are outside of fractals or not in the party and everyone else in the party is below 50 the fractal will reset to the highest remaining PRL and i believe the host also switches (havent confirmed this). Its annoying because it means while leveling you need to make sure your host/highest opener is inside and not repairing when switching to the next fractal. Thankfully we only experienced this once because fractals are account bound xD.

Also theres the issue of host switching without you being aware of it and then the new host switches character and destroys the instance. Its a flawed system, there should be someway to identify who is the host at all times.