View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0000001 | WolfAdmin | Commands | public | 2015-01-20 09:25 | 2016-03-09 17:58 |
| Reporter | Timo | Assigned To | Timo | ||
| Priority | normal | Severity | feature | Reproducibility | N/A |
| Status | closed | Resolution | won't fix | ||
| Target Version | 1.1.0 | ||||
| Summary | 0000001: Automatically !kick after x warns | ||||
| Description | autokick just like ETAdmin | ||||
| Tags | No tags attached. | ||||
| Mod | N/A | ||||
| Mod version | |||||
| Standalone | no | ||||
|
|
Decided not to implement this. Mainly because it will become a hassle to check whether someone has already been kicked/banned/whatever. If I would not perform these checks (which may become expensive) every (x+n)'th warn would result in an autokick being triggered. As warns are not stored per player session and the module is restarted after each session, I cannot do this per session (without having to do these checks). |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2015-01-20 09:25 | Timo | New Issue | |
| 2015-01-20 09:25 | Timo | Status | new => assigned |
| 2015-01-20 09:25 | Timo | Assigned To | => Timo |
| 2015-01-21 11:50 | Timo | Status | assigned => new |
| 2016-02-26 11:31 | Timo | Status | new => assigned |
| 2016-02-26 11:31 | Timo | Target Version | => 1.1.0 |
| 2016-03-04 12:24 | Timo | Relationship added | related to 0000055 |
| 2016-03-09 17:58 | Timo | Note Added: 0000060 | |
| 2016-03-09 17:58 | Timo | Status | assigned => closed |
| 2016-03-09 17:58 | Timo | Resolution | open => won't fix |
