Dungeons should not close when...

Dungeons should not close when...

in Guild Wars 2 Discussion

Posted by: Ace.1726

Ace.1726

I don’t know why this is the case but this needs to change.

Dungeons should not close when...

in Guild Wars 2 Discussion

Posted by: TheDaiBish.9735

TheDaiBish.9735

They shouldn’t close when…

C’mon, the suspense is killing me.

Life is a journey.
Time is a river.
The door is ajar.

Dungeons should not close when...

in Guild Wars 2 Discussion

Posted by: cesmode.4257

cesmode.4257

They shouldn’t close when…

C’mon, the suspense is killing me.

Lol I know hahahaa
They shouldn’t close…when…what? Im lost!

Karma is as abundant as air, and as useless as the Kardashians.

Dungeons should not close when...

in Guild Wars 2 Discussion

Posted by: ghettogenius.9174

ghettogenius.9174

Haha. Yeah. But what is not funny is that we can all finish that statement. Group leadership should be passed to a member still in the instance when the current leader leaves the dungeon or group.

I’ve mentioned this before, and it has to be tied to the story/explorer dungeon types and variables therein. My guess is when the leader (whose character model is keyed in on) of a dungeon leaves instance, the engine loses the reference for that model in the cutscenes and therefore must close the instance. Just a guess though.

Dungeons should not close when...

in Guild Wars 2 Discussion

Posted by: ricky markham.8173

ricky markham.8173

im wondering too
dungeon should not close when there a new patch?
dungeon should not close ..? come on finish the sentence

Dungeons should not close when...

in Guild Wars 2 Discussion

Posted by: Tiger Ashante.1792

Tiger Ashante.1792

Dungeon should never close until you decide to leave, period!

Edit: btw this is how it worked in gw1, you were never kicked from a dungeon even when everyone has left, you could stay as long as you wanted to explore or w/ever and i don’t see why it shouldn’t be the same in gw2.
I’ve been kicked out of dungeons on number of occasions just b4 i got my chest or trying to grab a poi but the leader grabs his chest and leaves immediately, never bothering to ask if everyone was ready to leave. This should never happen. it’s horrible, especially when u trying to explore Arah.

(edited by Tiger Ashante.1792)

Dungeons should not close when...

in Guild Wars 2 Discussion

Posted by: CC Jörn.5960

CC Jörn.5960

Hey Ace,

could you please add more details on what you exactly wanted to describe with your post. This would allow us to evaluate if you’re reporting a bug or if you’re making a suggestion and lead you to the right place on the forums.

Thanks for your cooperation.

Dungeons should not close when...

in Guild Wars 2 Discussion

Posted by: ilr.9675

ilr.9675

Obviously he’s referring to when the Instance Creator leaves….

This is a sticky issue b/c currently we can also benefit from it when we join a PUG of Guildies that we have no reason to trust…. in many cases lately whom will vote-kick you and probably one other “filler” to bring in their own guild members for a free 60 tokens for people who literally did nothing but “be online and show up” to get them. IoW: kicking the instance owner backfires on them and penalizes their SCAM when you’re the player who did all the Story Modes and then started the dungeon before they could.

(edited by ilr.9675)

Dungeons should not close when...

in Guild Wars 2 Discussion

Posted by: SeNoZinD.9874

SeNoZinD.9874

Best Troll Post 2013

Dungeons should not close when...

in Guild Wars 2 Discussion

Posted by: Absconditus.6804

Absconditus.6804

As others said, it’s pretty obvious that the full sentence is “Dungeons should not close when the instance owner leaves party”. This is a issue that anyone that has done a few dungeons knows about, and probably gets annoyed about as well.

Whoever the instance belongs to, decides to leave for whatever the reason, right at the end of the dungeon, perhaps from rage quitting, genuinely needing to go, or whatever else the case might be. This results in the whole party being booted out, even if they wish to continue. It’s a horrible design in a game mode that is pretty obviously hosted on ArenaNet’s side (unless magically everyone that plays Guild Wars 2, have excellent connections and I’m wrong). Why are there even ‘instance owners’ in the first place?

Vella Absconditus | Human Mesmer
Seafarer’s Rest

Dungeons should not close when...

in Guild Wars 2 Discussion

Posted by: Rhaps.8540

Rhaps.8540

Could equally be “Dungeons should not close when their waypoint is contested.” maybe he doesnt like having to do events to unlock CoF/Arah.. we just don’t know!

Seafarer’s Rest – Guild Leader The Deamon Army [TDA]

Dungeons should not close when...

in Guild Wars 2 Discussion

Posted by: Nuka Cola.8520

Nuka Cola.8520

Its so obvious what TC meant and some were lost… c’mon

Fact: every Thief tells you to “l2p” when the subject is to nerf stealth.

Dungeons should not close when...

in Guild Wars 2 Discussion

Posted by: Erasculio.2914

Erasculio.2914

As others said, it’s pretty obvious that the full sentence is “Dungeons should not close when the instance owner leaves party”.

As mentioned, the OP could as well be talking about how specific dungeons become closed when certain dynamic events are happening near them. Considering this topic was created during the Cursed Shores exploit, in which those trying to do the Arah dungeon often saw players not wanting to open the dungeon, it’s a possibility that the OP would be complaining about this system.

It’s funny how often people who claim something is “obvious” are completely wrong about whatever they are talking about.

“I think that players are starting to mature past the point of wanting to be on that
treadmill, of being in that obvious pattern of every time I catch up you are going to
put another carrot in front of me” – Mike O’Brien right before Ascended weapons

Dungeons should not close when...

in Guild Wars 2 Discussion

Posted by: Lucky.9421

Lucky.9421

Our group was recently trolled when the creator left right as the final boss reached about 5% health. I have heard other reports of this behavior. It seems to be getting more common.

If it is trollable, people will troll it. Anet should address this before it gets out of hand.

Dungeons should not close when...

in Guild Wars 2 Discussion

Posted by: ricky markham.8173

ricky markham.8173

Obviously he’s referring to when the Instance Creator leaves….

This is a sticky issue b/c currently we can also benefit from it when we join a PUG of Guildies that we have no reason to trust…. in many cases lately whom will vote-kick you and probably one other “filler” to bring in their own guild members for a free 60 tokens for people who literally did nothing but “be online and show up” to get them. IoW: kicking the instance owner backfires on them and penalizes their SCAM when you’re the player who did all the Story Modes to started the dungeon before they could.

thanks for the clarifycation i dont do dungeon with pug only guild group so never come across this. truly didnt know what op was hinting at

Dungeons should not close when...

in Guild Wars 2 Discussion

Posted by: sinzer.4018

sinzer.4018

This definitely needs to change, its an incredibly easy method of griefing.

I’ve mentioned this before, and it has to be tied to the story/explorer dungeon types and variables therein. My guess is when the leader (whose character model is keyed in on) of a dungeon leaves instance, the engine loses the reference for that model in the cutscenes and therefore must close the instance. Just a guess though.

I’ve never thought of it like this. If this is the case perhaps it would be best of the cutscene is based on your character and no one else’s.

Dungeons should not close when...

in Guild Wars 2 Discussion

Posted by: zenleto.6179

zenleto.6179

This definitely needs to change, its an incredibly easy method of griefing.

I’ve mentioned this before, and it has to be tied to the story/explorer dungeon types and variables therein. My guess is when the leader (whose character model is keyed in on) of a dungeon leaves instance, the engine loses the reference for that model in the cutscenes and therefore must close the instance. Just a guess though.

I’ve never thought of it like this. If this is the case perhaps it would be best of the cutscene is based on your character and no one else’s.

There’s an idea. Probably the best one for the day.

Fire up the Hyperbowl ma, we’re going to town!

Would you like some hard cheeze with your sad whine?