the ACTION may be in a privmsg to a channel or direct. Currently, the event does not inform you which this is.
The fix is simple; on line 469 of libircclient.c, the target param is being clobbered.
Attaching suggested fix. Note that this fix does break backward compatibility to anyone relying on the previous functionality; however it is likely that anyone using the library will have patched it as not being able to determine the target of an action is most likely a problem for most consumers of this library.
Log in to post a comment.