Difference between revisions of "Talk:Perk"
→Take Precedence?
imported>Egocarib |
imported>Lofgren |
||
| Line 6: | Line 6: | ||
"Priority: Used to control order of operations when two perk entries affect the same value. Perks with a higher priority take precedence." Does this mean lower priority entries do not occur or that higher priority entries occur/modify values and then the lower priority occurs/modifies and so on? Also, does same value refer to the same entry point or must the function (multiply, add, set) need to be the same as well? --[[User:Syneris|Syneris]] 00:29, 12 February 2012 (EST) | "Priority: Used to control order of operations when two perk entries affect the same value. Perks with a higher priority take precedence." Does this mean lower priority entries do not occur or that higher priority entries occur/modify values and then the lower priority occurs/modifies and so on? Also, does same value refer to the same entry point or must the function (multiply, add, set) need to be the same as well? --[[User:Syneris|Syneris]] 00:29, 12 February 2012 (EST) | ||
:I agree that this language should be changed. "Takes precedence" makes sense when you are talking about situation like that combat his spell example below, but if one perk multiplies a value and another perk adds to it neither of them are really "taking precedence." In this case they are just being executed in a certain order. [[User:Lofgren|Lofgren]] ([[User talk:Lofgren|talk]]) 2013-11-01T00:19:56 (EDT) | |||
:Priority seems to work on global level and not just on perk in question. For example only one "Apply Combat Hit Spell" entry point can work at one time - you can't apply two spells at same time in one hit and thats where priority must be used. Check Limbsplitter perk and you will see that priorities are given from 3 to 10 leaving priorities from 0 to 2 to be used by other perks like Warmaster (lower priority will always take precedence). I don't know for which entry points priority must be used, it need to be tested. [[User:Mitchalek|Mitchalek]] 07:38, 12 February 2012 (EST) | :Priority seems to work on global level and not just on perk in question. For example only one "Apply Combat Hit Spell" entry point can work at one time - you can't apply two spells at same time in one hit and thats where priority must be used. Check Limbsplitter perk and you will see that priorities are given from 3 to 10 leaving priorities from 0 to 2 to be used by other perks like Warmaster (lower priority will always take precedence). I don't know for which entry points priority must be used, it need to be tested. [[User:Mitchalek|Mitchalek]] 07:38, 12 February 2012 (EST) | ||
::I've tested this with 2 perks using the Mod Spell Cost entry point. I modified the vanilla Flames spell so its cost was 100 (for easier maths :P) then made a copy of the Novice Destruction perk (multiplier of 0.5) and changed the multiplier to 1.5. With both of these perks active the cost of Flames was 75 (with no enchantment/potion bonuses and a destruction skill of 0). In this case priority doesn't seem to matter as the entry point multipliers seem to get compounded. 1.5 x 0.5 = .75<br> | ::I've tested this with 2 perks using the Mod Spell Cost entry point. I modified the vanilla Flames spell so its cost was 100 (for easier maths :P) then made a copy of the Novice Destruction perk (multiplier of 0.5) and changed the multiplier to 1.5. With both of these perks active the cost of Flames was 75 (with no enchantment/potion bonuses and a destruction skill of 0). In this case priority doesn't seem to matter as the entry point multipliers seem to get compounded. 1.5 x 0.5 = .75<br> | ||