Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
From what I understand, you will lose the 'reapply' effect if the person who cast Hunter's Mark does not deal the killing blow to the target it is applied to.
Is that the issue? Because if it is, then it's working as intended.
Otherwise, you need to cast it again using a new spell slot. This is one advantage Hex has over Hunter's Mark, as Hex will get it's 'reapply' effect regardless of who deals the killing blow.
(I should add that this is how it's worked in BG3 since launch...but it's not RAW. HM should be able to be reapplied regardless of who deals the killing blow).
What is hex?
edit the logic flow is: Did the target drops below 0 hp --> If yes, can be reapllied.
What you suggest is adding in an entirely incorrect step that isn't even implied in the rules text to make it: Did the target drops below 0 hp --> If yes, did the caster deal the killing blow-->If yes, can be reapllied
What are you even talking about? I already pointed that out. It seems (to me) to be how it's working currently in BG3.
@OP As to whether it's been nerfed, I haven't noticed anything from using my Ranger. If it's been changed, it's likely a bug rather than a nerf, and you should document the changed behavior of the spell and report it.