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
Further, Darkvision normally does not help with magical Darkness, though Devil's Sight does. Though in BG3's case, the "cannot make ranged attacks" still overrides this.
Inorite? If only I could see what the problem was...
Darkness and Devil's Sight haven't worked properly since EA launched.
Also, Darkness should be targetable on an object.
No idea. Devil's sight, according to the game should let you see fine in Darkness. I do remember one patch playing a melee warlock that exploited this to basically kill everything without retaliation.
The 'no ranged attacks' rule is probably the way Larian is attempting to balance the fact that while Darkness should let you attack things inside and outside it at range as per DnD (albeit with disadvantage if you dont have devil's sight), there are some ranged spells/abilities that specifically require you being able to see the target. Which is different than knowing they are there [for example, making an attack action does not require you being able to see the target, while magic missile requires you be able to see the targets]. And Larian may be having technical issues having its game engine distinguish the difference between those two notions. So they opt to just disallow all ranged attacks into or out of darkness (and other similar spells).