We’ve forked the legacy chat system in our game and have made compression/other edits to further reduce network overhead. We still use the underlying infrastructure of remotes as required to use this service, but there are false positive assertions in place that create warnings for every single chat message sent in our servers. The specific source of this issue is Time which we have no ability to modify, as it’s created and sent naturally behind CoreGui which expects a certain compression spec.
For context; the purpose behind forking is because after every chat message is filtered (mostly immediately), legacy chat re-sends an at least 0.5KB message to all clients twice consecutively. We do not want to migrate to TextChatService for multiple unrelated reasons.
Malformed message data sent to chat event "OnMessageDoneFiltering". If you have modified the chat system, check what you are firing to this event - Client - CoreScripts/PlayerBillboards:135
[interface] bad value for Time: number expected, got nil - Client - CoreScripts/PlayerBillboards:136
Expected behavior
These warnings are false positives and should not emit if a message does not exactly meet a compressed specification. We have no way of modifying CoreScripts or the internally defined compression spec, but would still like to use the service/feature as a whole for the useful qualities it has. Please just silence these warnings.
Hi @hello42, to assist the team’s review, would you be able to elaborate on why you aren’t using the latest TextChatService? They are interested in any feedback or insights you can share.
We don’t use TextChatService because we feel it’s less customizable, less accessible to the developer, has performance issues, and as well, problems with high network receive. We see it’s CoreScript labels showing up in our Microprofiler dumps, alongside the accompanying CoreGui Roblox Leaderboard.
A lack of performance testing has hurt low end devices that we want to keep playing our games. There shouldn’t be a case where something Roblox instantiates at runtime causing low-end devices to crash. We call that bloatware and/or malware.
It has been 80 days and this issue still persists. Is this warning load-bearing?
The lack of tab support is mainly the reason it isn’t being used in many popular military games like “War Tycoon” and “Multi-Crew Tank Combat 4”, since having different chats for different teams, factions, squads, etc is a vital and an important feature and aspect of the games. I hope this could be added soon, I don’t understand why was the new TextChatService released with the lack of features from the old legacy chat system. Also as @hello42 pointed out there are performance issues with TextChatService that up until now are still not fixed.
