View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0019948 | Return of Reckoning | General | public | 2023-08-13 04:32 | 2023-08-13 04:32 |
| Reporter | ReturnOfReckoning | Assigned To | |||
| Priority | normal | Severity | minor | Reproducibility | have not tried |
| Status | new | Resolution | open | ||
| Summary | 0019948: Battle for Praag: numerous objective capture bugs | ||||
| Description | Reporter: Zomega-WAR <!-- Issues should be unique. Check if someone else reported the issue first, and please don't report duplicates. Only ONE issue in a report. Don't forget screens or a video. --> **Expected behavior and actual behavior:** 1) Expected: only the active flag can be captured Actual: locked flags can also have their progress changed (screenshot 1) 2) Expected: when a flag unlocks, it starts off neutral with no capture progress Actual: the unlocked flag can start in a state fully or partially captured by the team who held it previously, leading to either a very long capture time for the team trying to take it back, or an almost instant re-capture for the team who held it previously (screenshot 2, not very clear though) 3) Expected: when a flag is captured, there was a timer which controlled how long it had to be defended for before the next flag would unlock Actual: this timer is 0 seconds, so the moment a flag is captured the next flag immediately unlocks without giving the otherside to try and take back the captured flag. No screenshot of this as it's hard to show. 4) Expected: a timer showing when the first flag (central) can be captured at the start of the match Actual: the timers are now missing (screenshot 3) Due to how capture times varying depending on how many people are on the flag it is impossible to tell which of these issues are cosmetic with the scoreboard/tracker and which are actually affecting the flag capture time. **Screenshot 1: progress on 2 flags at once, one of which is locked.**  **Screenshot 2: buggy progress on central maintained once south central was captured, instead of central starting out as neutral**  In these two screenshots, destro were capping south-central while central was being uncapped even though it was locked. South central was then captured, and central did not reset to neutral. Order had control of central by then and were able to achieve a very quick capture (looks like only half a bar was needed?).   **Screenshot 3: no timer showing when central will unlock at the start of the scenario.**  <!-- Note that game critical and game breaking bugs may award a manticore/griffon (realm specific) at the leads discretion however, asking for one instantly disqualifies you from this reward. --> | ||||
| Tags | Scenarios, World Object | ||||
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2023-08-13 04:32 | ReturnOfReckoning | New Issue | |
| 2023-08-13 04:32 | ReturnOfReckoning | Tag Attached: Scenarios | |
| 2023-08-13 04:32 | ReturnOfReckoning | Tag Attached: World Object |
