View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0005054 | unreal | documentation | public | 2018-01-10 14:22 | 2018-03-25 13:40 |
| Reporter | acidvegas | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | always |
| Status | new | Resolution | open | ||
| Summary | 0005054: Documentation Errors / Minor Issues | ||||
| Description | With the "extbans/msgbypass" module, "filter" is actually "censor", but written on the forum/wiki as "filter": https://forums.unrealircd.org/viewtopic.php?f=1&t=8775 https://www.unrealircd.org/docs/Extended_Bans Under the "Class Block" section in https://www.unrealircd.org/docs/Class_block you have "nofakelag;" listed standalone, which is not right, it can only be options { nofakelag; };, I also think that this should be, by default configurable and users should not have to edit the source, as a recompile is required. If it is disabled by default and can only be abled by adding the line to the class block, what harm is done? Under the https://www.unrealircd.org/docs/Configuration#Configuration_file_syntax section you have: hosts { admin "admin.mynet.org"; netadmin "netadmin.mynet.org"; }; Which I don't think is even a setting, and if it is, the documentation in the Set Block is missing for these. Seems like something controlled under the oper class block maybe instead? I reported this before but I'll state it again, even with the m_admin module disabled, the admin {}; block is still required, which should not be. Lastly, the "config.settings" file generated after "./Config" has a few options that arent listed with any documentation as to what they are: SHOWLISTMODES="1" TOPICNICKISNUH="" SHUNNOTICES="" NOOPEROVERRIDE="" DISABLEUSERMOD="" OPEROVERRIDEVERIFY="" DISABLEEXTBANSTACKING="" Any information on these would be great for advanced users. | ||||
| Tags | No tags attached. | ||||
| 3rd party modules | |||||
|
|
Thanks, I've fixed the ~m:censor to be ~m:filter. I see Gottem fixed the docs for the nofakelag stuff. As for configuration syntax.. it is true that those settings don't exist anymore, but then again they are in the 'syntax' section.. so.. I don't know? Is it really that bad? Well, we could replace it with some other real examples I guess. m_admin yeah I think that bug report is still open As for config.settings.. it's true that those variables are not explained anywhere. On the other hand if you run ./Config or more likely ./Config -advanced you will get a good description about those settings. Don't you agree? Or what do you think should be improved... a reference to ./Config -advanced somewhere? Right now it's only in ./Config -help I believe. |
