I've been playing around with making new skills, trees and classes but Thunderstorm has me confused-- I was using it as a baseline to modify in a custom tree when I noticed that it fails to work. The rest of the tree isn't at fault since everything else is working fine.
Currently, it's exactly the same, with the exception of the name/type/require fields. Upon activation, it reserves the sustain, begins the manadrain and activation text. Deactivation seems to work fine as well. This leads me to believe that my problem resides somewhere between lines 23 and 40 (of the talent), but I don't see anything there that would cause it to fail just by moving it.
Can anybody offer some insight here?
Why's Thunderstorm breaking in a custom tree? [Resolved]
Moderator: Moderator
Why's Thunderstorm breaking in a custom tree? [Resolved]
Last edited by Aoi on Wed Jan 05, 2011 12:06 am, edited 1 time in total.
Re: Why's Thunderstorm breaking in a custom tree?
Thunderstorm and talents like it need to be called someplace to actually do anything. In other words, there's no trigger for thunderstorm in the thunderstorm talent.
For Corona the trigger is in the spellcrit stuff for combat (because it goes off every time you crit).
For Hymn of Moonlight, Body of Fire, and Thunderstorm this is in Actor (starting at line 246).
I'm guessing you need something like this.
Note that you'll want to replace all those names and replace t.do_coolstuff(self, t) with something appropriate.
Also you'll want to change the do_storm function name (in your thunderstorm function) to t.do_coolstuff (or whatever you decide to call it).
If that's not the issue then I'm not sure what else it could be. If it's tossing out an error in stdout that could give us more clues.
For Corona the trigger is in the spellcrit stuff for combat (because it goes off every time you crit).
For Hymn of Moonlight, Body of Fire, and Thunderstorm this is in Actor (starting at line 246).
I'm guessing you need something like this.
Code: Select all
if self:isTalentActive(self.T_AOISCOOLTALENT) then
local t = self:getTalentFromId(self.T_AOISCOOLTALENT)
t.do_coolstuff(self, t)
end
Also you'll want to change the do_storm function name (in your thunderstorm function) to t.do_coolstuff (or whatever you decide to call it).
If that's not the issue then I'm not sure what else it could be. If it's tossing out an error in stdout that could give us more clues.
Re: Why's Thunderstorm breaking in a custom tree?
Ahhhh... that indeed was it. Thank you!