With this you could still hook the server on the Remote, still getting every message, whisper or not, which then you could still create your message logging system like this. This is how I think it should be done:Ĭlient sends Message > FireServer > Server handles request and decides if it should be sent to one or more users > FireClient / FireAllClients based on if it’s a private or public message > Client adds it to the chat Which this allows the client to snap onto any messages getting sent and from who, including whispers. As Roblox sends the event to the server, which you can grab by attaching a remote to it in the MessageSender under Chat, or just grab the default Chat RemoteEvent from the server.Ĭlient sends Message > FireServer > Server handles request > FireAllClients > Client finds if it’s supposed to be responding to that Remote I think there would be a way around this. Roblox server should check the recipient argument and only send the event to the intended recipient if there is one, instead of broadcasting it to all clients. Exploiters may use this information to then intimidate players, potentially making players feel scared that their personal information can be accessed by someone random. Players on the platform have the belief that using the whisper chat is a means of private communication between themselves and their friends.ĭue to this, players often share personal information via whisper messages, which currently can also be viewed by exploiters. Recently, a lot of exploits have surfaced, some of which that allow the exploiter to listen to the Chatted event to spy on peoples in-game conversations. This event currently fires on all clients regardless of the intended recipient. As described on the Roblox Developer site, recipient is set to nil if the player was not whispering to another player, but contains a Player instance when the message is sent in whisper chat.

Player.Chatted fires an event with the parameters message and recipient.

2022.09

Roblox how to whisper