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
Called when a chat message from another player arrives. The emitted object contains:
* formattedMessage -- (JSON) the chat message preformatted, if done on server side
* plainMessage -- (Plaintext) the chat message without formatting (for example no `<username> message` ; instead `message`), on version 1.19+
* unsignedContent -- (JSON) unsigned formatted chat contents ; should only be present when the message is modified and server has chat previews disabled - only on version 1.19 - 1.19.2
* type -- the message type - on 1.19, which format string to use to render message ; below, the place where the message is displayed (for example chat or action bar)
* sender -- the UUID of the player sending the message
* senderTeam -- scoreboard team of the player (pre 1.19)
* senderName -- Name of the sender
* targetName -- Name of the target (for outgoing commands like /tell). Only in 1.19.2+
* verified -- true if message is signed, false if not signed, undefined on versions prior to 1.19
from testing (on 1.19.4), I found that it looks something more like this:
interfaceServerPlayerMessage{formattedMessage?: stringplainMessage?: stringunsignedContent: stringtype: numbersender: UUID// no senderTeam (since only pre-1.19)senderName: stringtargetName: string|undefinedverified: boolean}
Versions
Detailed description of a problem
according to index.d.ts,
playerChat
event's data looks like this:but this is inconsistent according to API.md:
from testing (on
1.19.4
), I found that it looks something more like this:Expected behavior
index.d.ts = API.md = "real life" (testing)
The text was updated successfully, but these errors were encountered: