Template talk:Spell table: Difference between revisions

From bg3.wiki
Jump to navigation Jump to search
m (→‎Attack/Save column not displaying correct information: Correction to table; Grease's save is showing up in the search (at time of writing))
Line 15: Line 15:
| [[Bane (Spell)|Bane]] || Prevent condition || ''(none)'' || CHA save || "condition save" had CHA, "save" was not populated. Main info box had no indication of Save, condition info box had "Charisma saving throw".
| [[Bane (Spell)|Bane]] || Prevent condition || ''(none)'' || CHA save || "condition save" had CHA, "save" was not populated. Main info box had no indication of Save, condition info box had "Charisma saving throw".
|-
|-
| [[Grease]] || Prevent condition from terrain || ''(none)'' || DEX save || "save" had DEX, "condition" was "Prone", "condition save" had "Dexterity". Main info box had "DEX Save" under "Details:", condition info box had "Dexterity saving throw", area info box did not indicate any Save.
| [[Grease]] || Prevent condition from terrain || DEX save || DEX save || "save" had DEX, "condition" was "Prone", "condition save" had "Dexterity". Main info box had "DEX Save" under "Details:", condition info box had "Dexterity saving throw", area info box did not indicate any Save.
|-
|-
| [[Entangle]] || Prevent condition from terrain || ''(none)'' || STR save || "save" had STR, "condition" and "condition save" were not populated. Main info box had "STR Save" under "Details:".  No condition info box (area info box did not indicate any Save).
| [[Entangle]] || Prevent condition from terrain || ''(none)'' || STR save || "save" had STR, "condition" and "condition save" were not populated. Main info box had "STR Save" under "Details:".  No condition info box (area info box did not indicate any Save).

Revision as of 05:25, 11 January 2024

Attack/Save column not displaying correct information

Not sure if this would be a fix from this template or in the database, but it seems like the "Attack/Save" column does not display correctly. First, no spells or cantrips are indicated with "Attack roll" in that column, despite there being plenty of attack roll spells. Second, it seems as though only some Saves are displayed in that column. To take an example from the List of 1st level spells page - Bane is a CHA save and Charm Person is a WIS save, but only Charm Person is indicated as a save in the table. --Willach (talk) 03:49, 11 January 2024 (CET)Reply[reply]


Follow-up to this, I noticed that the corresponding pages had save info indicated differently in their Spell page template. This may impact the results of the database query for Saves. Here's some examples I found:

Spell Save effect Table save Actual Save Spell page notes
Animal Friendship Prevent condition WIS save WIS save "save" and "condition save" both had WIS. Main info box had "WIS Save" under "Details:" and condition info box had "Wisdom saving throw".
Compelled Duel Prevent condition (none) WIS save "save" had WIS, "condition save" had "Wisdom". Main info box had "WIS Save" under "Details:" and condition info box had "Wisdom saving throw".
Bane Prevent condition (none) CHA save "condition save" had CHA, "save" was not populated. Main info box had no indication of Save, condition info box had "Charisma saving throw".
Grease Prevent condition from terrain DEX save DEX save "save" had DEX, "condition" was "Prone", "condition save" had "Dexterity". Main info box had "DEX Save" under "Details:", condition info box had "Dexterity saving throw", area info box did not indicate any Save.
Entangle Prevent condition from terrain (none) STR save "save" had STR, "condition" and "condition save" were not populated. Main info box had "STR Save" under "Details:". No condition info box (area info box did not indicate any Save).
Arms of Hadar Halve damage and prevent condition STR save STR save "save" and "condition save" both had STR, "damage save" and "damage save effect" were not populated. Main info box had "STR Save" under "Details:", but no info about saves under "Damage:" (some other similar spells do). Condition info box had "Strength saving throw".
Thunderwave Halve damage and prevent knockback (none) CON save "save" had CON; "condition", "condition save", "damage save", and "damage save effect" were not populated. Main info box had "STR Save" under "Details:", but no info about saves under "Damage:" (some other similar spells do). No condition info box.
Hellish Rebuke Halve damage DEX save DEX save "damage save" had "Dexterity", "damage save effect" had "half", "save" was not populated. Main info box had no Save information under "Details:", but had "(Dexterity save to halve)" under "Damage:"
Burning Hands Halve damage (none) DEX save "save" had DEX, "damage save" and "damage save effect" were not populated. Main info box had "DEX Save" under "Details:", but no info about saves under "Damage:" (some other similar spells do).
Ice Knife Halve extra damage after attack roll (none) DEX save "save" had "DEX", "extra damage" was populated but "extra damage save" and "extra damage save effect" were not populated. Main info box had "DEX Save" under "Details:", but no info about saves under "Damage:".
Ray of Sickness Prevent condition after attack roll (none) CON save "save" and "damage save" were not populated, "condition save" had "Constitution". Main info box had no indication of Save, condition info box had "Constitution saving throw".

Apologies for the large table; I wanted to make sure I was thorough.

Given what I found above, I conclude that the Spell table search will only display the corresponding save in the following conditions:

  • Both "save" and "condition save" are populated. Both must be the three-letter abbreviation of an attribute (i.e. both must be "STR" instead of "Strength"), but seems as though the abbreviation restriction might not apply if "area" is populated?
  • If "damage" is populated, "damage save" is populated. Attribute name does not need to be abbreviated.

Now the question comes, should the database, the search template, or each spell's individual pages be updated to populate the table appropriately? --Willach (talk) 05:23, 11 January 2024 (CET)Reply[reply]