Minecraft:Formatting codes: Difference between revisions
More actions
Sync: updated from Minecraft |
Sync: updated from Minecraft |
||
| (10 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
{{about|the legacy §-based formatting system|the modern system|Text component format|emoji shortcodes in ''Bedrock Edition''| | {{about|the legacy §-based formatting system|the modern system in ''Java Edition''|Text component format|emoji shortcodes in ''Bedrock Edition''|Font#Emoji support}} | ||
{{Redirect|Format|pack formats|Pack format}} | {{Redirect|Format|pack formats|Pack format}} | ||
{{Deprecated feature|See {{bug|MC-190605}}, and [[Minecraft:Ore UI]] does not support them.}} | {{Deprecated feature|See {{bug|MC-190605}}, and [[Minecraft:Ore UI]] does not support them.}} | ||
[[File:Minecraft Formatting.gif|thumb|200px|A book showing the possible formatting options with the character that performs them | [[File:Minecraft Formatting.gif|thumb|200px|A book showing the possible formatting options with the character that performs them]] | ||
'''Formatting codes''' | '''Formatting codes''' add color and modifications to [[Minecraft:Font|text]] in-game. | ||
Text in ''Minecraft'' can be formatted with the {{w|section sign}} (<code>§</code>). {{IN|bedrock}}, the section sign can be used in [[Minecraft: | Text in ''Minecraft'' can be formatted with the {{w|section sign}} (<code>§</code>). {{IN|bedrock}}, the section sign can be used in almost any in-game text input such as [[Minecraft:Book and Quill|book and quills]] and the [[Minecraft:chat]]. {{IN|java}}, section signs may only be used in text outside gameplay, such as [[Minecraft:resource packs]] and world titles. | ||
== Usage == | == Usage == | ||
Text can be formatted using the section sign (§) followed by a character. A § symbol followed by a | Text can be formatted using the section sign (<code>§</code>) followed by a character. A <code>§</code> symbol followed by a character in the message tells the client to switch colors while displaying text. | ||
=== ''Java Edition'' === | === ''Java Edition'' === | ||
Formatting codes can be used in <samp>[[Minecraft:server.properties|<code>server.properties</code>]]</samp>, <samp>[[Minecraft:pack.mcmeta|<code>pack.mcmeta</code>]], [[Minecraft:Splash|<code>splashes.txt</code>]]</samp>, [[Minecraft:language]] files, world titles, commands such as <code>/tellraw</code> and <code>/title</code> in [[Minecraft:datapacks|data packs]], and server names. | |||
If a color code is used after a formatting code, the formatting code is disabled beyond the color code point. For example, <code>§cX§nY</code> displays as <span class="format-c" style="font-family: Minecraft;">X<u>Y</u></span>, whereas <code>§nX§cY</code> displays as <span class="format-f" style="font-family: Minecraft"><u>X</u><span class="format-c">Y</span></span>. Therefore, when using a color code in tandem with a formatting code, ensure the color code is used first and reuse the formatting code when changing colors. Also, you could put <code>§r§f</code> in an anvil to rename an item as non-italic. | If a color code is used after a formatting code, the formatting code is disabled beyond the color code point. For example, <code>§cX§nY</code> displays as <span class="format-c" style="font-family: Minecraft;">X<u>Y</u></span>, whereas <code>§nX§cY</code> displays as <span class="format-f" style="font-family: Minecraft"><u>X</u><span class="format-c">Y</span></span>. Therefore, when using a color code in tandem with a formatting code, ensure the color code is used first and reuse the formatting code when changing colors. Also, you could put <code>§r§f</code> in an anvil to rename an item as non-italic. | ||
=== ''Bedrock Edition'' === | === ''Bedrock Edition'' === | ||
{{info|section=1|[[Minecraft:Ore UI#Warning|Ore UI]] does not support color codes.<ref>{{tweet|Volgar|1867216296821370992|It probably won't be supported in the new screens, but it certainly shouldn't look like this, just plain text. Thanks, I'll pass it to the team.}}</ref><ref>{{bug|MCPE-174371| | {{info|section=1|[[Minecraft:Ore UI#Warning|Ore UI]] does not support color codes in most situations.<ref>{{tweet|Volgar|1867216296821370992|It probably won't be supported in the new screens, but it certainly shouldn't look like this, just plain text. Thanks, I'll pass it to the team.}}</ref><ref>{{bug|MCPE-174371||The new "Play screen" UI doesn't support colored characters|WAI}}</ref><ref>{{bug|MCPE-152246||New Create New World UI doesn't support text formatting codes|WAI}}</ref>{{more info needed|It works in a few places, such as DDUI <code>CustomForm</code> labels, though even then some areas of <code>CustomForm</code>s lack support. Where all does it work exactly?}}}} | ||
Formatting codes | Formatting codes can be used in any text input, but will only be displayed in JSON UI. Additionally, Realm names and player names disallow formatting codes. This practically limits formatting codes to the following uses: | ||
[[ | |||
* [[Minecraft:Book and Quill|Book and quill]] text, name, and author. | |||
* [[Minecraft:Chat]] messages, including those sent by commands like {{Command|msg}}. | |||
* [[Minecraft:Signs]] and [[Minecraft:hanging signs]], without requiring dyes. | |||
* [[Minecraft:Anvils]] and [[Minecraft:Cartography Tables|cartography tables]] to rename [[Minecraft:items]]. Nameplates from [[Minecraft:name tags]] or other means also display formatting. | |||
* Text in [[Minecraft:resource packs]] displayed in-game, like language files, [[Minecraft:splashes]], [[Minecraft:loading tips]], and [[Minecraft:credits]]. | |||
* Pack names, descriptions, and settings strings. | |||
* Commands that can display text, like {{Command|title}} but also {{Command|scoreboard}}. | |||
* Technically world names and server names, but these are rarely displayed in JSON UI. | |||
Formatting codes persist after a color code. Usage in [[Minecraft:party]] chat censors the entire message. | |||
=== Color codes === | === Color codes === | ||
| Line 105: | Line 117: | ||
| <code>§9</code> | | <code>§9</code> | ||
| <code>blue</code> | | <code>blue</code> | ||
| 85 || 85 || 255 || style="text-align: left;" | {{color|#5555FF}} | | 85 || 85 || 255 || style="text-align: left;" | {{color|#5555FF}}{{Until|BE 26.50}} | ||
{{color|#447FFF}}{{Upcoming|BE 26.50}} | |||
| 21 || 21 || 63 || style="text-align: left;" | {{color|#15153F}} | | 21 || 21 || 63 || style="text-align: left;" | {{color|#15153F}} | ||
| <code>\e[0;94m</code> | | <code>\e[0;94m</code> | ||
| Line 157: | Line 170: | ||
| 55 || 53 || 1 || style="text-align: left;" | {{color|#373501}} | | 55 || 53 || 1 || style="text-align: left;" | {{color|#373501}} | ||
| — | | — | ||
| {{only|be|short=1}} | | {{only|be|short=1}}<br>Unavailable on Playstation. | ||
|- | |- | ||
| <code>§h</code> | | <code>§h</code> | ||
| <code>material_quartz</code> | | <code>material_quartz</code> | ||
| 227 || 212 || 209 ||style="text-align: left;" | {{color|#E3D4D1}} | | 227 || 212 || 209 ||style="text-align: left;" | {{color|#E3D4D1}}{{Until|BE 26.50}} | ||
{{color|#D9CCB8}}{{Upcoming|BE 26.50}} | |||
| 56 || 53 || 52 || style="text-align: left;" | {{color|#383534}} | | 56 || 53 || 52 || style="text-align: left;" | {{color|#383534}} | ||
| — | | — | ||
| Line 168: | Line 182: | ||
| <code>§i</code> | | <code>§i</code> | ||
| <code>material_iron</code> | | <code>material_iron</code> | ||
| 206 || 202 || 202 ||style="text-align: left;" | {{color|#CECACA}} | | 206 || 202 || 202 ||style="text-align: left;" | {{color|#CECACA}}{{Until|BE 26.50}} | ||
{{color|#A9B4B7}}{{Upcoming|BE 26.50}} | |||
| 51 || 50 || 50 || style="text-align: left;" | {{color|#333232}} | | 51 || 50 || 50 || style="text-align: left;" | {{color|#333232}} | ||
| — | | — | ||
| Line 175: | Line 190: | ||
| <code>§j</code> | | <code>§j</code> | ||
| <code>material_netherite</code> | | <code>material_netherite</code> | ||
| 68 || 58 || 59 ||style="text-align: left;" | {{color|#443A3B}} | | 68 || 58 || 59 ||style="text-align: left;" | {{color|#443A3B}}{{Until|BE 26.50}} | ||
{{color|#8F727D}}{{Upcoming|BE 26.50}} | |||
| 17 || 14 || 14 || style="text-align: left;" | {{color|#110E0E}} | | 17 || 14 || 14 || style="text-align: left;" | {{color|#110E0E}} | ||
| — | | — | ||
| Line 182: | Line 198: | ||
| <code>§m</code> | | <code>§m</code> | ||
| <code>material_redstone</code> | | <code>material_redstone</code> | ||
| 151 || 22 || 7 ||style="text-align: left;" | {{color|#971607}} | | 151 || 22 || 7 ||style="text-align: left;" | {{color|#971607}}{{Until|BE 26.50}} | ||
{{color|#EE222C}}{{Upcoming|BE 26.50}} | |||
| 37 || 5 || 1 || style="text-align: left;" | {{color|#250501}} | | 37 || 5 || 1 || style="text-align: left;" | {{color|#250501}} | ||
| — | | — | ||
| Line 189: | Line 206: | ||
| <code>§n</code> | | <code>§n</code> | ||
| <code>material_copper</code> | | <code>material_copper</code> | ||
| 180 || 104 || 77 ||style="text-align: left;" | {{color|#B4684D}} | | 180 || 104 || 77 ||style="text-align: left;" | {{color|#B4684D}}{{Until|BE 26.50}} | ||
{{color|#C87363}}{{Upcoming|BE 26.50}} | |||
| 45 || 26 || 19 || style="text-align: left;" | {{color|#2D1A13}} | | 45 || 26 || 19 || style="text-align: left;" | {{color|#2D1A13}} | ||
| — | | — | ||
| Line 196: | Line 214: | ||
| <code>§p</code> | | <code>§p</code> | ||
| <code>material_gold</code> | | <code>material_gold</code> | ||
| 222 || 177 || 45 ||style="text-align: left;" | {{color|#DEB12D}} | | 222 || 177 || 45 ||style="text-align: left;" | {{color|#DEB12D}}{{Until|BE 26.50}} | ||
{{color|#FFBF1E}}{{Upcoming|BE 26.50}} | |||
| 55 || 44 || 11 || style="text-align: left;" | {{color|#372C0B}} | | 55 || 44 || 11 || style="text-align: left;" | {{color|#372C0B}} | ||
| — | | — | ||
| Line 203: | Line 222: | ||
| <code>§q</code> | | <code>§q</code> | ||
| <code>material_emerald</code> | | <code>material_emerald</code> | ||
| 17 || 159 || 54 ||style="text-align: left;" | {{color|#119F36}} | | 17 || 159 || 54 ||style="text-align: left;" | {{color|#119F36}}{{Until|BE 26.50}} | ||
{{color|#13A045}}{{Upcoming|BE 26.50}} | |||
| 4 || 40 || 13 || style="text-align: left;" | {{color|#04280D}} | | 4 || 40 || 13 || style="text-align: left;" | {{color|#04280D}} | ||
| — | | — | ||
| Line 210: | Line 230: | ||
| <code>§s</code> | | <code>§s</code> | ||
| <code>material_diamond</code> | | <code>material_diamond</code> | ||
| 44 || 186 || 168 ||style="text-align: left;" | {{color|#2CBAA8}} | | 44 || 186 || 168 ||style="text-align: left;" | {{color|#2CBAA8}}{{Until|BE 26.50}} | ||
{{color|#5FECFF}}{{Upcoming|BE 26.50}} | |||
| 11 || 46 || 42 || style="text-align: left;" | {{color|#0B2E2A}} | | 11 || 46 || 42 || style="text-align: left;" | {{color|#0B2E2A}} | ||
| — | | — | ||
| Line 217: | Line 238: | ||
| <code>§t</code> | | <code>§t</code> | ||
| <code>material_lapis</code> | | <code>material_lapis</code> | ||
| 33 || 73|| 123 ||style="text-align: left;" | {{color|#21497B}} | | 33 || 73|| 123 ||style="text-align: left;" | {{color|#21497B}}{{Until|BE 26.50}} | ||
{{color|#577BFF}}{{Upcoming|BE 26.50}} | |||
| 8 || 18 || 30 || style="text-align: left;" | {{color|#08121E}} | | 8 || 18 || 30 || style="text-align: left;" | {{color|#08121E}} | ||
| — | | — | ||
| Line 224: | Line 246: | ||
| <code>§u</code> | | <code>§u</code> | ||
| <code>material_amethyst</code> | | <code>material_amethyst</code> | ||
| 154 || 92 || 198 ||style="text-align: left;" | {{color|#9A5CC6}} | | 154 || 92 || 198 ||style="text-align: left;" | {{color|#9A5CC6}}{{Until|BE 26.50}} | ||
{{color|#B66CDD}}{{Upcoming|BE 26.50}} | |||
| 38 || 23 || 49 || style="text-align: left;" | {{color|#261731}} | | 38 || 23 || 49 || style="text-align: left;" | {{color|#261731}} | ||
| — | | — | ||
| Line 231: | Line 254: | ||
| <code>§v</code> | | <code>§v</code> | ||
| <code>material_resin</code> | | <code>material_resin</code> | ||
| 235 || 114 || 20 ||style="text-align: left;" | {{color|#EB7114}} | | 235 || 114 || 20 ||style="text-align: left;" | {{color|#EB7114}}{{Until|BE 26.50}} | ||
{{color|#FF6A00}}{{Upcoming|BE 26.50}} | |||
| 59 || 29 || 5 || style="text-align: left;" | {{color|#3B1D05}} | | 59 || 29 || 5 || style="text-align: left;" | {{color|#3B1D05}} | ||
| — | | — | ||
| Line 237: | Line 261: | ||
|- | |- | ||
| <code>§w</code> | | <code>§w</code> | ||
| <code> | | <code>party_blue</code> | ||
| 140 || 179 || 255 || style="text-align: left;" | {{color|#8CB3FF}} | | 140 || 179 || 255 || style="text-align: left;" | {{color|#8CB3FF}} | ||
| 35 || 45 || 64 || style="text-align: left;" | {{color|#232D40}} | | 35 || 45 || 64 || style="text-align: left;" | {{color|#232D40}} | ||
| Line 280: | Line 304: | ||
The random characters placed after <code>§k</code> are always the same width as the original characters. For example, any random character cycled through in place of the letter "m" would be a wide character while any random character in place of the letter "i" would be a narrow character. | The random characters placed after <code>§k</code> are always the same width as the original characters. For example, any random character cycled through in place of the letter "m" would be a wide character while any random character in place of the letter "i" would be a narrow character. | ||
<code>§r</code> resets the styles of following characters; e.g., <code>§nXXX§rYYY</code> displays as <span class="format-f" style="font-family: Minecraft"><u>XXX</u>YYY</span>, which can be used to remove the default italics formatting when renaming an item in an [[Minecraft: | <code>§r</code> resets the styles of following characters; e.g., <code>§nXXX§rYYY</code> displays as <span class="format-f" style="font-family: Minecraft"><u>XXX</u>YYY</span>, which can be used to remove the default italics formatting when renaming an item in an [[Minecraft:anvil]].{{only|be}} | ||
=== Typing === | === Typing === | ||
| Line 287: | Line 311: | ||
* If <code>EnableHexNumpad</code> is enabled in the Windows registry, {{keys|Alt+NUMPAD<nowiki>+</nowiki>|A|NUMPAD7}} (using the main keyboard for "A") works for any language due to it being Unicode. | * If <code>EnableHexNumpad</code> is enabled in the Windows registry, {{keys|Alt+NUMPAD<nowiki>+</nowiki>|A|NUMPAD7}} (using the main keyboard for "A") works for any language due to it being Unicode. | ||
* On a Mac with a US keyboard, type {{keys|Option+6}} (or {{keys|Option+5}} for US Extended). For any other keyboard, type {{keys|Option+0|0|a|7}}. | * On a Mac with a US keyboard, type {{keys|Option+6}} (or {{keys|Option+5}} for US Extended). For any other keyboard, type {{keys|Option+0|0|a|7}}. | ||
* On Linux with the [[Minecraft:wikipedia:Compose key|compose key]] activated, type {{keys|Compose|s|o}}. The symbol can also be typed by using Unicode shortcuts: {{keys|Control+Shift+u|a|7|Enter}} | * On Linux with the [[Minecraft:wikipedia:Compose key|compose key]] activated, type {{keys|Compose|s|o}}. The symbol can also be typed by using Unicode shortcuts: {{keys|Control+Shift+u|a|7|Return}}.{{info needed|does Numpad Enter also work?}} | ||
* For various Android keyboards: | * For various Android keyboards: | ||
** Google Keyboard (GBoard): The "§" is in the More Symbols section the symbols. To access it, press the Numbers and Symbols button (?123), then press the More Symbols button (=\<). Note that on previous versions of GBoard, it was behind the Paragraph Symbol "¶" in the same position, but they were | ** Google Keyboard (GBoard): The "§" is in the More Symbols section the symbols. To access it, press the Numbers and Symbols button (?123), then press the More Symbols button (=\<). Note that on previous versions of GBoard, it was behind the Paragraph Symbol "¶" in the same position, but they were since swapped so that now "¶" is behind "§". | ||
** Samsung Keyboard: The "§" is under the "s" key. To access, hold down on the "s" and then slide over to the "§" mark. | ** Samsung Keyboard: The "§" is under the "s" key. To access, hold down on the "s" and then slide over to the "§" mark. | ||
* For iOS: | * For iOS: | ||
| Line 302: | Line 326: | ||
When part of [[Minecraft:JSON text|JSON]] text, the symbol can be written as {{code|\u00A7}} or {{code|\u00a7}}. | When part of [[Minecraft:JSON text|JSON]] text, the symbol can be written as {{code|\u00A7}} or {{code|\u00a7}}. | ||
Alternatively {{in|be}}, the character can be copied from this page (<code>§</code>) and pasted into virtually any text field by pressing {{keys| | Alternatively {{in|be}}, the character can be copied from this page (<code>§</code>) and pasted into virtually any text field by pressing {{keys|Control+V}} (Windows) or {{keys|Command+V}} (macOS). If pasting does not work it may be necessary to use the JSON format or another method. | ||
While in chat in | While in chat {{in|je}}, usage of this character disconnects the user, even in 'offline' single player mode, and thus cannot be used directly in commands such as <code>/say</code>. | ||
=== Sample text === | === Sample text === | ||
The following text can be pasted into a [[Minecraft:Book and Quill]] {{ | The following text can be pasted into a [[Minecraft:Book and Quill|book and quill]] {{in|be}} to produce what is shown in the picture; strikethrough and underlined text appears colored instead. | ||
{| | {| | ||
| Line 334: | Line 358: | ||
''Note: The dice icon highlights text, which, in the real game, will appear as obfuscated text.'' | ''Note: The dice icon highlights text, which, in the real game, will appear as obfuscated text.'' | ||
{{Calculator|formattingCodeEditor}} | {{Calculator|formattingCodeEditor}} | ||
== Use in custom language packs == | == Use in custom language packs == | ||
| Line 406: | Line 372: | ||
The player can also use a resource pack with <samp>§</samp> character(s) already present in the world name, and in this case, when creating a new world, all the player has to do is to change the color codes after the <samp>§</samp> characters. | The player can also use a resource pack with <samp>§</samp> character(s) already present in the world name, and in this case, when creating a new world, all the player has to do is to change the color codes after the <samp>§</samp> characters. | ||
{{IN|bedrock}}, the player is allowed to use a <samp>§</samp> inside of the world name when creating the world. This allows for using custom colors and formatting codes inside of the world name without having to modify the game. However, because most menu screens displaying world names use [[Minecraft:Ore UI]], it is rarely visible in-game. Exceptions include | {{IN|bedrock}}, the player is allowed to use a <samp>§</samp> inside of the world name when creating the world. This allows for using custom colors and formatting codes inside of the world name without having to modify the game. However, because most menu screens displaying world names use [[Minecraft:Ore UI]], it is rarely visible in-game. Exceptions include the ''[[Minecraft:Editor]]'' and some world selection menus. | ||
== Use in server names == | == Use in server names == | ||
| Line 414: | Line 380: | ||
== History == | == History == | ||
{{cleanup|section=1}} | |||
{{ | |||
=== ''Java Edition'' === | |||
{{info needed section|Old text said obfuscated text was "followed by <code>@~</code> in older versions" - was this ever the case and when did it change?}} | |||
[[File:Obfuscated Text Comparison.gif|thumb|250px|Appearance of <code>1234567890abcdefghijklmnopqrstuvwxyz~!@#$%^&*()-=_+{}[]</code> as obfuscated text in four different versions.]] | |||
{{HistoryTable | |||
|{{HistoryLine|java classic}} | |||
|{{HistoryLine||0.0.16a_02|Added formatting codes for 16 different colors, initially using the ampersand ({{cd|&}}) character.{{note|May have actually been added anywhere between [[Minecraft:0.0.15a (Multiplayer Test 2)]] and [[Minecraft:0.0.16a_01]], but it can not be verified as these versions are currently [[Minecraft:Missing Java Edition versions|lost]].}}}} | |||
|{{HistoryLine|java indev}} | |||
|{{HistoryLine||unknown|Formatting codes no longer function, though the game still parses them and skips rendering the formatting code itself.{{check version|might have been infdev, hard to tell because there's barely anything in these versions that draws user provided text}}}} | |||
|{{HistoryLine|java alpha}} | |||
|{{HistoryLine||v1.0.10|The game now parses formatting codes using the section sign ({{cd|§}}) instead of the ampersand ({{cd|&}}), though this still doesn't actually color the text.}} | |||
|{{HistoryLine||v1.0.12|Formatting codes once again function to color text. | |||
|The available colors have undergone minor changes compared to Classic - dark colors were made slightly lighter, light colors were made slightly darker, and color 6 was changed completely from {{color|#BFBF00}} to {{color|#FFAA00}}.}} | |||
|{{HistoryLine|java}} | |||
|{{HistoryLine||1.0|dev=Beta 1.9 Prerelease 6|Added the obfuscated formatting code for use in the [[Minecraft:end poem]].|In addition to randomizing the characters displayed, obfuscated text in this version also randomly alternates between the blue and dark gray colors, overriding the underlying text color.}} | |||
|{{HistoryLine||1.1|dev=11w49a|As a result of an internal rewrite to text rendering, obfuscated text now uses the regular color of the underlying text instead of cycling colors.}} | |||
|{{HistoryLine||1.2.4|dev=release|Added bold, italic, underline, and strikethrough formatting codes.}} | |||
|{{HistoryLine||1.3.1|dev=12w17a|Added [[Minecraft:books and quills]], which allow typing formatting codes without the use of external tools.}} | |||
|{{HistoryLine||1.7.2|dev=unknown|Added additional characters to the non-Unicode set supported by the game, which can now appear in obfuscated text.{{info needed|What characters were added exactly?}}}} | |||
|{{HistoryLine||1.13|dev=unknown|Obfuscated text now only cycles through characters in the [[Minecraft:wikipedia:ASCII#Character_set|ASCII]] set.{{info needed|Old text said: "Nevertheless, an obfuscated character can still add a character to its loop. If a character that matches its dimensions was written into the chat by a player, it is inserted to the loop automatically." Does it only cycle through unicode characters currently rendered onscreen? Also, how did it behave before?}}}} | |||
|{{HistoryLine|||dev=unknown|Obfuscated text now cycles through all Unicode characters that are the same width as the original character.}} | |||
|{{HistoryLine||1.21.6|dev=unknown|Removed the ability to type or paste section signs into books, preventing formatting codes from being used here.{{Check version|Original text said "paragraph symbols", is this actually related? I remember formatting codes no longer being typable in books long before this.}}}} | |||
|{{HistoryLine||1.21.9|dev=25w36a|Formatting codes are now stripped from [[Minecraft:code of conduct]] files, preventing them from being used here.}} | |||
}} | |||
{{Notelist}} | |||
=== ''Bedrock Edition'' === | |||
{{info needed section|When was §g added?}} | |||
{{HistoryTable | |||
|{{HistoryLine|bedrock}} | |||
|{{HistoryLine||unknown|Added formatting codes. Unlike Java Edition, they can be typed/pasted into most text fields directly.}} | |||
|{{HistoryLine||1.19|dev=Preview 1.19.80.21|Added {{cd|material_quartz}}, {{cd|material_iron}}, {{cd|material_netherite}}, {{cd|material_redstone}}, {{cd|material_copper}}, {{cd|material_gold}}, {{cd|material_emerald}}, {{cd|material_diamond}}, {{cd|material_lapis}}, and {{cd|material_amethyst}} formatting codes, for use in [[Minecraft:Trimming|trimming]] tooltips.}} | |||
|{{HistoryLine||1.21.50|dev=Preview 1.21.50.25|Added {{cd|material_resin}} formatting code.}} | |||
|{{HistoryLine||26.30|dev=Preview 26.30.27|Added {{cd|party_blue_color}} formatting code for [[Minecraft:party]] members nicknames.}} | |||
|{{HistoryLine||26.50|dev=Preview 26.50.24|Changed the color of the {{cd|blue}} formatting code from {{color|#5555FF}} to {{color|#447FFF}}.|Changed the colors of the material formatting codes: | |||
* {{cd|§h}} from {{color|#E3D4D1}} to {{color|#D9CCB8}} | |||
* {{cd|§i}} from {{color|#CECACA}} to {{color|#A9B4B7}} | |||
* {{cd|§j}} from {{color|#443A3B}} to {{color|#8F727D}} | |||
* {{cd|§m}} from {{color|#971607}} to {{color|#EE222C}} | |||
* {{cd|§n}} from {{color|#B4684D}} to {{color|#C87363}} | |||
* {{cd|§p}} from {{color|#DEB12D}} to {{color|#FFBF1E}} | |||
* {{cd|§q}} from {{color|#119F36}} to {{color|#13A045}} | |||
* {{cd|§s}} from {{color|#2CBAA8}} to {{color|#5FECFF}} | |||
* {{cd|§t}} from {{color|#21497B}} to {{color|#577BFF}} | |||
* {{cd|§u}} from {{color|#9A5CC6}} to {{color|#B66CDD}} | |||
* {{cd|§v}} from {{color|#EB7114}} to {{color|#FF6A00}}}} | |||
}} | |||
== Trivia == | == Trivia == | ||
* The first 16 color codes almost exactly match, in order, the 16 colors available using a [[Minecraft:wikipedia:Color Graphics Adapter#Color palette|Color Graphics Adapter (CGA)]], as released in 1981. Only color 6 differs; the value for color 6 in Minecraft – {{color|#FFAA00}} – differs from that made for CGA – {{color|#AA5500}}. | * The first 16 color codes almost exactly match, in order, the 16 colors available using a [[Minecraft:wikipedia:Color Graphics Adapter#Color palette|Color Graphics Adapter (CGA)]], as released in 1981. Only color 6 differs; the value for color 6 in Minecraft – {{color|#FFAA00}} – differs from that made for CGA – {{color|#AA5500}}. | ||
* Obfuscated format (§k) displays as dots in ''[[Minecraft:Bedrock Edition]]'' if any font except Mojangles is used. | * Obfuscated format (<code>§k</code>) displays as dots in ''[[Minecraft:Bedrock Edition]]'' if any font except Mojangles is used. | ||
== References == | == References == | ||
Latest revision as of 11:10, 6 September 2026
|
For the {{{Description}}} of the same name, see [[{{{Destination}}}]]. |
Template:Redirect Template:Deprecated feature
Formatting codes add color and modifications to text in-game.
Text in Minecraft can be formatted with the Template:W (§). Template:IN, the section sign can be used in almost any in-game text input such as book and quills and the Minecraft:chat. Template:IN, section signs may only be used in text outside gameplay, such as Minecraft:resource packs and world titles.
Usage
Text can be formatted using the section sign (§) followed by a character. A § symbol followed by a character in the message tells the client to switch colors while displaying text.
Java Edition
Formatting codes can be used in server.properties, pack.mcmeta, splashes.txt, Minecraft:language files, world titles, commands such as /tellraw and /title in data packs, and server names.
If a color code is used after a formatting code, the formatting code is disabled beyond the color code point. For example, §cX§nY displays as XY, whereas §nX§cY displays as XY. Therefore, when using a color code in tandem with a formatting code, ensure the color code is used first and reuse the formatting code when changing colors. Also, you could put §r§f in an anvil to rename an item as non-italic.
Bedrock Edition
Formatting codes can be used in any text input, but will only be displayed in JSON UI. Additionally, Realm names and player names disallow formatting codes. This practically limits formatting codes to the following uses:
- Book and quill text, name, and author.
- Minecraft:Chat messages, including those sent by commands like Template:Command.
- Minecraft:Signs and Minecraft:hanging signs, without requiring dyes.
- Minecraft:Anvils and cartography tables to rename Minecraft:items. Nameplates from Minecraft:name tags or other means also display formatting.
- Text in Minecraft:resource packs displayed in-game, like language files, Minecraft:splashes, Minecraft:loading tips, and Minecraft:credits.
- Pack names, descriptions, and settings strings.
- Commands that can display text, like Template:Command but also Template:Command.
- Technically world names and server names, but these are rarely displayed in JSON UI.
Formatting codes persist after a color code. Usage in Minecraft:party chat censors the entire message.
Color codes
Messages sent from the server to the client can contain color codes, which allow the coloring of text for various purposes.
| Code | Name | Foreground color | Background color | Equivalent ANSI escape code | Version | ||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| R | G | B | Hex | R | G | B | Hex | ||||
§0
|
black
|
0 | 0 | 0 | Template:Color | 0 | 0 | 0 | Template:Color | \e[0;30m
|
|
§1
|
dark_blue
|
0 | 0 | 170 | Template:Color | 0 | 0 | 42 | Template:Color | \e[0;34m
|
|
§2
|
dark_green
|
0 | 170 | 0 | Template:Color | 0 | 42 | 0 | Template:Color | \e[0;32m
|
|
§3
|
dark_aqua
|
0 | 170 | 170 | Template:Color | 0 | 42 | 42 | Template:Color | \e[0;36m
|
|
§4
|
dark_red
|
170 | 0 | 0 | Template:Color | 42 | 0 | 0 | Template:Color | \e[0;31m
|
|
§5
|
dark_purple
|
170 | 0 | 170 | Template:Color | 42 | 0 | 42 | Template:Color | \e[0;35m
|
|
§6
|
gold
|
255 | 170 | 0 | Template:Color | 64 | 42 | 0 | Template:Color | \e[0;33m
|
|
§7
|
gray
|
170 | 170 | 170 | Template:Color | 42 | 42 | 42 | Template:Color | \e[0;37m
|
Template:Only |
| 198 | 198 | 198 | Template:Color | 49 | 49 | 49 | Template:Color | Template:Only | |||
§8
|
dark_gray
|
85 | 85 | 85 | Template:Color | 21 | 21 | 21 | Template:Color | \e[0;90m
|
|
§9
|
blue
|
85 | 85 | 255 | Template:ColorTemplate:Until | 21 | 21 | 63 | Template:Color | \e[0;94m
|
|
§a
|
green
|
85 | 255 | 85 | Template:Color | 21 | 63 | 21 | Template:Color | \e[0;92m
|
|
§b
|
aqua
|
85 | 255 | 255 | Template:Color | 21 | 63 | 63 | Template:Color | \e[0;96m
|
|
§c
|
red
|
255 | 85 | 85 | Template:Color | 63 | 21 | 21 | Template:Color | \e[0;91m
|
|
§d
|
light_purple
|
255 | 85 | 255 | Template:Color | 63 | 21 | 63 | Template:Color | \e[0;95m
|
|
§e
|
yellow
|
255 | 255 | 85 | Template:Color | 63 | 63 | 21 | Template:Color | \e[0;93m
|
|
§f
|
white
|
255 | 255 | 255 | Template:Color | 63 | 63 | 63 | Template:Color | \e[0;97m
|
|
§g
|
minecoin_gold
|
221 | 214 | 5 | Template:Color | 55 | 53 | 1 | Template:Color | — | Template:Only Unavailable on Playstation. |
§h
|
material_quartz
|
227 | 212 | 209 | Template:ColorTemplate:Until | 56 | 53 | 52 | Template:Color | — | Template:Only |
§i
|
material_iron
|
206 | 202 | 202 | Template:ColorTemplate:Until | 51 | 50 | 50 | Template:Color | — | Template:Only |
§j
|
material_netherite
|
68 | 58 | 59 | Template:ColorTemplate:Until | 17 | 14 | 14 | Template:Color | — | Template:Only |
§m
|
material_redstone
|
151 | 22 | 7 | Template:ColorTemplate:Until | 37 | 5 | 1 | Template:Color | — | Template:Only |
§n
|
material_copper
|
180 | 104 | 77 | Template:ColorTemplate:Until | 45 | 26 | 19 | Template:Color | — | Template:Only |
§p
|
material_gold
|
222 | 177 | 45 | Template:ColorTemplate:Until | 55 | 44 | 11 | Template:Color | — | Template:Only |
§q
|
material_emerald
|
17 | 159 | 54 | Template:ColorTemplate:Until | 4 | 40 | 13 | Template:Color | — | Template:Only |
§s
|
material_diamond
|
44 | 186 | 168 | Template:ColorTemplate:Until | 11 | 46 | 42 | Template:Color | — | Template:Only |
§t
|
material_lapis
|
33 | 73 | 123 | Template:ColorTemplate:Until | 8 | 18 | 30 | Template:Color | — | Template:Only |
§u
|
material_amethyst
|
154 | 92 | 198 | Template:ColorTemplate:Until | 38 | 23 | 49 | Template:Color | — | Template:Only |
§v
|
material_resin
|
235 | 114 | 20 | Template:ColorTemplate:Until | 59 | 29 | 5 | Template:Color | — | Template:Only |
§w
|
party_blue
|
140 | 179 | 255 | Template:Color | 35 | 45 | 64 | Template:Color | — | Template:Only |
Formatting codes
| Code | Name | Equivalent ANSI escape code | Version |
|---|---|---|---|
§k |
obfuscated | — | |
§l |
bold | \e[1m
|
|
§m |
\e[9m
|
Template:Only | |
§n |
underlined | \e[4m
|
Template:Only |
§o |
italic | \e[3m
|
|
§r |
reset | \e[0m
|
The random characters placed after §k are always the same width as the original characters. For example, any random character cycled through in place of the letter "m" would be a wide character while any random character in place of the letter "i" would be a narrow character.
§r resets the styles of following characters; e.g., §nXXX§rYYY displays as XXXYYY, which can be used to remove the default italics formatting when renaming an item in an Minecraft:anvil.Template:Only
Typing
- To enter "§" on Windows with most US/UK English keyboards type Template:Keys (alt code on cp437) or Template:Keys. For any other keyboard, the Windows ANSI version Template:Keys often works.
- If
EnableHexNumpadis enabled in the Windows registry, Template:Keys (using the main keyboard for "A") works for any language due to it being Unicode. - On a Mac with a US keyboard, type Template:Keys (or Template:Keys for US Extended). For any other keyboard, type Template:Keys.
- On Linux with the compose key activated, type Template:Keys. The symbol can also be typed by using Unicode shortcuts: Template:Keys.Template:Info needed
- For various Android keyboards:
- Google Keyboard (GBoard): The "§" is in the More Symbols section the symbols. To access it, press the Numbers and Symbols button (?123), then press the More Symbols button (=\<). Note that on previous versions of GBoard, it was behind the Paragraph Symbol "¶" in the same position, but they were since swapped so that now "¶" is behind "§".
- Samsung Keyboard: The "§" is under the "s" key. To access, hold down on the "s" and then slide over to the "§" mark.
- For iOS:
- On the iPad the "§" is under the percent sign. To access, tap the number/symbol button and then swipe down on the percent sign.
- On the iPhone the "§" is under the ampersand "&". To access, tap the number/symbol button then hold down the ampersand key and slide over to the "§" mark.
- For Xbox:
- On the Xbox One the "§" is under the paragraph mark "¶". To access, use Template:Xbtn, hold down Template:Xbtn while on ¶ until other options pop up. Move the cursor over to the "§" mark and use Template:Xbtn to select.
- One can also highlight the S key on the standard alphanumeric keyboard, then press and hold Template:Xbtn to reveal several "alternate" characters, including "§". This method also works on the Windows 10 version.
- For Nintendo Switch:
- In the bottom left corner of the keyboard is a language button. Tapping it or pressing Template:Nsbtn on it will open a list of keyboard languages. Scroll down to the bottom and select the "Symbol" keyboard. The "§" character is located on page 2.
When part of JSON text, the symbol can be written as Template:Code or Template:Code.
Alternatively Template:In, the character can be copied from this page (§) and pasted into virtually any text field by pressing Template:Keys (Windows) or Template:Keys (macOS). If pasting does not work it may be necessary to use the JSON format or another method.
While in chat Template:In, usage of this character disconnects the user, even in 'offline' single player mode, and thus cannot be used directly in commands such as /say.
Sample text
The following text can be pasted into a book and quill Template:In to produce what is shown in the picture; strikethrough and underlined text appears colored instead.
| File:Minecraft Formatting.gif |
§nMinecraft Formatting§r §00 §11 §22 §33 §44 §55 §66 §77 §88 §99 §aa §bb §cc §dd §ee §ff §rk §kMinecraft §rl §lMinecraft §rm §mMinecraft §rn §nMinecraft §ro §oMinecraft §rr §rMinecraft |
Formatting code editor
This tool converts input text into plain text with formatting codes.
Note: The dice icon highlights text, which, in the real game, will appear as obfuscated text. Template:Calculator
Use in custom language packs
Formatting codes can be used to color names and description in language files by using § then any of the numbers/letters displayed above. This is also used in end.txt and credits.txt. An example of this is §dDiamond to make the name of a diamond appear as Diamond.
§r cannot be used to remove italics from custom translation tags within language files. For example, if the translation tag "item.example.test": "§rTest Item" is applied to the Name display data of a custom item ({display:{Name:'{translate:"item.example.test"}'}), it still appears as Test Item rather than simply Test Item. This is not true of any other formatting options.
Use in world names
Template:IN, with the help of external tools, such as NBTExplorer, world names can have custom colors and formatting codes. To modify the name, choose the LevelName tag in the world's level.dat. For example, the LevelName tag can be set to §1R§2e§3d§4s§5t§6o§7n§8e §9C§ar§be§ca§dt§ei§fo§1n§2s to make the world name a colorful one.
Additionally, the player can rename the world's folder to contain the codes. Then, in the world selection menu, the specified colors or effects will appear.
The player can also use a resource pack with § character(s) already present in the world name, and in this case, when creating a new world, all the player has to do is to change the color codes after the § characters.
Template:IN, the player is allowed to use a § inside of the world name when creating the world. This allows for using custom colors and formatting codes inside of the world name without having to modify the game. However, because most menu screens displaying world names use Minecraft:Ore UI, it is rarely visible in-game. Exceptions include the Minecraft:Editor and some world selection menus.
Use in server names
With the use of a third party tool such as NBTExplorer, server names can have custom colors. To utilize this functionality, select the Template:Cd attribute in the Template:Cd file inside the Template:Cd directory using a third party tool. In the following example, the Template:Cd tag is set to
§4§lMinecraft §6§lServer:
History
Java Edition
1234567890abcdefghijklmnopqrstuvwxyz~!@#$%^&*()-=_+{}[] as obfuscated text in four different versions.Bedrock Edition
Trivia
- The first 16 color codes almost exactly match, in order, the 16 colors available using a Color Graphics Adapter (CGA), as released in 1981. Only color 6 differs; the value for color 6 in Minecraft – Template:Color – differs from that made for CGA – Template:Color.
- Obfuscated format (
§k) displays as dots in Minecraft:Bedrock Edition if any font except Mojangles is used.
References
Template:Navbox Java Edition technical Template:Navbox Minecraft
Minecraft:de:Formatierungscodes Minecraft:es:Códigos de formato Minecraft:fr:Codes de mise en forme Minecraft:it:Codici di formattazione Minecraft:ja:装飾コード Minecraft:ko:형식화 부호 Minecraft:pl:Kody formatowania Minecraft:pt:Códigos de formatação Minecraft:ru:Форматирование текста Minecraft:uk:Коди форматування Minecraft:zh:格式化代码