After updating to Apex 1.3.0 and installing the luaplugin posted by Lee it appears that dcpp:setListener on "chat" no longer works. Is anyone else experiencing this problem? And is there a fix?
Thank you,
taco
LUA setListener to chat broken?
Started by tacobob, Feb 28 2010 07:53 PM
6 replies to this topic
#1
Posted 28 February 2010 - 07:53 PM
#2
Posted 28 February 2010 - 09:22 PM
tacobob, on 28 February 2010 - 07:53 PM, said:
After updating to Apex 1.3.0 and installing the luaplugin posted by Lee it appears that dcpp:setListener on "chat" no longer works. Is anyone else experiencing this problem? And is there a fix?
Thank you,
taco
Thank you,
taco
It doesn't work at all, or triggers an error?
#3
Posted 28 February 2010 - 11:52 PM
Crise, on 28 February 2010 - 09:22 PM, said:
It doesn't work at all, or triggers an error?
Does not work at all. No error it just doesn't do anything. Pms still work fine but chat does nothing. I thought it might have been something wrong with my previously working script so I tried the bier script included with the older versions of the plugin and that did not work, no error, just didn't work.
Thanks,
taco
edit1: I should also indicated that I'm using the x86 versions of apex and lua plugin.
edit2: I installed the x64 versions of both and still experiencing the same issue.
#4
Posted 01 March 2010 - 11:35 AM
tacobob, on 28 February 2010 - 11:52 PM, said:
Does not work at all. No error it just doesn't do anything. Pms still work fine but chat does nothing. I thought it might have been something wrong with my previously working script so I tried the bier script included with the older versions of the plugin and that did not work, no error, just didn't work.
Thanks,
taco
edit1: I should also indicated that I'm using the x86 versions of apex and lua plugin.
edit2: I installed the x64 versions of both and still experiencing the same issue.
Thanks,
taco
edit1: I should also indicated that I'm using the x86 versions of apex and lua plugin.
edit2: I installed the x64 versions of both and still experiencing the same issue.
It seems this was caused by another stupid mistake on my side... oh well 1.3.1 will resolve it.
#7
Posted 11 January 2012 - 06:04 PM
Works on my version just fine
.
1 user(s) are reading this topic
0 members, 1 guests, 0 anonymous users


