You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
TrickyLeifa opened this issue
May 23, 2024
· 2 comments
Assignees
Labels
bugConfirmed bugDOOM#%Something is doomed to be destroyedengine/timingIssues related to event timing and sequencing (not lag-related issues)exploitThis issue causes an exploithackuiIssues related to the user interface (non-viewport related)
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.
The text was updated successfully, but these errors were encountered:
Messages are coming in to the client > The client types a message and hits enter > Text input is disabled/greyed out/otherwise made clear you cannot hit enter again > Client waits for their SINGLE message to be processed > Text input is enabled/not greyed/etc.
This preserves the "you don't have to hold down enter" behavior, keeps the incoming queue, and solves the issue of compounding chat noise via multiple outbound messages.
bugConfirmed bugDOOM#%Something is doomed to be destroyedengine/timingIssues related to event timing and sequencing (not lag-related issues)exploitThis issue causes an exploithackuiIssues related to the user interface (non-viewport related)
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.
The text was updated successfully, but these errors were encountered: