Jump to content

Search the Community

Showing results for tags 'pool of darkness'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Русскоязычное сообщество
    • Новости и анонсы
    • Игровые события
    • Вопросы и ответы
    • Общий раздел
    • Руководства по игре
    • Классы
    • Предложения
    • Поддержка
    • Тестовый сервер
    • Гильдии
    • Конкурсы
    • Уголок творчества
    • Таверна
  • International
    • News & Announcements
    • Game events
    • Must read for everybody
    • Support
    • New Players
    • Videos of the game
    • General
    • Guides
    • Class Discussion
    • PvP and Arena
    • Suggestions
    • Test server
    • Guilds
    • Tavern
    • Fan Art
    • Contests
  • Fórum Português
  • Fansites

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Location:


Interested in


Title

Found 1 result

  1. Hi, While we were doing some testing for AOE skill damages, we came across this bug in the warlock skill. Pool of darkness ( Side note: Probably one of the weakest AOE skills in game) does not seem to be working as it is supposed to be. When the skill is used in a crowd of large number of players, it only procs 1 tick of damage instead of 5 ticks. We tested it with a lower number of people and it seems to be working fine there. But since most of the scenarios in game consists of mass battles, there's bound to be a large crowd when the skill is used. From our understanding of the testing, It seems to stop working when there are more enemy targets than the maximum target limit of the skill. After the nerf of warlocks at the last update, the class has a painfully low number of useful skills it can use in GvGs before dying; with pool of darkness being one of them. I don't know how long this bug has been there for but it's very easy to discern since no one checks visuals during mass battles. Do check if this is the issue or if there are any other underlying issues that's causing it to proc just once. I'd also like to request that this bug be addressed and solved promptly instead of a 6 or 9 month delay. Kindly look into it at the earliest and get back to us. Please acknowledge. @Nolan @Holmes @Hedfuc @Higgings@Jcbreff
×
×
  • Create New...