Pl0x
Are nightmare completions and dragon kills going to be retroactive?
#1
Posté 10 juillet 2015 - 03:02
#2
Posté 10 juillet 2015 - 08:29
the perilous dragon kills weren't completely retroactive, the completions with the new characters weren't retroactive - why should it be any different now?
- kaileena_sands, Silversmurf et Zantazar aiment ceci
#3
Posté 10 juillet 2015 - 08:32
the perilous dragon kills weren't retroactive, the completions with the new characters weren't retroactive - why should it be any different now?
Perilous dragon kills were retroactive if you had the killing blow.
#4
Posté 10 juillet 2015 - 08:34
Perilous dragon kills were retroactive if you had the final kill.
yeah, but that wasn't intended from BW so they changed it to "be in a party who kills the dragon" which WASN'T retroactive
#5
Posté 10 juillet 2015 - 08:37
yeah, but that wasn't intended from BW so they changed it to "be in a party who kills the dragon" which WASN'T retroactive
The fact remains that it was retroactive.
#6
Posté 10 juillet 2015 - 08:45
The fact remains that it was retroactive.
sure, you're right ![]()
(I didn't land the killing blow too often but completed way more matches, which now feels kind of a waste of time - especially since they are now 'as a party, kill x dragons'
)
... sorry, I'm just a little sour when it comes to the topic of 'retroactive', 'tracking' and stuff... BW says promises sth and then doesn't act on it ![]()
same thing with the bugged servers during the last weeks daily challenges - some completions didn't count as well and no compensation was given (I know - a minor thing, but it still bugs me...)
- Zantazar aime ceci
#7
Posté 10 juillet 2015 - 08:46
Perilous dragon kills were retroactive if you had the killing blow.
The killing blow player was not intended.
The fact remains that it was retroactive.
The point is that what was intended (team kill) was not retroactive, what was not intended (one player kill) was retroactive.
Zan the Man has a Plan
- Dekibra et Silversmurf aiment ceci
#8
Posté 10 juillet 2015 - 09:32
The killing blow player was not intended.
The point is that what was intended (team kill) was not retroactive, what was not intended (one player kill) was retroactive.
Zan the Man has a Plan
I am not saying that it was intended, nor that it was fair for only the player with the killing blow to get credit. Dekibra said nothing about it not being retroactive for the team, but implied that it was not retroactive at all. My post was just intended to show that to some degree it was retroactive. Skewing facts does not help.
#9
Posté 10 juillet 2015 - 09:37
I am not saying that it was intended, nor that it was fair for only the player with the killing blow to get credit. Dekibra said nothing about it not being retroactive for the team, but implied that it was not retroactive at all. My post was just intended to show that to some degree it was retroactive. Skewing facts does not help.
corrected my initial post
#10
Posté 10 juillet 2015 - 09:43
I am not saying that it was intended, nor that it was fair for only the player with the killing blow to get credit. Dekibra said nothing about it not being retroactive for the team, but implied that it was not retroactive at all. My post was just intended to show that to some degree it was retroactive. Skewing facts does not help.
Skewing facts does not help ... help what?
I think that most readers realise what Dekibra meant, your reply regarding retroactive on the player with the final kill seems pedantic in correcting what was said literally but not with it's intended meaning.
So, yes you are correct in everything that you have said. But more importantly to reiterate the point:
.... what was intended (team kill) was not retroactive, what was not intended (one player kill) was retroactive.
Zan the Man has a Plan
- Dekibra aime ceci
#11
Posté 10 juillet 2015 - 09:56
At this point I highly doubt they will be retro.
But hey, have you and your friends already got all the Hakkon weapons?
If the answer is no, then there is no reason to worry about whether they are retro or not ![]()
- Jailson_MMB, Proto et Snakebite aiment ceci





Retour en haut






