nil pointer in arg #1

by **Sardrimm** » Tue Oct 24, 2006 4:59 pm

When in the BGs and I kill something, I am geting the following dialog:

interface\Addons\PVPLog\PVPLog.lua:2066:Bad Argument #1 to lower (string expected, got nil)

Is there something I need to do to get rid of this error?

Thanks

by **mrmuskrat** » Tue Oct 24, 2006 5:58 pm

What version are you using? Is it a new installation or an old one that just started having this problem?

by **Sardrimm** » Wed Oct 25, 2006 4:56 am

Sorry, it is 0.6.1 that was downloaded after the post saying to re-download 0.6.1 went up.

I simply removed the folder from the interfaces folder and put the new one in. Is there something else I am supposed to do to reset anything?

by **Dreadan** » Wed Oct 25, 2006 6:00 am

Getting the same error

Error: bad argument #1 to `lower' (string expected, got nil)
File: Interface\AddOns\PvPLog\PvPLog.lua
Line: 2066
Count: 2

This is 6.1 and i didn't erased the saved variables file.

by **mrmuskrat** » Wed Oct 25, 2006 9:03 am

Interesting. Did you modify the notify kills and/or notify death from none to something else? Emptied it out perhaps?

I see that I missed that possibility.

By the way, I've picked up a Lua book.

by **Dreadan** » Wed Oct 25, 2006 10:24 am

No I don't think i did. I haven't changed anything since i installed it.

The 5 check boxes at the top of the options screen are checked and everything else is set to none

by **Sardrimm** » Wed Oct 25, 2006 3:36 pm

I have never changed any settings in the mod. I will say that this has been happening since version 0.6.0. I upgraded to 0.6.1 thinking that it would fix the problem but it is still there.

It happens when I kill someone or when I am killed.

I will try changing my options.

by **Sardrimm** » Wed Oct 25, 2006 4:50 pm

Ok, got it.

if I type /pl options or some illegal option, when it went to list the possible options it would dies with another nil pointer when trying to print the notify line.

SO I brought up the interface, changed both of the Kill Notify to raid and then back to none. Now all is fine.

thanks for the pointer of what to try.

by **mrmuskrat** » Sat Oct 28, 2006 4:36 am

Your comments will help me track this down. Thanks!

by **Atolicus** » Tue Nov 07, 2006 8:53 pm

SO I brought up the interface, changed both of the Kill Notify to raid and then back to none. Now all is fine.

I believe the problem you are running into relates to an error that existed in 0.6.0 when the channel was set to none. One of the fixes in 0.6.1 was this channel error, however when you updated to 0.6.1 your SavedVariables file still contained the old "none" channel data and was still causing the error. By switching to raid and back to none you "reset" this saved data and eliminated the error.

Anyone having this error simply needs to do as you did, change the channel to anything other than none and back.

Atolicus.