TextChatMessage.Metadata can no longer be modified on the server

Bug Reports Engine Bugs
,
1

Previously, changes to TextChatMessage.Metadata on the server would be replicated to clients. This is no longer the case.

Pictured below is what it looks like when I print before and after modification on the server (lines 1 and 2,) and when the client receives the message (line 3.) The client should be seeing the same text in line 2.

{98BE94C5-7CAF-4BEE-880E-971CA1AE8D38}

Code used:

print(message.Status, message.Metadata, message.PrefixText, message.Text)
message.Metadata = HttpService:JSONEncode({Dead = dead, Team = team, TeamChat = teamChat})

2

Thanks for the report. We’ll follow up when we have an update for you.

3

Hello and thank you for the report! It looks like like this report was marked as a duplicate, is there another post that I can take a look at to understand this further?

This does look like intentional behavior to me though. Generally the metadata argument is set by being passed as an argument to TextChannel:SendAsync or TextChannel:DisplaySystemMessage, and it’s not intended to be modified on the server so that it can be passed on to the client. I’m not sure how this was working before though.

I’m curious as to what your use case is for modifying the metadata on the server? Maybe there is another way to get what you’d like done without changing the metadata.

4

I was modifying metadata on the server to tell recipients if the sender was dead or not at the time the message was being processed.

Doing it this way would have had the benefit of allowing a message to be received from dead players if they were alive at the time of sending.

I’m just checking if the sender is currently dead at the time of receipt on the client now.

5

I think this was marked as a duplicate in error. I can’t find any related posts.