Chat - Revision history

imported>LassiPulkkinen: /* Client chat mode */ Typo.

2024-03-13T23:22:39Z

Client chat mode: Typo.

← Older revision		Revision as of 23:22, 13 March 2024
Line 9:		Line 9:
	It is the server's responsibility to not send packets if the client has the given type disabled. However, it is the client's responsibility to not send incorrect chat packets.		It is the server's responsibility to not send packets if the client has the given type disabled. However, it is the client's responsibility to not send incorrect chat packets.

	Here's a matrix comparing what packets the server should send to a clients based on their chat settings:		Here's a matrix comparing what packets the server should send to clients based on their chat settings:

	{\| class="wikitable"		{\| class="wikitable"

imported>LassiPulkkinen: Fix section titles.

2024-02-04T11:39:02Z

Fix section titles.

← Older revision		Revision as of 11:39, 4 February 2024
Line 3:		Line 3:
	This article details various aspects of Minecraft's chat system. The packets themselves are documented in [[Protocol]].		This article details various aspects of Minecraft's chat system. The packets themselves are documented in [[Protocol]].

	=== Client chat mode ===		== Client chat mode ==

	The client may use the Chat Mode field of the [[Protocol#Client Information (configuration)\|Client Information]] packet to indicate that it only wants to receive some types of chat messages.		The client may use the Chat Mode field of the [[Protocol#Client Information (configuration)\|Client Information]] packet to indicate that it only wants to receive some types of chat messages.
Line 68:		Line 68:
	If the client attempts to send a chat message and the server rejects it, the Notchian server will send that client a [[Protocol#System Chat Message\|System Chat Message]] (non-overlay) with a red <code>chat.disabled.options</code> translation component (which becomes "Chat disabled in client options.").		If the client attempts to send a chat message and the server rejects it, the Notchian server will send that client a [[Protocol#System Chat Message\|System Chat Message]] (non-overlay) with a red <code>chat.disabled.options</code> translation component (which becomes "Chat disabled in client options.").

	=== Social Interactions (blocking) ===		== Social Interactions (blocking) ==

	1.16 added a ''social interactions screen'' that lets players block chat from other players. Blocking takes place clientside by detecting whether a message is from a blocked player.		1.16 added a ''social interactions screen'' that lets players block chat from other players. Blocking takes place clientside by detecting whether a message is from a blocked player.

imported>LassiPulkkinen: Simplify wording.

2024-02-04T11:36:24Z

Simplify wording.

← Older revision		Revision as of 11:36, 4 February 2024
Line 1:		Line 1:
	{{Hatnote\|This page previously contained documentation on text formatting features, which can now be found at [[Text formatting]].}}		{{Hatnote\|This page previously contained documentation on text formatting features, which can now be found at [[Text formatting]].}}

	This article details various ~~features and considerations~~ of Minecraft's chat system. The packets themselves are documented in [[Protocol]].		This article details various aspects of Minecraft's chat system. The packets themselves are documented in [[Protocol]].

	=== Client chat mode ===		=== Client chat mode ===

imported>LassiPulkkinen: Split off Text formatting.

2024-01-10T18:08:31Z

Split off Text formatting.

Show changes

imported>LassiPulkkinen: /* Standard chat message */ Oops.

2024-01-07T22:21:42Z

Standard chat message: Oops.

← Older revision		Revision as of 22:21, 7 January 2024
Line 215:		Line 215:
	The normal chat message uses a translation component along with some styling.		The normal chat message uses a translation component along with some styling.

	{{Warning2\|Since 1.19.1 the Notchian ~~client~~ uses the [[Registry Data#Chat Type\|chat type]] mechanism, meaning chat messages are no longer sent directly like shown in this example.}}		{{Warning2\|Since 1.19.1 the Notchian server uses the [[Registry Data#Chat Type\|chat type]] mechanism, meaning chat messages are no longer sent directly like shown in this example.}}

	<syntaxhighlight lang="javascript">		<syntaxhighlight lang="javascript">

imported>LassiPulkkinen: /* Old system */ Reorder...

2024-01-07T22:19:32Z

Old system: Reorder...

← Older revision		Revision as of 22:19, 7 January 2024
Line 233:		Line 233:

	e.g.: <code>This is white, but §4this is dark red. §lThis is still red, but also bold, while §rthis is neither.</code>		e.g.: <code>This is white, but §4this is dark red. §lThis is still red, but also bold, while §rthis is neither.</code>

			There is no way to escape the <code>§</code> or <code>&</code> symbol; the Notchian server and client simply disallow it in text originating from the player.

	The Notchian client processes these formatting sequences in virtually all rendered text. Their effects are constrained to the specific run of text they're part of, and <code>§r</code> reverts back merely to the styling inherited from the surrounding context. In the context of text components, instances of <code>text</code> or <code>keybind</code> content are considered singular runs of text, whereas in <code>translatable</code> content each static (non-placeholder) segment is an individual run.		The Notchian client processes these formatting sequences in virtually all rendered text. Their effects are constrained to the specific run of text they're part of, and <code>§r</code> reverts back merely to the styling inherited from the surrounding context. In the context of text components, instances of <code>text</code> or <code>keybind</code> content are considered singular runs of text, whereas in <code>translatable</code> content each static (non-placeholder) segment is an individual run.

	~~There is no way to escape the <code>§</code> or <code>&</code> symbol; the Notchian server and client simply disallow it in text originating from the player.~~

	In '''Minecraft Classic''', the Notchian client expects that an escape code in a chat message will be followed by at least one character, and will otherwise crash with a StringIndexOutOfBoundsException. The server must sanitize outbound messages by removing any control characters at the end.		In '''Minecraft Classic''', the Notchian client expects that an escape code in a chat message will be followed by at least one character, and will otherwise crash with a StringIndexOutOfBoundsException. The server must sanitize outbound messages by removing any control characters at the end.

imported>LassiPulkkinen: /* Old system */ Mention lack of escape for §.

2024-01-07T22:17:31Z

Old system: Mention lack of escape for §.

← Older revision		Revision as of 22:17, 7 January 2024
Line 235:		Line 235:

	The Notchian client processes these formatting sequences in virtually all rendered text. Their effects are constrained to the specific run of text they're part of, and <code>§r</code> reverts back merely to the styling inherited from the surrounding context. In the context of text components, instances of <code>text</code> or <code>keybind</code> content are considered singular runs of text, whereas in <code>translatable</code> content each static (non-placeholder) segment is an individual run.		The Notchian client processes these formatting sequences in virtually all rendered text. Their effects are constrained to the specific run of text they're part of, and <code>§r</code> reverts back merely to the styling inherited from the surrounding context. In the context of text components, instances of <code>text</code> or <code>keybind</code> content are considered singular runs of text, whereas in <code>translatable</code> content each static (non-placeholder) segment is an individual run.

			There is no way to escape the <code>§</code> or <code>&</code> symbol; the Notchian server and client simply disallow it in text originating from the player.

	In '''Minecraft Classic''', the Notchian client expects that an escape code in a chat message will be followed by at least one character, and will otherwise crash with a StringIndexOutOfBoundsException. The server must sanitize outbound messages by removing any control characters at the end.		In '''Minecraft Classic''', the Notchian client expects that an escape code in a chat message will be followed by at least one character, and will otherwise crash with a StringIndexOutOfBoundsException. The server must sanitize outbound messages by removing any control characters at the end.

imported>LassiPulkkinen: /* Text content */ Link capitalization.

2024-01-07T21:48:06Z

Text content: Link capitalization.

← Older revision		Revision as of 21:48, 7 January 2024
Line 105:		Line 105:

	;<code>text</code>		;<code>text</code>
	:''String''. Set as the content directly, with no additional processing. (But see [[#Old ~~System~~]], which still applies.)		:''String''. Set as the content directly, with no additional processing. (But see [[#Old system]], which still applies.)

	=== Translatable content ===		=== Translatable content ===

imported>LassiPulkkinen: /* Text content */ Warn about legacy formatting.

2024-01-07T21:47:05Z

Text content: Warn about legacy formatting.

← Older revision		Revision as of 21:47, 7 January 2024
Line 105:		Line 105:

	;<code>text</code>		;<code>text</code>
	:''String''. Set as the content directly, with no additional processing.		:''String''. Set as the content directly, with no additional processing. (But see [[#Old System]], which still applies.)

	=== Translatable content ===		=== Translatable content ===

imported>LassiPulkkinen: /* Current system (text components) */ Make server-side resolution warnings less obnoxious.

2024-01-07T21:31:02Z

Current system (text components): Make server-side resolution warnings less obnoxious.

← Older revision		Revision as of 21:31, 7 January 2024
Line 148:		Line 148:
	Resolved by the server into text content containing the value of <code>objective</code> for <code>name</code>, or the empty string if none exists.		Resolved by the server into text content containing the value of <code>objective</code> for <code>name</code>, or the empty string if none exists.

	~~{{Warning2\|This content type must be resolved by the server~~, ~~and~~ will be displayed as empty text ~~if sent directly to a client~~.}}		If sent directly to a client, will be displayed as empty text.

	=== Selector content ===		=== Selector content ===
Line 159:		Line 159:
	Resolved by the server into a delimited list of entities matching the selector, each with an appropriate hover event (and click event if it happens to be a player).		Resolved by the server into a delimited list of entities matching the selector, each with an appropriate hover event (and click event if it happens to be a player).

	~~{{Warning2\|This content type must be resolved by the server~~, ~~and~~ will be displayed as the selection pattern ~~if sent directly to a client~~.}}		If sent directly to a client, will be displayed as the selection pattern.

	=== NBT content ===		=== NBT content ===
Line 181:		Line 181:
	Resolved by the server into a delimited list of all NBT values, for all objects specified by the data source, matching the specified path.		Resolved by the server into a delimited list of all NBT values, for all objects specified by the data source, matching the specified path.

	~~{{Warning2\|This content type must be resolved by the server~~, ~~and~~ will be displayed as empty text ~~if sent directly to a client~~.}}		If sent directly to a client, will be displayed as empty text.

	=== Examples ===		=== Examples ===