| View Issue Details [ Jump to Notes ] | [ Issue History ] [ Print ] | ||||||||
| ID | Project | Category | View Status | Date Submitted | Last Update | ||||
|---|---|---|---|---|---|---|---|---|---|
| 0006317 | Spring engine | Lua | public | 2019-10-11 02:37 | 2019-11-02 15:18 | ||||
| Reporter | sprung | ||||||||
| Assigned To | Kloot | ||||||||
| Priority | low | Severity | feature | Reproducibility | N/A | ||||
| Status | resolved | Resolution | fixed | ||||||
| Product Version | 104.0 +git | ||||||||
| Target Version | Fixed in Version | 104.0 +git | |||||||
| Summary | 0006317: Expand AllowCommand with playerID | ||||||||
| Description | After d2d0240c17cacc812ecad1511514a25b83917987 it became possible for various players to control the same team (even earlier there was comshare). That patch only has allyteam-level granularity but having playerID in AllowCommand would enable finer control. Any other solution that allows (a player on) team A to control team B, but not team C, and doesn't necessarily allow team B to control A, would also be fine. | ||||||||
| Tags | No tags attached. | ||||||||
| Checked infolog.txt for Errors | Irrelevant | ||||||||
| Attached Files |
| ||||||||
 Relationships |
|
 Relationships |
| Notes |
|
|
sprung (reporter) 2019-10-11 02:39 |
Addendum to the last sentence: "given that teams A, B, and C are on the same allyteam". |
| Notes |
| Issue History |
|||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2019-10-11 02:37 | sprung | New Issue | |
| 2019-10-11 02:39 | sprung | Note Added: 0020174 | |
| 2019-11-02 15:18 | Kloot | Assigned To | => Kloot |
| 2019-11-02 15:18 | Kloot | Status | new => resolved |
| 2019-11-02 15:18 | Kloot | Resolution | open => fixed |
| 2019-11-02 15:18 | Kloot | Fixed in Version | => 104.0 +git |
| Issue History |