Bounty failed despite succeeding.

Bounty failed despite succeeding.

in Bugs: Game, Forum, Website

Posted by: aswedEMD.3597

aswedEMD.3597

We were doing a guild bounty training on Devious Teesa, confronted her before our time ran out, and beat her before that time ran out as well. For some reason though, despite beating her (see chat in screenshot that shows we definitely beat her), it says we failed the guild bounty training in our guild history. I’d try to reproduce it if I could, but obviously that’s a bit hard to do with the random nature of bounties, especially with our very small guild.

Attachments:

Bounty failed despite succeeding.

in Bugs: Game, Forum, Website

Posted by: Illconceived Was Na.9781

Illconceived Was Na.9781

To get an official answer, you’d have to create a support ticket and work with customer service. What follows is my impression.

There are two timers you have to beat:

  • The event timer on defeating Tessa.
  • The overall timer for the bounty.

The screenshot you showed doesn’t indicate whether you succeeded in beating either of those. I have seen more than a few guilds fail one or the other of above, and (some) members were convinced (at the time) that the bounty was defeated soon enough for both. The individuals in question only were able to change their mind, because other folks had been watching the timers and/or actually had screenshots.

In this case, the screenshot shows Teesa yielding at 5:03, the bounty failing @ approximately 5:03 (one minute before 5:04) and being started at 4:48 (16 min before 5:04). That’s consistent with barely missing the deadline for the training.

That doesn’t mean you didn’t encounter some sort of bug; it just means that there are other possible explanations.

John Smith: “you should kill monsters, because killing monsters is awesome.”