Theres a small issue/bug with GnomeSequencer in regards to transfering instances (zoning to a new continent, bg, instance or raid). It basically goes like this:

I made a macrosequencer that goes like:
Click A
Click A
CLick B
Click B
Click B
Click B
Restart

When this sequence is going on inbetween instance transfers, there's a bug going on where the sequence will both continue and reset, resulting in A and B being pressed simultaneously. It's as if two sequences are going off at once. The only way to fix this is to /reload.

Suggestion: Add a checkbox that says 'Reset sequence on instance transfer' ; the same option that currently exists for in/out of combat.

Hey, thanks for the reply. I think I know what the issue is now and it's not related to GSE.

Edit: Perhaps it is an issue. If I don't use a /reload in my sequence, and i transfer instances, it gets stuck on the first line for about 5 or 6 times before fixing itself (without using /reload).

If i do type /reload, it restarts normally.

I think there is a bug with the sequence properly resetting after instance transfers. The debug gives nothing. Also it is not related to combat.

Not sure if I understand, I am never in combat this entire time. Not sure how that's related, it's purely about zoning out / zoning in.

anyways im going to bed ill read it tomorrow, thanks for helping tho :)

So I would have to check off 'reset on combat'?

I see what u are saying now. I do zone in/out frequently, often in the middle of the sequence. My goal is to have it start from the first line every time a transfer happens, without having to press the 'reset macro sequence' hotkey.

Hope my issue is a bit less vague now

I found sort of a workaround to the issue by adjusting the sequence. Cheers !

Btw my issue was related to the calibration, which in my case cannot be solved but I found a band-aid solution.