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
Is your feature request related to a problem? Please describe.
There are multiple onPlayerChat event handlers across multiple resources that implement the same or trivial functionality, such as:
playercolors: hooks onPlayerChat to apply the player's nametag color to their name in chat
freeroam: duplicates playercolor functionality and implements spam protections
Is your feature request related to a problem? Please describe.
There are multiple
onPlayerChat
event handlers across multiple resources that implement the same or trivial functionality, such as:playercolors
: hooks onPlayerChat to apply the player's nametag color to their name in chatfreeroam
: duplicatesplayercolor
functionality and implements spam protectionstdma
: applies team colors to chat messagesctv
: same as aboveassault
: same as aboveIn the case of
freeroam
andplayercolors
, these handlers conflict with each other resulting in chat messages appearing twice (see #460).The other cases are examples of duplicated functionality, which isn't ideal.
Describe the solution you'd like
Implement a new
chatmanager
resource with the following functionality, customizable via resource settings:admin
andadmin2
Describe alternatives you've considered
Changes could be made within mtasa-blue to implement player and team name colors in chat by default.
Additional context
Previous pull requests that weren't completed:
#461
#463
The text was updated successfully, but these errors were encountered: