Page History

Caster level when applied to the spell. However GetEffectCasterLevel ignores it (thus dispel checks are whacky).

Classes usually only go up to 40 for spellcasters, but you might be able to do a higher value up to 60 or more if you test it properly.

0.5 for cantrips

1 - 9 for spells

Curiously it seems the game ignores this and uses the Innate level in spells.2da instead for things like save DCs/spell immunity by level, although mostly this column follows spells.2da innate column anyway so you'd never usually notice.

Probably needs some more testing however and may affect price? and possibly Toolset generated items. Best to make it a mirror of the Innate column in spells.2da. ///Note: seems like this column was just added to easily calculate Cost column, see formula below. - Aleist3r

Cost value to use for this item property. See itemprops.2da, itempropdef.2da, iprp_costtable.2da and iprp_paramtable.2da for more information on cost calculations. Fun times with uses/day, charges/use, single use and unlimited use multipliers.

Most lines use PnP formula for wand price: CasterLvl * InnateLvl * 750. Some of OC spells have different values instead 750, my only guess is, it was changed during development to reduce prices of some potions. Or, had their Caster Level adjusted later without changing Cost column. Then, there are lines added in SoU (lines 345 - 424) and those have no consistency whatsoever, they look like either some happy accident or had CasterLvl column adjusted after calculating cost. HotU lines seems mostly consistent with formula barring lines with values set to either 20k or 40k, or where Innate Level = 1 and Caster Level = 6 (those lines clearly had their CLvl adjusted). For lines 511+ it just looks like existing lines were copied and had their Caster level changed without recalculating cost. Item-specific properties have their own prices, but so do epic spells (there is clearly a pattern here but does not seem like there is any consistency in formulas actually, looks like epic spells are calculated as 17 * 9 * 750 = 114750 then +100k if CasterLvl = 25 or +200k of CasterLvl = 30 ).

1 allowed on Potions

0 not allowed on Potions

These are only for toolset usage. It won't affect Item Property script functions or GFF edited items.

If 1 it can be added to potions, if 0 it cannot.

Generally friendly only spells get this set to 1.

Potions are base items line 54.

Note potions have the special property of not having more than one "use" ever, by default, so only one spell can be applied to them.

1 allowed on Wands

0 not allowed on Wands

These are only for toolset usage. It won't affect Item Property script functions or GFF edited items.

If 1 it can be added to potionswands, if 0 it cannot.

Seems to be no rhyme or reason what gets this set as 1. Randomly summon, friendly and hostile spells are all 1 or 0. Actually, seems like PnP rule was used here, that is, non-epic wands can store up to 4th level spells. (There are some exceptions from this rule: lines 146, 190, 191, 322, 324, 325, 326, 328, 469-474, 477, 479-481, 483, 484, 511, 512, 514-520 and item-specific properties. Interestingly enough, grenade properties can be added to wands but that's likely a bug.)

Wands are base items line 46.

1 allowed on items that are not Potions or Wands

0 not allowed on items that are not Potions or Wands

These are only for toolset usage. It won't affect Item Property script functions or GFF edited items.

If the wand and potion usage columns are 0 this should be set to 1.

If 1 it can be added to items which are not line 54 or 46, 0 if it cannot be.