View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000772 | unreal | documentation | public | 2003-03-06 07:00 | 2003-11-20 19:46 |
| Reporter | Brad | Assigned To | syzop | ||
| Priority | normal | Severity | feature | Reproducibility | always |
| Status | closed | Resolution | no change required | ||
| Product Version | 3.2-beta15 | ||||
| Summary | 0000772: set::oper-auto-join bug | ||||
| Description | In the Unreal3.2 Docs it says set::oper-auto-join <channels>; The channel(s) a user will be forced to join when they /oper. To specify more than one channel use a comma seperated list. [Note: don't forget to add quotes, like: oper-auto-join "#chan";] yet when adding oper-auto-join "#Services,#Opers"; it only sends user to the first channel on a /oper. Not sure if it's doc bug like AngryWolf seems to think, or if it should actually work the way it's documented, but I know it works that way and correctly on 3.1.x BTW, I wasn't the one who noticed this first, "frozen" did on the unreal support channel. Though it does affect my server, as well. | ||||
| 3rd party modules | |||||
|
|
"Not sure if it's doc bug like AngryWolf seems to think" No, I didn't think it's a doc bug, but, uhm, both auto-join and oper-autojoin are working well for me... |
|
|
The whole value of set::oper-auto-join is sended to a /join command which allows a comma separated list, therefore it should work. (I assume you could join manually.) |
|
|
Well, I don't know about frozen.. but it seemed like I did a /rehash too soon before my FTP client got the file uploaded, I just did another /rehash and it works now. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2003-11-20 19:46 | syzop | Status | resolved => closed |
