If I am on #channel1 and #channel2 and /me to them both /ctcp #channel1,#channel2 ACTION waves, ZNC creates new directory ~/.znc/moddata/log/mikaela/#channel1,#channel2 instead of storing the logs into both #channel1 and #channel2. Sending normal messages to multiple targets works correctly.
If I am on #channel1 and #channel2 and /me to them both `/ctcp #channel1,#channel2 ACTION waves`, ZNC creates new directory `~/.znc/moddata/log/mikaela/#channel1,#channel2` instead of storing the logs into both `#channel1` and `#channel2`. Sending normal messages to multiple targets works correctly.
<!-- github-sync-id:44236091 -->
mkaysi@lakka ~/.znc/moddata/log/mikaela/freenode/##mikaela,#znc
% cat 2014-09-28.log
[20:40:38] * Mikaela also notes that the multi-target ctcp actions appear as normal /me's in those weird directories.
example:
```
mkaysi@lakka ~/.znc/moddata/log/mikaela/freenode/##mikaela,#znc
% cat 2014-09-28.log
[20:40:38] * Mikaela also notes that the multi-target ctcp actions appear as normal /me's in those weird directories.
```
<!-- github-comment-id:57093258 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
If I am on #channel1 and #channel2 and /me to them both
/ctcp #channel1,#channel2 ACTION waves, ZNC creates new directory~/.znc/moddata/log/mikaela/#channel1,#channel2instead of storing the logs into both#channel1and#channel2. Sending normal messages to multiple targets works correctly.example: