Tequatl The Invisible

#1 - May 26, 2014, 3:29 a.m.
Blizzard Post

Hi ANet team, players,

I saw that there’s a thread about the bug with the laser (haven’t paid attention so I won’t comment on this), but I’m surprised there’s not thread about Tequatl becoming invisible after the defense phase.

Basically, what happens is this:

  • Defense phase kicks in after his hp reaches 75%;
  • People successfully defend the batteries and laser and move back to double damage spot;
  • You pick your reason for the bug:
    # Some say it is caused by excessive damage dealt to Tequatl;
    # Or maybe just a wrong behaviour by the code;
  • When it’s time for Teq to come back to “life” and everyone to go to their positions, we instead get the animation where he takes off again while in fact, he, as an object, he is still on the same place (also shown there on the mini map)
  • Bone walls are spawned randomly afterwards, the usual rotation is DPS -> Destroy bone wall -> back to DPSing invisible Tequatl;
  • Defense phase kicks in again, upon successful defending the laser, Tequatl lands?! again and you just DPS him to death.

Bonus chest rewards usually get bugged too and you only get two chests as a reward.

My complaint here, and probably the complaint of many players who do Tequatl on daily basis just for the challenge, is not about the bug with the rewards that occurs, but with the fact that simply stacking under his head and bashing him to death takes away the fun of actually participating in the kill process of one of the hardest champions in-game. Not to mention that many of the achievements required for the “The Sunbringer” title are also nearly impossible to get facing the current problem.

I would be grateful if we get a response from the ANet team if they’re aware of this issue.

Thanks in advance!

Aurora/Winter

#12 - May 27, 2014, 5:05 p.m.
Blizzard Post

I would be grateful if we get a response from the ANet team if they’re aware of this issue.

Detailed repro steps like this go a long way towards helping us debug issues like this. We’re currently investigating the issue.