cmss13-devs / cmss13-devs/cmss13

OW Console unusable due to processing action bugged

Open
#11,772 0 comments 0 reactions 0 assignees View on GitHub
Bug Needs Reproducing
Dominant language
DM
Stars
170
Forks
940
Avg merge
5d 16h
Merged PRs (30d)
61

Description

## Testmerges
#10999: 'Fix of various plane related issues' by Blundir at commit f85a7153c4
#11661: 'Despoiler rework' by Git-Nivrak at commit c0f8d2884f
#11590: 'Elite Human Hunting Grounds Presets' by dawsonkeyes at commit f154d98543

## Round ID
32640

## Description of the bug
Overwatch console becomes unusable due to a perpetual cycle of "processing action"
Cause is unknown to be exact but my theory is that it's caused by when two OW console receive the same action order and is processing at the same time like firing an OB at the same time on both consoles but this is just a theory
If someone could experiment around and find out the actual cause, that would be appreciated

## What's the difference with what should have happened?
OW Console should be able to be used after the action process

## How do we reproduce this bug?
Theory test:
1. Dial OB coords on 2 different console unsure if you would need the same coords or it would work with completely different ones
2. Fire the OB at the same time on both consoles
3. Then check if the console is bugged "processing the action"

## Attached logs
```
N/A
```

## Additional details
- Author: General Hi Ping
- Admin: SmellyHippie
- Note: None

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.