All my mods seem to be working fine, but I'm getting this one minor error upon UI initialization:

"Error: bad argument #1 to 'strmatch' (string expected, got nil)
File: Interface\FrameXML\ChatFrame.lua
Line: 872
Count: Infinite

Has anyone else got such an error and able to find out which mod is responsible? I thought it might be ChatMod, as I don't have any other mods that deal with chat frames, but it's not ChatMod.

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
-----

* * * *

I'm getting a nil error with "strsplit", only while mounted. It's a persistent error while mounted, I cannot click it away until I dismount.

I have disabled every addon and restarted the game. Still errors when mounted.

Well, drastic measures do work. After deleting the WTF files, the error goes away. It must be one of the variables from previous mods that left some frame in a unforgivable spot.

* * * *

Ugh... well, I'll find it.

I'd rather quit playing than start completely over again.

And I'm not gonna quit playing... so, here begins the long process of editing every one of those files and finding the problem.

Nope.... I've removed:

/wow\wtf/Account/<accountname>/SavedVariables/*
/wow\wtf/Account/<accountname>/SavedVariables.lua
/wow\wtf/Account/<accountname>/SavedVariables/lua.bak
/wow\wtf/Account/<accountname>/Agalor/Daximus/*

Only things left are macros, bindings, and cache.md5

Still have the error.

Interface\FrameXML\ChatFrame.lua:1256: bad argument #2 to 'strsplit' (string expected, got nil)

Could be the Config.wtf file...

* * * *

i am having the same problem
this is the whole log from bugsack

[2007/05/22 16:56:10-683-x26114]: Interface\FrameXML\ChatFrame.lua:872: bad argument #1 to 'strmatch' (string expected, got nil):
Interface\FrameXML\ChatFrame.lua:872: in function `QueryCastSequence':
Interface\FrameXML\ChatFrame.lua:1253: in function <Interface\FrameXML\ChatFrame.lua:1229>:
Interface\FrameXML\ChatFrame.lua:1272: in function <Interface\FrameXML\ChatFrame.lua:1269>:
(tail call): ?:
Interface\FrameXML\ChatFrame.lua:1287: in function <Interface\FrameXML\ChatFrame.lua:1283>:
Interface\FrameXML\ChatFrame.lua:1299: in function `UpdateMacroFeedback':
<string>:"*:OnUpdate":10: in function <[string "*:OnUpdate"]:1>

After doing some debugging and digging around I have found the source of the problem. Looking into the source of ChatFrame.lua, line 872, is contained within a function called QueryCastSequence. The culprit line is this:

local reset, spells = strmatch(sequence, "^reset=([^%s]+)%s*(.*)");

And somehow this sequence variable is nil. No idea why, didn't dig that far. So, who cares, right? Probably nobody but the devs. However, the function name is the key, at least the name was helpful. What I have found is that if you have /castsequence macros stored globally then you will have this error on ALL your characters. If you have /castsequence macros stored for individual characters then it will be limited to just those characters with their own /castsequence macros.

I also believe, though not fully tested, that this may also only apply to macros that use the "?" icon to try to grab the button icon based on the active spell in the sequence. So, picking a concrete icon may be a workaround until they get the real problem fixed.

I do believe this is a legitimate bug, and a pretty bad one as far as I'm concerned. I can't play the game with that error dialog staring at me on the screen and I really do rely on my /castsequence macros, a lot.

If you don't need the macros, delete them, or isolate them to individual characters and your problem might be less of one. Or not...

Either way I hope they fix this very soon.

---

Q u o t e:
After doing some debugging and digging around I have found the source of the problem. Looking into the source of ChatFrame.lua, line 872, is contained within a function called QueryCastSequence. The culprit line is this:

local reset, spells = strmatch(sequence, "^reset=([^%s]+)%s*(.*)");

And somehow this sequence variable is nil. No idea why, didn't dig that far. So, who cares, right? Probably nobody but the devs. However, the function name is the key, at least the name was helpful. What I have found is that if you have /castsequence macros stored globally then you will have this error on ALL your characters. If you have /castsequence macros stored for individual characters then it will be limited to just those characters with their own /castsequence macros.

I also believe, though not fully tested, that this may also only apply to macros that use the "?" icon to try to grab the button icon based on the active spell in the sequence. So, picking a concrete icon may be a workaround until they get the real problem fixed.

I do believe this is a legitimate bug, and a pretty bad one as far as I'm concerned. I can't play the game with that error dialog staring at me on the screen and I really do rely on my /castsequence macros, a lot.

If you don't need the macros, delete them, or isolate them to individual characters and your problem might be less of one. Or not...

Either way I hope they fix this very soon.

---

download buggrabber and bugsack from wowace
files.wowace.com
it will collect all of the error and wont pop up like the default one does

and yes it's the castsequence marco
i delete all of the castsequence marco and fix the error now

---

Q u o t e:
Could be the Config.wtf file...

* * * *

---

Troodi, please stop niticing everytime I miss something :p

Removing Config.wtf makes the error go away.... only because it removes 'SET scriptErrors "1"' The error is still there.

So that's everything in WTF that applies globally, and to this specific character, except marco files... which leads us into the post above this one.

I have no /castsequence macros. I do, however, on this character, have a macro using the ? to get the spell icon, and using showtooltip. I'll be pulling out my macros now to see if that changes things. Edit when I know.

Small follow up to the issue. Doesn't matter about the icon, can be "?" or a specific icon, doesn't matter. Something is just plain wrong with /castsequence macros. My warlock is the simplest case I have, one custom macro for tossing dots.

/castsequence [exists,harm] reset=combat/target Immolate, Corruption, Curse of Agony

That throws the error. I change the marco to simply be

/cast Corruption

Click okay and the error dialog goes away. Put the macro back in and the error dialog instantly comes back. Ugh.

I already use quite a few ace addons so I'll try to use the buggrabber and what not. Hopefully it's a cosmetic thing with the error and the macro can still function. Remains to be seen.

It appears to be a cosmetic UI problem and not one that affects the game play. So... my workaround for now, until this really gets looked into and fixed would be:

1. Edit config.wtf and change 'SET scriptErrors "1"' to 'SET scriptErrors "0"'

This gets rid of the error dialog. Edit it back once this issue is resolved because those error messages can be helpful at times, obviously.

2. Set icons for macros which use /castsequence, or always just be stuck with the lovely red "?"


The macros appear to still function as they did pre-2.1. The buttons just don't look as pretty. And if you have a toolbar with a row of macros as my warrior does then I hope you are used to hotkeys because visually it won't be too easy to tell which button to click, other than the tooltip.

Good luck with that.

Update on the error while mounted....

Confirmed my problem is also with a macro:

MACRO 2 "mount" Ability_Mount_BlackDireWolf
/userandom [nomounted] Red Skeletal Warhorse, Black War Kodo
/dismount [mounted]

Throws the above mentioned "strsplit" error while mounted. Once dismounted, the error is able to be clicked away. Error is present whether mounting using the macro, or manually using the mount. Removing this macro fixes the error.

edit- "/userandom [nomounted] Red Skeletal Warhorse" gives the error. Looks like /castsequence and /userandom so far. "/use [nomounted] Red Skeletal Warhorse" works fine.

Would be nice to get a dev response to this, I think we've pretty reliably recreated it.

Shameless bump to get this some more attention. Especially since now it looks like there are 2 macro functions with this issue. Plus the mount one mixed in?

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

I reported this issue here as well:

http://forums.worldofwarcraft.com/thread.html?topicId=106001305&sid=1

I thought it might be showtooltip, but maybe its castsequence. I'm at work but I'll fire up WoW on the laptop here in a bit and see if I can figure anything more out.