Skip to content

Remove or redesign "ghost" messages #972

@TrickyLeifa

Description

@TrickyLeifa

Ghost messages are a "feature" that was recently added, unfortunately this "feature" also exemplify a good deal of why it is very poorly designed. First is code complexity, the amount of code that was changed (especially logs) to accommodate the supposed feature is a cruel mistake. The code is very shoddy and so poorly implemented you have to use a magnifying glass and a PHD in natural science to figure out the intention of some of it.

The very fact that the 'Instant Objection' toggle can completely bypass the ghost message is horrendous. Additionally, the fact there can be multiples ghost messages queued after another, which completely defeats the purpose of the system which is meant to relay to the user that ONE other user already spoke and that their message is on the way is idiotic at best and completely insane at worst. If everyone can queue their message anyway with a system that is meant to control the flow of messages it's completely and utterly useless.

Metadata

Metadata

Assignees

Labels

DOOM#%Something is doomed to be destroyedbugConfirmed bugengine/timingIssues related to event timing and sequencing (not lag-related issues)exploitThis issue causes an exploithackuiIssues related to the user interface (non-viewport related)

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions