Thomas Sader
Thomas Sader
It is possible that #1115 fixed this. Someone just needs to test it with the tpool command
why is this useful? aren't those putlog lines limited anyway?
It still has side-effects I have seen in the past, e.g. raw console log being mangled. It might be warranted to always give the bind handler a copy of this...
ctcp.mod automatically attempts to figure out the address to respond with after /ctcp bot chat. It sends `DCC CHAT ` to make the user connect to itself. In the example...
Broken by https://github.com/eggheads/eggdrop/pull/1162
Could maybe also warn if it starts with a literal '{'?
``` Note: Be aware that the syntax for setting the need- settings is different between Tcl's [channel set] and the dcc .chanset command. .chanset #chan need-op putmsg NickServ "op #chan"...
We should use the return value of the Tcl proc to deny the change as invalid. That could be in a new PR, but it is one of the main...
I agree with this. Those paths should be in config.h defines then instead of in the config (at least their defaults). To address compatibility (because we have 20 year old...
Chanset binds would be useful, especially for custom int/string settings where you could apply validity checking and reject the change if it's not a valid value. If this is only...