Post by Moongaze on May 13, 2008 13:06:35 GMT -5
Got WOW 2.4.2? You MUST upgrade LS to version 707 or greater or you will not be able to use LunarSphere. Version 707 is now live and will fix your issue if you still have the older version. If you've been holding off on updating LS for whatever reason, now's the time to update.
ONE line of code is the problem line and it has a horrible cascading effect that essentially disables 1/6th of LunarSphere, but since most of LunarSphere relies on SOMETHING from that 1/6, the whole thing breaks.
This type of breaking is not common and doesn't happen much, since Blizzard rarely removes stuff that we normally would use. Sadly, this affects all users of LS, all the way back to version ... 300-400 I think. It's an old part of LS
For those who are interested in why it broke, the answer is simple:
In Blizzard's GlobalStrings.lua file that is inside their game file database, there were two lines that I used to determine if items had charges. These two lines set up variables called:
ITEM_SPELL_CHARGES
ITEM_SPELL_CHARGES_P1
Well, one is for plural "charges" and one is for "charge" ... and I looked for the plural version which was the ITEM_SPELL_CHARGES_P1 variable. Well, Blizzard decided to combine the two and there is now just:
ITEM_SPELL_CHARGES
So, when I try to perform some string manipulation on ITEM_SPELL_CHARGES_P1, which doesn't exist, LunarSphere complains and stops dead turkey, thus preventing it from running. I'm a little embarassed by that error, but it happens =(
So, I just look for ITEM_SPELL_CHARGES now and it will take care of the singular and plural form of the word "charge."
ONE line of code is the problem line and it has a horrible cascading effect that essentially disables 1/6th of LunarSphere, but since most of LunarSphere relies on SOMETHING from that 1/6, the whole thing breaks.
This type of breaking is not common and doesn't happen much, since Blizzard rarely removes stuff that we normally would use. Sadly, this affects all users of LS, all the way back to version ... 300-400 I think. It's an old part of LS
For those who are interested in why it broke, the answer is simple:
In Blizzard's GlobalStrings.lua file that is inside their game file database, there were two lines that I used to determine if items had charges. These two lines set up variables called:
ITEM_SPELL_CHARGES
ITEM_SPELL_CHARGES_P1
Well, one is for plural "charges" and one is for "charge" ... and I looked for the plural version which was the ITEM_SPELL_CHARGES_P1 variable. Well, Blizzard decided to combine the two and there is now just:
ITEM_SPELL_CHARGES
So, when I try to perform some string manipulation on ITEM_SPELL_CHARGES_P1, which doesn't exist, LunarSphere complains and stops dead turkey, thus preventing it from running. I'm a little embarassed by that error, but it happens =(
So, I just look for ITEM_SPELL_CHARGES now and it will take care of the singular and plural form of the word "charge."