Guild Wars 2

Why anet kill players on disconnect? Maybe time to fix this?

At that moment ANET always kill player on disconnection from dungeon instance.

It seems like the bug from fractals returns to all game wide!

It was a bug with fractals where people logged out to repair mid fractal and still be able to rejoin group as long as you didn’t leave party. Also you can still do this now, its not an exploit, but you died as a side effect which was the bug. It happens in wvw and everything else instanced/another map now.

didn’t u use to be able to res in combat and teams just had to res rush boss to stop he recovering making every boss easy.

I’m pretty sure when they disabled the ressing while in combat they also introduced this to stop you getting around not being able to res by just logging out and coming back in alive.

Nah. If you were dead in one area you didn’t come back alive in another (unless you used a waypoint). Since I didn’t use a waypoint, I stayed dead if I was dead in a dungeon. This occurred as intended when I DCed and came back still dead outside a dungeon.

The problem here is leaving an area by log out alive, then being killed when coming back in game. It originated in fractals.

You joined dead if your party is in combat or now and again it seems to bug out and spawn you dead when there not but most the time if party isn’t in combat u join alive. If they r not in combat the dialog to re-spawn shows up straight away in fractals or u can waypoint straight away to get up. its only 1 or 2 clicks of a button…

If they are in combat u have to wait for them to leave a pain if you got disconnected but its something that has to stay otherwise its open to abuse.

Most of you are right and wrong.

There are a few things:

Leaving Fractals and rejoining Fractals will not kill you, unless any person in your group is in combat.

In a party instance, you may not res while your party is in combat (AI does not count, unless that AI forces a player in combat).

If you are dead and zone into an instance, you remain dead.

If you disconnect, your body persists in game for approximately 5 minutes before the game realizes you have lost connection. During this time, it is possible to die.

Each of these things is a solution to a different problem. From top to bottom (not necessarily chronologically in terms of implementation):

Leaving and rejoining Fractals killing players is in response to players leaving the dungeon by relogging, repairing, then joining back in during long boss fights, particularly when one person is cheesing the boss by staying in combat with or without dealing damage (see: Nade kit vs Mossman, which is also why we have Skelks appear).

In a party, you may not res while your party is in combat because the age-old tactic of beating hard bosses was having everyone rush the boss, and as people die, they waypoint and run back to the boss, essentially “zerging” the boss (without the mass numbers, but with a constant flow of forces, assuming not everyone dies). Still possible to do, but requires all players to get out of combat without reseting the boss.

If you are dead, you will stay dead. Seems kind of logical and was in place from the beginning.

Disconnecting and your body persisting is in case you have a slow or bad connection and used to reconnect. However, this is a relic from GW1 since GW2 does not properly attempt to reconnect you to the service if your connection is lost (if your connection is slow, then you’re fine), no matter how little time your connection was interrupted. People with slow connections will simply have latency and potentially “rubberband” lag. People with hiccup connections will find it nearly impossible to play GW2 with the constant black screen-ing and the client taking upwards of 10 minutes to notice it has lost the connection, making it faster to alt+f4 (or apple+q) and re-open the game, even if you’re not on an SSD where the game can take a few minutes to open up.

Works the same in WvW. If you are in combat and disconnect you will log back in dead. If you are not in combat and disconnect you will log back in alive. The system is in place to prevent the Alt-F4 group from avoiding a stomp.

Theftwind.8976:

Works the same in WvW. If you are in combat and disconnect you will log back in dead. If you are not in combat and disconnect you will log back in alive. The system is in place to prevent the Alt-F4 group from avoiding a stomp.

Actually, that’s not entirely true.

When you alt f4 while in combat in WvW, it counts as a “forfeit” and you instantly die, causing all players who have tagged you to gain loot. Before, players would duel and alt f4 if they were ever downed, right before the stomp. This prevented other players from getting loot and kill credit.

I was just PvEing yesterday in Mount Maelstrom when I realized I must’ve lost connection. (I was running around and nothing was responding to me). Sure enough, a few moment later I got the disconnect notice. When I got back I was dead on the ground. Not sure that’s ever happened to me before, even at the super-crowded Maw after reset where I’ll often lag out, disconnect and come back okay. (Sometimes WITH the chest waiting!)