Have they changed how SendChatMessage works?

[Coote]

Currently on live

SendChatMessage(msg[random(trash)], "SAY", NIL)

works perfectly fine, but on the beta servers, I'm getting errors.

Message: Interface\AddOns\AfterKill\AfterKill.lua:29: attempt to index global 'msg' (a nil value)
Time: 06/30/12 06:05:18
Count: 1
Stack: Interface\AddOns\AfterKill\AfterKill.lua:29: in function <Interface\AddOns\AfterKill\AfterKill.lua:27>

That particular line of code is the only one that's throwing errors. I've tested with that line removed, and everything else works perfectly. I've tried looking and seeing what changed, but finding nothing. Undocumented change, or just me being noobier than usual?

[Xrystal]

One thing to do is find out where your msg table is set as it thinks it is null at present

It doesn't look like SendChatMessage function itself has changed.
SendChatMessage(msg, "WHISPER", editBox.languageID, lastTell);
Is an example of what is in the latest beta version of ChatFrame.lua

[Coote]

Thanks. I fixed it by changing up my table a bit, and the message.

Going from

local trash = {
	"test 1",
	"test 2",
	"test 3",
}

SendChatMessage(msg[random(trash)], "SAY", NIL)

to

local trash = {
	[1] = "test 1",
	[2] = "test 2",
	[3] = "test 3",
}

SendChatMessage(trash[random(1,3)], "SAY", NIL)

fixed it up.

[Lombra]

The table is identical to what you had before, however you're now actually referring to that table and not some other, non existant one. You were also trying to pass the table as an argument to random, rather than its length.

This should work:

local trash = {
	"test 1",
	"test 2",
	"test 3",
}

SendChatMessage(trash[random(#trash)], "SAY")

(also, no need to explicitly pass nil since it's the last argument)

[Seerah]

For future reference, if the function were changed, the error message would say that you were using it incorrectly. (for example "TipTop-2.9.4\\tiptop-2.9.4.lua:409: Usage: GetSpecializationInfo(specIndex[, isInspect[, isPet]]])")

Your error was just saying that the argument you passed to the function was nil and it couldn't do anything with it. This could be from typos, clearing the variable, scope issues, etc.