Message: Interface\FrameXML\RestrictedExecution.lua:397: Call failed: Interface\FrameXML\RestrictedExecution.lua:124: Direct table creation is not permitted
Time: 01/15/17 07:44:23
Count: 24
Stack: [C]: ?
Interface\FrameXML\RestrictedExecution.lua:397: in function <Interface\FrameXML\RestrictedExecution.lua:390>
(tail call): ?
(tail call): ?
Interface\FrameXML\SecureHandlers.lua:490: in function <Interface\FrameXML\SecureHandlers.lua:468>
[C]: in function SetAttribute’
Interface\FrameXML\SecureHandlers.lua:673: in function <Interface\FrameXML\SecureHandlers.lua:659>
(tail call): ?
Interface\AddOns\GSE\API\Storage.lua:506: in function OOCUpdateSequence’
Interface\AddOns\GSE\API\Events.lua:240: in function `?’
…nder\libs\LibInit\Ace3\AceTimer-3.0\AceTimer-3.0.lua:53: in function <…nder\libs\LibInit\Ace3\AceTimer-3.0\AceTimer-3.0.lua:48>

Locals: (*temporary) = “Call failed: Interface\FrameXML\RestrictedExecution.lua:124: Direct table creation is not permitted”

@ramseykj

I zoned into a new area was all i was doing. Riding a mount and headed to a dungeon. Zoned into Dalaran from druid class hall

Timothy, When this version of GnomeSequencer Enhanced came out I wiped out everything (i.e. wtf folder, interface, and cache) I have all my macros saved in a word document. When i put them into the newest GSE I copied and pasted them, so they don't have any loops or versions for Mythic/Raid content. I hope this information helps.

Yes it does - thank you.

Each macro has a hidden "button". When you click the macro it clicks the hidden button and the current line of your macro executes. As you can configure different versions of a macro to behave differently in some places (PVP/Mythic/Raid) when you zone it reconfigures those buttons. I was checking if you had an invalid config as while I see people reporting the problem its not one I have been able to recreate yet. So was looking for a way to do that.

I have refactored the part of the code that adds a table to the button and saved that in another way. I am concerned that there is something else happening underneath and this is hiding that problem.

Will do more testing and see how it behaves tonight.