Talk:Spellburst

Preface

I'm having my first experience with spell burst in Nelemar with my capped paladin so I figured I'd post my observations on here. I will train skills to incrementally increase wearable mana and track my ability to avoid spell burst while adding spells. Any discrepancies in wearable mana totals is caused by the value of skill bonus enhancives changing as the underlying skill increases in rank.

Using the Gib's wiki calculation I currently have wearable mana of 66.44. My current burst-free set is 406, 414, 506, 508, 509, 601 and 202. Referring to Gib's modifiers I count each elemental spell as costing an additional 0.5 mana, each spell of level nine or over as costing an additional 0.5 mana and each spell identified by Gib as causing unique problems as costing an additional 0.5 mana. Using those modifiers I calculate values of 6.5, 15, 6.5, 8.5, 10.5, 1 and 2 for each spell in my burst-free set totaling 50 mana.

Baseline

406, 414, 506, 508, 509, 601, 202 = 50 mana.

66.44 wearable mana total.

Replacing 601 with 401 does not result in spell burst. (+0.5 mana)

Replacing 202 and 601 with 503 does not result in spell burst. (+0.5 mana)

Replacing 406 with 507 results in spell burst. (+1 mana)

Replacing 506 with 507 results in spell burst. (+1 mana)

Adding 401 results in spell burst. (+1.5 mana)

Replacing 202 with 503 results in spell burst. (+1.5 mana)

Testing - Wiki Formula

First eight tests increased wearable mana in increments of 1.1 and resulted in no change in burst point.

Test nine - 77.11 wearable mana total.

Replacing 506 with 507 does not result in spell burst. (+1 mana)

Replacing 406 with 507 does not result in spell burst. (+1 mana)

Adding 401 does not result in spell burst. (+1.5 mana ???)

Replacing 202 with 503 does not result in spell burst. (+1.5 mana ???)

Adding 401 and replacing 202 with 402 does not result in spell burst. (+2 mana ???)

Replacing 601 with 503 does not result in spell burst. (+2.5 mana ???)

Replacing 601 with 503 and replacing 202 with 402 does not result in spell burst. (+3 mana ???)

Adding 503 does not result in spell burst (+3.5 mana ???)

Adding 503 and replacing 202 with 402 does not result in spell burst. (+4 mana ???)

Adding 503 and replacing 506 with 507 does not result in spell burst. (+4.5 mana ???)

Adding 503 and 401 does not result in spell burst. (+5 mana ???)

Adding 905 does not result in spell burst. (+5.5 mana ???)

Adding 503 and 401 and replacing 202 with 402 does not result in spell burst. (+5.5 mana ???)

Adding 503 and 401 and replacing 506 with 507 does not result in spell burst. (+6 mana ???)

Adding 905 and replacing 506 with 507 does not result in spell burst. (+6.5 mana ???)

...

Adding 905 and 401 and 507 does not result in spell burst. (+14.5 mana ???)

Adding 401 and 503 and 905 and 911 does not result in spell burst. (+23 mana !!!)

Interlude

In light of my review of ;burst_calc and Gib's PC thread dealing with it, I am switching to tracking ;burst_calc current mana against the ;burst_calc mana limit mana. To get a more precise measurement I added one rank of lore which (conveniently) brought me from 61 to 61.5 ;burst_calc limit mana. In so doing I happened to notice that ;burst_calc does not factor in enhancive bonuses. Adding one rank of lore with my enhancives on took me to 61.5 but removing an enhancive that gave two ranks had no effect.

In the interests of making this a bit easier to read, let us now assume that my base spell set is:

202, 401, 406, 414, 503, 507, 508, 509, 601 and 911

Testing - ;burst_calc

Adding 401 and 503 and 507 and 911 does not result in spell burst. (67.5 ;burst_calc current mana)

Adding 401 and 503 and 507 and 712 does not result in spell burst. (68.5 ;burst_calc current mana)

Adding 401 and 507 and 905 and 911 does not result in spell burst. (69.5 ;burst_calc current mana)

Adding 401 and 507 and 905 and 712 results in spell burst.

Adding 503 and 507 and 905 and 911

Adding 401 and 503 and 507 and 905 and 911 results in spell burst. (72.5 ;burst_calc current mana)

MICHN18 (talk) 15:04, 5 January 2016 (CST)