1. We have a QA initiative where we work with the community more closely than ever to get your bug reports into the hands of the developers. Please use this forum for LIVE Server bug reporting. Do follow the format below, because it will help us out greatly in responding. If you do not, it's possible your bug report will be misinterpreted, or worse, lost!

    Read BEFORE submitting your first bug: Reporting Bugsā€¦ QA 101 Document
    • Search for your bug before posting in order to avoid duplicate reports.
    • Only reply to an existing thread if you have additional information for the reported bug. ALL extraneous commentary will be deleted to avoid cluttering the reports.
    • Keep your bug report short and factual.
    • There is no need to submit crash logs. Crash data we require is automatically logged.
    Bug Report Template
    1. Title:
    2. Reproduction Rate:
    3. Blocker?
    4. Details:
    5. Steps to Reproduce:
    6. User Specs:
    To get started, use /bug in-game (/devbug if on QA) to auto-create this template. It will even auto-fill some of the required information and open the browser for you. Then take the information that was just saved to your system's clipboard and paste it into a new QA forum post. Thank you bug hunters!
Dismiss Notice
This Section is READ ONLY - All Posts Are Archived

[Known]Spirit Avatar. Able to fight as spirit and can't be killed or revived.

Discussion in 'Critical Issues (Blockers, Performance, Crashes)' started by Ooga Booga, Feb 25, 2018.

  1. Ooga Booga

    Ooga Booga Avatar

    Likes Received:
    Trophy Points:
    Seems a Troll has killed me in snowy mountain road encounter and I can still attack the troll without taking damage. I am still getting stunned and pushed back but I have taken half the Trolls life as a spirit and sat there for 15 minutes trying to revive while I was being attack before I noticed I could attack back. I could not loot the body though.
  2. Attenwood

    Attenwood Avatar

    Likes Received:
    Trophy Points:
    Thank you for reporting. We've been able to reproduce this issue and are currently investigating for fixes ASAP.