2.1 Parse error, can't figure out the source.

#2 - May 23, 2007, 7:11 a.m.

Yup, me too.

Turned on display of Lua errors to begin to debug mods/macros and this error pops up. This error shows without any mods loaded. Persists through logout, shutdown and restart. Was able to loads a few mods, one had an error pop up over this one and was able to take care of that mod's problem. This error will not clear. (Only by turning off "Show Lua errors" in the interface)

Error Frame with big red text:
-------------------------------------------------
Interface\FrameXML\ChatFrame.lua:872:
bad argument #1 to 'strmatch' (string expected, got nil)
[Okay] <------- button -- doesn't work, will not close the error frame
-------------------------------------------------

System G4 mac powerbook
OS 10.3.9
-----

* * * *

Slouken

#21 - May 23, 2007, 3:33 p.m.

Q u o t e:
I had this error too, I renamed my addons folder and it got rid of the issues. Simply disabling the mods did not, strange?

Yes, very strange. Can anyone else confirm whether or not disabling addons and/or removing the Interface folder fixes the problem?

Slouken

#23 - May 23, 2007, 4:06 p.m.

That's great, can you list the macro that shows the problem for this level 1 character?

Slouken

#30 - May 23, 2007, 5:56 p.m.

Q u o t e:
More info:

These macros dos NOT cause the problem:

/castsequence Shred, Maim
/castsequence [target=target] Shred, Maim
/castsequence [nostance:1] Shred, Maim
/castsequence [noharm] Shred, Maim
/castsequence [nostance:1,noharm] Shred, Maim

These DO:

/castsequence [stance:1] Shred, Maim
/castsequence [harm] Shred, Maim
/castsequence [target=target,harm] Shred, Maim
/castsequence [stance:1,harm] Shred, Maim
/castsequence [stance:1,noharm] Shred, Maim
/castsequence [nostance:1,harm] Shred, Maim

Great, I'm testing these out this morning. Thanks!

Slouken

#31 - May 23, 2007, 6:23 p.m.

Okay, I can reproduce this, thanks!

Slouken

#33 - May 23, 2007, 6:33 p.m.

Okay, this is fixed for 2.1.2. In the meantime, if you add a semicolon to the end of the macro, that will fix the problem.

Thanks for the great test cases!