Hay, the crypt module is show the worng mode in IRC
Insted of show
[2017-03-27] [21:11:51] »» [@foo] random massage
[2017-03-27] [21:18:47] »» [+bar] random massage
It shows
[2017-03-27] [21:11:51] »» [*foo] random massage
[2017-03-27] [21:18:47] »» [*bar] random massage
So every mode is replaced whit *, this will be a problem if you run lets say an eggdrop for an example as it won´t found the nickname when its has * in start of the nick.
The problem seems to be confirmed about someone that know how to read the code here
[2017-03-27] [01:45:54] »» [genius3000] Whiskey: I don't use the crypt module nor do I show STATUS characters with the nickname in my client, but by looking at the source of the crypt module...it shows a nickname as NickPrefix + Nick, where NickPrefix is set via the module (check ListKeys for current) and defaults to '*'.
[2017-03-27] [01:49:05] »» [genius3000] My take on the code would mean that it purposely shows a custom (to the crypt module) Prefix character instead of the actual one. I do not know why, I can presume it does this to show that it was a message filtered (decrypted) through crypt....
Hay, the crypt module is show the worng mode in IRC
```
Insted of show
[2017-03-27] [21:11:51] »» [@foo] random massage
[2017-03-27] [21:18:47] »» [+bar] random massage
```
```
It shows
[2017-03-27] [21:11:51] »» [*foo] random massage
[2017-03-27] [21:18:47] »» [*bar] random massage
```
So every mode is replaced whit *, this will be a problem if you run lets say an eggdrop for an example as it won´t found the nickname when its has * in start of the nick.
The problem seems to be confirmed about someone that know how to read the code here
```
[2017-03-27] [01:45:54] »» [genius3000] Whiskey: I don't use the crypt module nor do I show STATUS characters with the nickname in my client, but by looking at the source of the crypt module...it shows a nickname as NickPrefix + Nick, where NickPrefix is set via the module (check ListKeys for current) and defaults to '*'.
[2017-03-27] [01:49:05] »» [genius3000] My take on the code would mean that it purposely shows a custom (to the crypt module) Prefix character instead of the actual one. I do not know why, I can presume it does this to show that it was a message filtered (decrypted) through crypt....
```
<!-- github-sync-id:217351754 -->
Disable it then, dependant on which version of ZNC you're on, this is done by either:
SetKey [nick-prefix] :
SetKey @nick-prefix@ :
SetNickPrefix
Disable it then, dependant on which version of ZNC you're on, this is done by either:
- SetKey [nick-prefix] :
- SetKey @nick-prefix@ :
- SetNickPrefix
<!-- github-comment-id:289589652 -->
I use ZNC 1.6.3 and latest version of crypt module, as i copy the latest one yesterday from the github to test if that would reslove the problem
But this one is set whit "SetKey #channel <key>"
You can´t mean i have to set it for every single nickanme in the channel?
The * come from the channel chat, and i don´t get the point whit nick-prefix is there anyway to get "user/+voice/@op/~founder"
I use ZNC 1.6.3 and latest version of crypt module, as i copy the latest one yesterday from the github to test if that would reslove the problem
But this one is set whit "SetKey #channel \<key\>"
You can´t mean i have to set it for every single nickanme in the channel?
The * come from the channel chat, and i don´t get the point whit nick-prefix is there anyway to get "user/+voice/@op/~founder"
<!-- github-comment-id:289594083 -->
No, I literally mean it as I wrote it down, but as you're using 1.6.3 I'll narrow it down: /msg *crypt SetKey [nick-prefix] :
I recommend using 1.7.* though as it has, amongst others, an updated Crypt module with dedicated SetNickPrefix/GetNickPrefix commands and addition of KeyX command for use with CBC in PM's.
No, I literally mean it as I wrote it down, but as you're using 1.6.3 I'll narrow it down:
`/msg *crypt SetKey [nick-prefix] :`
I recommend using 1.7.* though as it has, amongst others, an updated Crypt module with dedicated SetNickPrefix/GetNickPrefix commands and addition of KeyX command for use with CBC in PM's.
<!-- github-comment-id:289600451 -->
As genius3000 explained to you, this has nothing to do with modes. Read again what he told you.
I use ZNC 1.6.3 and latest version of crypt module, as i copy the latest one yesterday from the github to test if that would reslove the problem
Modules are not guaranteed to be compatible with older ZNC versions. It works only the other way around.
> So every mode is replaced whit *
As genius3000 explained to you, this has nothing to do with modes. Read again what he told you.
> I use ZNC 1.6.3 and latest version of crypt module, as i copy the latest one yesterday from the github to test if that would reslove the problem
Modules are not guaranteed to be compatible with older ZNC versions. It works only the other way around.
<!-- github-comment-id:289610476 -->
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.
Hay, the crypt module is show the worng mode in IRC
So every mode is replaced whit *, this will be a problem if you run lets say an eggdrop for an example as it won´t found the nickname when its has * in start of the nick.
The problem seems to be confirmed about someone that know how to read the code here
Disable it then, dependant on which version of ZNC you're on, this is done by either:
I use ZNC 1.6.3 and latest version of crypt module, as i copy the latest one yesterday from the github to test if that would reslove the problem
But this one is set whit "SetKey #channel <key>"
You can´t mean i have to set it for every single nickanme in the channel?
The * come from the channel chat, and i don´t get the point whit nick-prefix is there anyway to get "user/+voice/@op/~founder"
No, I literally mean it as I wrote it down, but as you're using 1.6.3 I'll narrow it down:
/msg *crypt SetKey [nick-prefix] :I recommend using 1.7.* though as it has, amongst others, an updated Crypt module with dedicated SetNickPrefix/GetNickPrefix commands and addition of KeyX command for use with CBC in PM's.
As genius3000 explained to you, this has nothing to do with modes. Read again what he told you.
Modules are not guaranteed to be compatible with older ZNC versions. It works only the other way around.