Missing command: setbncuser USER sysnotices not a valid command?

Bug #783009 reported by Ze0de
This bug affects 1 person
Affects Status Importance Assigned to Milestone

Bug Description

It appears a command has been missed from the list of available commands when using "setbncuser USER...."

/sbnc set sysnotices on|off works fine from your client, however it is not available via the internal/tcl commands "setbncuser/getbncuser USER sysnotices"

This also has implications for the sbnciface where System Notices can not be turned on/off via the iface, since "setvalue/getvalue sysnotices" will not function.

Error msg in both cases:

[14:26] --sBNC- An error occured in the tcl script:
[14:26] --sBNC- RuntimeError Type should be one of: server port serverpass client clientcount realname nick awaynick away awaymessage uptime lock admin hasserver hasclient vhost channels tag delayjoin seen quitasaway automodes dropmodes suspendreason ssl sslclient realserver ident tags localip lean memory memorylimit channelsort sessions autobacklog

Revision history for this message
Ze0de (i-admin-my-bnc-net) wrote :

Forgot to say, sBNC 1.3 beta 5 by the way.

Revision history for this message
Gunnar Beutner (gunnarbeutner) wrote :

Fixed in git commit 0af2be0e68b842fe7465782499a3596416874149.

Changed in shroudbnc:
status: New → Fix Committed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers