DataManager.GetSpellData(Spell).Range

[Endus]

Does this work for anyone else or am I just using it wrong?

This is what I'm putting into the console:

var range =  (int)DataManager.GetSpellData("Spell Name").Range;

Log(range);

I'm getting all sorts of numbers from it, and the majority of them are wrong. Paladin's Fast Blade returns 3 (correct), but then Paladin's Savage Blade returns 255 (incorrect). It seems like most of the Black Mage and White Mage spells are correct (25 and 30), but then I couldn't find a single Warrior spell that was correct (255 for the ones I checked). Same goes for every Rogue spell I try (255, incorrect).

Am I using it wrong or does mastahg need to take a look at it?

 

[kaihaider]

until mastahg enlightens us, we can workaround it with

SpellRangeCheck ck = Actionmanager.InSpellInRangeLOS(spell, o);
ck == SpellRangeCheck.ErrorNotInRange

 

[Wheredidigo]

until mastahg enlightens us, we can workaround it with

SpellRangeCheck ck = Actionmanager.InSpellInRangeLOS(spell, o);
ck == SpellRangeCheck.ErrorNotInRange

That is not an equivalent workaround for getting the Range of a spell. We need Mastahg to fix his own shit. He's the one that has pointed me to using DataManager to get this kind of information. Kind of typical that half of it works and half of it doesn't.

 

[kaihaider]

That is not an equivalent workaround for getting the Range of a spell. We need Mastahg to fix his own shit. He's the one that has pointed me to using DataManager to get this kind of information. Kind of typical that half of it works and half of it doesn't.

for what logic would you need to know spell range and can't jerry rig around SpellrangeCheck?

I seriously would like to know.

btw, I think he just didn't notice it broke in an update...

Mastahg may be the rebornbuddy community's god but he's not an actual god...

 

[mastahg]

Looks like they now do some funky logic for melee abilities. cheap and ez fix, anything that returns 255 should return 3