View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0003703 | unreal | ircd | public | 2008-06-18 03:36 | 2008-08-26 23:27 |
| Reporter | Bricker | Assigned To | |||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | not fixable | ||
| Product Version | 3.2.7 | ||||
| Summary | 0003703: Channel Ban Reason | ||||
| Description | That's right. Set a ban, give a reason. Why? Oh I dunno, maybe so when [email protected] joins #Chan "You were banned cuz you fail at life" "You suck, fuck off" etc etc etc... Basically, idea i came up with for Unreal would be... /mode #Chan +b ~r:*!*@* "Reason here but if left blank, revert to default" or something else. ANyway, discuss. *(Also, could be useful for chanops to see why someone was banned, but they wouldnt be stored in the channel ban list for "GUI" but somehow listing stuff)* | ||||
| 3rd party modules | |||||
|
|
been discussed on InspIRCds side, their is some hackish stuff they have as a 3rd partly, mostly don't think this will work. Closing, can always reopen later. " side note, i'm so sick of new features being limited by the fucking client. |
|
|
See Notes |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2008-06-18 03:36 | Bricker | New Issue | |
| 2008-06-18 03:36 | Bricker | QA | => Not touched yet by developer |
| 2008-06-18 03:36 | Bricker | U4: Need for upstream patch | => No need for upstream InspIRCd patch |
| 2008-06-18 03:36 | Bricker | U4: Upstream notification of bug | => Not decided |
| 2008-06-18 03:36 | Bricker | U4: Contributor working on this | => None |
| 2008-08-26 23:26 | Bricker | Note Added: 0015377 | |
| 2008-08-26 23:27 | Bricker | Status | new => closed |
| 2008-08-26 23:27 | Bricker | Note Added: 0015378 | |
| 2008-08-26 23:27 | Bricker | Resolution | open => not fixable |
