Ver 1.3.2 Causing Error
Comicus opened this issue · 8 comments
Going to previous version for now...
Getting this error ;
10x GS-Core\startup.lua:351: Usage: CreateMacro(name, iconFileName, body, perCharacter)
[C]: in function CreateMacro' GS-Core\startup.lua:351: in function
GSregisterSequence'
GS-Core\startup.lua:367: in function `GSCheckMacroCreated'
GS-Core\Core.lua:305: in function <GS-Core\Core.lua:235>
Locals:
(_temporary) = "DB_KTN_MouseOver"
(_temporary) = nil
(_temporary) = "#showtooltip
/click DB_KTN_MouseOver"
(_temporary) = 1
I'm having an issue with this version also. when logging in with my mage I'm getting the following error.
{see attached GS-Core.!BugGrabber.zip file}
The gest of it is that the spec id {#64} is wrong.
On a side note {and not really an error} when doing /gs showspec, I'm only getting the Spec ID, where before I would get both the spec id (say 63 for Fire Mage) and Class id ( say 2 for Mage)
Keep up the great work, I love where you have taken GS.
Thanks for this. I will look into it as I level Legion. I will have a patch out in a day it so.
TimothyLuke
On 31 Aug 2016, at 12:38 AM, jfvandenbosch [email protected] wrote:
I'm having an issue with this version also. when logging in with my mage I'm getting the following error.
{see attached BugGrabber.lua.zip file
GS-Core.!BugGrabber.zip
}The gest of it is that the spec id {#64} is wrong.
On a side note {and not really an error} when doing /gs showspec, I'm only getting the Spec ID, where before I would get both the spec id (say 63 for Fire Mage) and Class id ( say 2 for Mage)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
@Comicus I cant replicate the problem you are describing. If i open as a priest and look at that sequence it works as per normal
@jfvandenbosch I have forced specID to be converted to a number.
@camelot10 found the same error that was originally reported but I cannot replicate the problem. Is there anymore information apart from the stack trace?
@jfvandenbosch The problem is in your sequence.
Your sequence should read specID=64, not specID="64",
Fixed the showspec part in #70