could use same trigger for cast and effect recognition, and differentiate from there
in Conditions, no need to set values to locals, just use them in the create function call
why force the spell hotkey when stopping the cast?
i also thinks its silly to require xe and xedamage when all you are using it for is to deal damage
you should really avoid all fancy maths when uneeded. for instance, you always calcualte distance, even if the spell is over, the target is dead, or its past the damage interval
on top of that, you could remove the SquareRoot call by comparing to a squared break point
what happened to uplaoding two seperate versions?
lastly using T32 for this is silly, as you aren't doing damage all that often - as such, its much less efficient as a by product
sorry I can't approve this right now, not because of the menial change suggestions, as there are bigger, more tangible problems that exist
It'll be good practice at least, I did a bunch of practice boards the last few weeks but that's a bit different than actual repair. It's pretty obvious what's going on with those, so it's not very hard to trace the leads, and they aren't designed with faults so
Site is peaking on traffic for the recipes - Sundays are always the big days and we are 200 plus unique visitors an hour right now and it will be like that probably be around 3000 total on the site all day maybe more if Google desires it LOL
Anyway I have a power bench that I don't actually know how to use, but I'm assuming I can take the battery out and power it directly from that to see if any of them turn on.
If you had kids like me that grew up in that era you could just go to your closet and fish out one of the cords from the cord bag. I bet I have everyone of those cord connectors plus some