Macros for class not showing
fireymerlin opened this issue · 4 comments
Version: GS 2.0.9
I have "Show All Macros in Editor" unchecked.
I only see one sample macro: SAM_KTN_MouseOver.
That is for a priest.
I'm seeing that one macro and only that one, for all my classes.
If I check "Show All Macros in Editor", exit the editor, open the editor, uncheck the box, exit the editor, open the editor, I see my class macros.
I'm also seeing "SAM_KTN_MouseOver" on all my classes in additional to the correct ones.
In summary, 2 problems:
- Class macros are not showing unless I display all class macros first.
- SAM_KTN_MouseOver is showing for all classes that I've tested.
Hi Fireymerlin
Was this from a fresh install of GSE 2.0.9?
If it's not could you please run the /gs movelostmacros command added in 2.0.4 via #187
The duplicate KTN's may need to be manually deleted.
TimothyLuke
… On 19 Jan 2017, at 2:31 am, fireymerlin ***@***.***> wrote:
Version: GS 2.0.9
I have "Show All Macros in Editor" unchecked.
I only see one sample macro: SAM_KTN_MouseOver.
That is for a priest.
I'm seeing that one macro and only that one, for all my classes.
If I check "Show All Macros in Editor", exit the editor, open the editor, uncheck the box, exit the editor, open the editor, I see my class macros.
I'm also seeing "SAM_KTN_MouseOver" on all my classes in additional to the correct ones.
In summary, 2 problems:
Class macros are not showing unless I display all class macros first.
SAM_KTN_MouseOver is showing for all classes that I've tested.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Does the Export/Import function work? If it does, I'll export the macros I created and start with a fresh install of GS.
Yes they do
TimothyLuke
… On 20 Jan 2017, at 11:11 pm, fireymerlin ***@***.***> wrote:
Does the Export/Import function work? If it does, I'll export the macros I created and start with a fresh install of GS.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.