http://www.guildwarsguru.com/forum/s...php?t=10321835
This is from a closed forum where a party member zoned out before the other member appeared in the zone resulting in a death.
If this happens to you, you will get a death tacked on to your toon.
Survivor haters can use this against you. that can go in and out before you get there and I think that this is wrong to suffer a death at the hands of others leaving before you zone especially with only 500 XP left to get the max survivor title.
I am going for the Survivor title and when I read that I was REally? Scarry stuff
Watch Out Survivors
imnotyourmother
Vamis Threen
There weren't any links in your post for me to follow. However I can guess what it's about.
It doesn't matter.
You should never play with other people (not fair on them, stupid for you) or use a slow computer when going for survivor. If you follow these simple rules then the above will never happen to you.
That is all.
It doesn't matter.
You should never play with other people (not fair on them, stupid for you) or use a slow computer when going for survivor. If you follow these simple rules then the above will never happen to you.
That is all.
Shursh
yep i encountered this same problem (i was NOT going for survivor title, and neither was the person i accidently killed)
we zoned into north kryta, i realized i had the wrong build, quickly zoned back into outpost before my friend had loaded. i get back in town with him not in the group, get a pm from him a minute later, "wtf man, i'm dead??"
anyone know if this bug is going to be fixed anytime soon? not that it really matters, if you are going for survivor, this is very easy to avoid by use of common sense...but still, a minor annoyance at times.
we zoned into north kryta, i realized i had the wrong build, quickly zoned back into outpost before my friend had loaded. i get back in town with him not in the group, get a pm from him a minute later, "wtf man, i'm dead??"
anyone know if this bug is going to be fixed anytime soon? not that it really matters, if you are going for survivor, this is very easy to avoid by use of common sense...but still, a minor annoyance at times.
Kattar
http://www.guildwarsguru.com/forum/s...php?t=10321835
Link is above. And it's not a bug, as is mentioned in the thread. So don't go getting all freaked out about losing your survivor.
Link is above. And it's not a bug, as is mentioned in the thread. So don't go getting all freaked out about losing your survivor.
Arduin
It's even scarier this isn't a bug. Now people can intentionally screw other peoples survivors over.
Nightow
Quote:
|
Originally Posted by Arduinna
It's even scarier this isn't a bug. Now people can intentionally screw other peoples survivors over.
|
Kattar
It's not just when one person zones, it's when the whole party but you zones just after you load. It's been this way for as long as I can remember.
Simple solution, if you're going for survivor, in Pre: don't group with someone who won't wait on you to load (no PuGs), or in the rest of the game: -image the .dat file so there's less of a chance that everyone leaves before you finish downloading.
Simple solution, if you're going for survivor, in Pre: don't group with someone who won't wait on you to load (no PuGs), or in the rest of the game: -image the .dat file so there's less of a chance that everyone leaves before you finish downloading.
Taixen
When it is possible to obtain a Max Survivor title in little more than a day through means of something like the Boxing in EoTN if you are unlucky enough to lose your Survivor Title because of this issue just Re-Roll and be a little more careful.
Evil_Necro
thanks for the info ^_^
Now gotta watch out
Now gotta watch out
Jae Onasi
I gotta ask why in the world it would be programmed intentionally as a death instead of just leaving you by yourself in the zone, however.
Kattar
It's programmed as a /resign. If you're the party leader, it should leave you in the zone. If not, you die.
Nightow
Katsumi, I understand you when you said, "It's been this way for as long as I can remember." but Jae Onasi does bring up a good point. Is it intentional or not? If not, I'd say it's a bug. Long lasting one yes but still.
Kattar
No, I just mean that's the way it's programmed. In every other instance, that's fine. So technically, it's not a bug, it's a game mechanic that is functioning as intended. Hence why it was closed in Game Bugs.
Kashrlyyk
Quote:
|
Originally Posted by Katsumi
No, I just mean that's the way it's programmed.
|
Quote:
|
Originally Posted by Katsumi
In every other instance, that's fine. So technically, it's not a bug, it's a game mechanic that is functioning as intended. Hence why it was closed in Game Bugs.
|
Amy Awien
It's a bug when the behaviour of the program does not meet the specifications, no matter if it's 'the way it's programmed' or not.
Kattar
I won't debate whether real bugs are coded intentionally or not, or whether something that is broken, but "working as intended" is a bug or not. There's no point in a philosophical debate as to the nature of every game bug.
And no, I don't work for ANet. All I do is mod for the Game Bugs forum. I have had this happen to me enough times to know that this acts like a /resign when it happens though. I'm only speaking from experience. But of course, since I post here and try to explain why this is the way it is, I get responses like this.
If you like, pm Andrew Patrick or anyone else on the QA team here or on the wiki.
And no, I don't work for ANet. All I do is mod for the Game Bugs forum. I have had this happen to me enough times to know that this acts like a /resign when it happens though. I'm only speaking from experience. But of course, since I post here and try to explain why this is the way it is, I get responses like this.
If you like, pm Andrew Patrick or anyone else on the QA team here or on the wiki.
FoxBat
But the thing is, /resign doesn't increase your death count. Why does this? (Or does it?)
Amy Awien
Quote:
|
Originally Posted by Katsumi
... since I post here and try to explain why this is the way it is, I get responses like this. ...
|
On a practical note, if -image doesn't work out, how would bringing a hero along? If it only occurs if all other party members are rezoned before you connect, your hero should prevent all party members from rezoning, since it tends to stay with you.
Kattar
Quote:
|
Originally Posted by Official Wiki
Resignation does not count towards the survivor title track.
|
EDIT: Reopened the thread in game bugs, if anyone cares to go there and test to see whether this actually gives you a death or not.
the Puppeteer
Bottom line: don't PuG
Taki
Quote:
|
Originally Posted by Katsumi
Knew this was here somewhere. ANet says it doesn't. But I'm sure they'll be people that will post otherwise.
EDIT: Reopened the thread in game bugs, if anyone cares to go there and test to see whether this actually gives you a death or not. |
Kattar
Regardless, it doesn't count as a death, which is the important part.
illidan009
Quote:
|
Originally Posted by the Puppeteer
Bottom line: don't PuG
|
zwei2stein
Quote:
|
Originally Posted by Katsumi
Regardless, it doesn't count as a death, which is the important part.
|
daze
/resign doesnt count as a death and neither does instant death. I have been a victim of both on my survivor and still retain 0 deaths. However, i have never been a victim of the "mapping out before i load" death because i follow the first 3 rules of Survivor.
1: Dont PUG
2: Always go solo or with H/H
3: Never bring Human players.
When i grind bukdek byway for my survivor title, i resigned each time i was done clearing the map and it never counted as a death.
1: Dont PUG
2: Always go solo or with H/H
3: Never bring Human players.
When i grind bukdek byway for my survivor title, i resigned each time i was done clearing the map and it never counted as a death.
Courage!
THATS MY LINK i copyrighted that
Kattar
Quote:
| Care to change thread title then? |
Plus, I'm not a Riverside mod, so...
Faer
Quote:
|
Originally Posted by Kashrlyyk
Do you work for ANet and therefore know it is not a bug?
|
Katsumi is pretty bad at Guild Wars (Backfire, lawl), but he's got fairly good judgment when it comes to these sorts of things. Personally, I'd trust his word above any one (or even small set of) actual ArenaNet employees any day, as they have already proven to be incompetent time and time again. He has yet to make a total buffoon of himself.
Just don't play the game with him. He's terrible.
(<3)
Hyper.nl
Quote:
|
Originally Posted by Katsumi
Regardless, it doesn't count as a death, which is the important part.
|
imnotyourmother
but if the other person leave BEFORE you map in. The comment on just use a faster computer does not apply. If there are files to load and you have never been there you are in for some serious trouble even with the fastest computer in the world if it is "Loading" the area and the people do not want to wait and they leave your dead. Plain and simple.
You suffer a death at the hands of another playing taking 0 damage. You health bar says 0 so you are dead.
This needs to be looked at.
You suffer a death at the hands of another playing taking 0 damage. You health bar says 0 so you are dead.
This needs to be looked at.
Kattar
Quote:
|
Originally Posted by imnotyourmother
You health bar says 0 so you are dead.
|
If it acted like a /resign, then you would appear dead, but the "death" would not add 1 to the /deaths command.
If it gave him a death, it could be a bug. But the OP never posted whether it caused a death or not, so we can't be sure.
From the screenshot, it looked like it should not have counted as a death.
/thread