Toggle menu
Toggle personal menu
Not logged in
Your IP address will be publicly visible if you make any edits.

Talk:Spells

Discussion page of Spells

Latest comment: 6 January by Toancaro in topic Spells#Upcasting

Icons showing wrong spell info

Hi, in the big table, hoovering over several icons show the wrong spell information. Branding Smite and Calm Emotions are just two examples. It's minor but just thought you might want to know.

Shield spell link directs to Shields (equipment)

Not the spell

Spell table

It would be really cool if you added a column that provided each spell's school.

Multi classing ESL

I believe that bg3 rounds up even when multiclassing. i have seen reports that say they fixed it can anyone confirm maybe this should be added to the main file to explain ESL

Spells - upcasting?

In the table for spells, I think it would be a good idea to include a row for upcasting. It's extremely relevant for Warlocks, and to some extent anyone who can potentially upcast spells. For example, Spells like Hex don't upcast, Burning Hands adds another damage die, and Scorching Ray adds an entirely new ray to fire.

missing spell

sights of the seelie: summon deva is not listed as a spell anywhere on the page

Spell Properties Table missing spells

There are some spells that are missing from the "Spell Properties Table". I don't know how to add them. The ones I have noticed that are missing are: chain lightning, lightning bolt, and lightning arrow. There might be more spells missing but I only noticed these because I ctrl-f "lightning" trying to find good spells for tempest cleric build.

unsigned comment by Nammerduong (talk) 16:33, 25 October 2023

The tables are manual. I will switch them to automatic tables. -Sky (talk) 16:50, 25 October 2023 (CEST)Reply[reply]

Spells#Upcasting

I see some "At higher levels" sections in Spell Page are using Spells#Upcasting, but this link does not work. Should we redirect it to Upcasting? (And if so, how do we do it?) Toancaro (talk) 00:05, 6 January 2024 (CET)Reply[reply]