Chorus flowers are plants that are found in the End. They grow on chorus plants.
Obtaining
Chorus flowers can be mined with any tool and will drop themselves when broken. They will not drop anything when pushed by a piston or water, or when their supporting block is destroyed.
| Block | Chorus Flower | |
|---|---|---|
| Hardness | 0.4 | |
| Tool | ||
| Breaking time[A] | ||
| Default | 0.6 | |
| Wooden | 0.3 | |
| Stone | 0.15 | |
| Iron | 0.1 | |
| Diamond | 0.1 | |
| Netherite | 0.1 | |
| Golden | 0.05 | |
- ↑ Times are for unenchanted tools as wielded by players with no status effects, measured in seconds. For more information, see Breaking § Speed.
Natural generation
Chorus flowers are naturally generated in the End at the top of chorus plants, in their fully-grown state.
Farming
Chorus flowers can be planted and will grow in any dimension, regardless of light level. A flower will no longer grow once it has reached age 5 (appearing purple rather than white), but may be harvested and replanted to reset the age.
Usage
Chorus flowers are used to grow chorus plants. They can be planted on end stone in any dimension.
Placement and growth
Chorus flowers must be above end stone or chorus plant, or be above air and horizontally adjacent to exactly one chorus plant. If these conditions are not met, the block breaks without dropping anything.
Each block tick until the flower reaches age 5, the flower will attempt to grow if the block above is air. The flower will not age if growth is not attempted due to lack of an air block above.
The flower may attempt to grow upwards depending on the structure of chorus plant blocks directly beneath:
- 100% chance if zero or one plant block is directly beneath
- 60% if the flower is above a two-block unbranched plant (i.e. two plant blocks over endstone)
- 50% if above a two-block high branch (i.e. two plant blocks over air)
- 40% if above a three-block unbranched plant
- 25% if above a three-block high branch
- 20% if above a four-block unbranched plant
The growth attempt succeeds if the blocks horizontally adjacent to and above the target block above are all air, and results in the target block becoming a flower block with the same age while the existing flower block turns to chorus plant.
If upwards growth does not occur and the flower's age is less than 4, the flower may attempt to branch horizontally. 1–4 branches are attempted on an unbranched plant or 0–3 on a branched plant. For each branch a horizontal direction is chosen at random, and if the block in that direction is an air block with more air blocks on all other horizontal sides and an air block below, it is replaced with a flower with age incremented by 1. If at least one branch succeeds, the original flower block is turned to chorus plant.
If no growth occurs on a growth attempt, the flower's age is set to 5.
Data values
Block state
See also: Block states
| Name | Default value | Allowed values | Description |
|---|---|---|---|
| age | 0
| 01234 | A freshly planted chorus flower starts at age 0. The age is incremented when a chorus flower turns horizontally and/or generates additional chorus flowers on the same plant. |
5 | At age 5, the chorus flower does not grow further. A chorus flower can become age 5 at any time. |
| Name | Metadata Bits | Default value | Allowed values | Values for Metadata Bits |
Description |
|---|---|---|---|---|---|
| age | 0x10x20x4 | 0
| 01234 | 01234 | A freshly planted chorus flower starts at age 0. The age is incremented when a chorus flower turns horizontally and/or generates additional chorus flowers on the same plant. |
5 | 5 | At age 5, the chorus flower does not grow further. A chorus flower can become age 5 at any time. | |||
6789101112131415 | Unsupported | Unused |
History
| release | |||||
|---|---|---|---|---|---|
1.9{{Extension DPL}}<ul><li>[[Debug Stick|Debug Stick]]<br/>{{about|the item|other uses|Debug}}
{{exclusive|java}}
{{Item
| image = Debug Stick.gif
| rarity = Epic
| renewable = No
| stackable = No
}}
The '''debug stick''' is an [[item]] used to edit the [[block states]] of [[block]]s. It is visually identical to a regular [[stick]], but with a glint (as if [[Enchanting|enchanted]]).
== Obtaining ==
The debug stick is obtainable via [[commands]] such as {{cmd|/give}} or {{Cmd|/item}}, or the Creative inventory if the player has the appropriate permissions. It can be obtained only in worlds with cheats on.
== Usage ==
The debug stick can be used to change block states. {{control|Hitting}} the block allows players to select the block state key they wish to change, for an example, switching between the ''conditional'' and the ''facing'' block state keys for a [[command block]]. {{control|Using}} the block allows them to cycle through the valid values for the block state key, again as an example, the player can make the command block face, ''down'', ''east'', ''north'', ''south'', ''up'', or ''west'' if they chose the ''facing'' block state key. {{control|Sneaking}} while {{control|hitting}} or {{control|using}} cycles through the block state keys or values in reverse order.
It is notable that {{Control|using}} debug stick directly on an interactive block without {{Control|sneaking}} uses the block itself instead of the stick.<ref>{{bug|MC-200199}} </ref>
The debug stick cannot be used while in Survival or Adventure mode. It works only in creative mode with cheats enabled. In modes other than Creative, it acts like a regular item — although when {{control|using}} it on a block, the player swings the stick as if interacting with it (but nothing happens).
== Data values ==
=== ID ===
{{ID table
|edition=java
|showforms=y
|generatetranslationkeys=y
|displayname=Debug Stick
|spritetype=item
|nameid=debug_stick
|form=item
|foot=1}}
=== Item data ===
<div class="treeview">
* {{nbt|compound|tag}}: The item's '''tag''' tag.
{{:Player.dat_format/Debug Sticks}}
</div>
== History ==
{{History|java}}
{{History||1.13|snap=17w47a|[[File:Debug Stick.gif|32px]] Added debug sticks.}}
{{History||1.16|snap=20w10a|Debug sticks are now capable of editing [[fire]] due to its added hitbox.}}
{{History||1.19.3|snap=22w44a|The debug stick is now available in the creative inventory, but only if cheats are enabled.}}
{{History|||snap=22w45a|Moved the debug stick behind the Operator Utilities tab in the creative inventory. The tab is only available if cheats are enabled and the "Operator Items Tab" option in the controls menu is turned on.}}
{{History|foot}}
== Issues ==
The debug stick is not supported, and any issues resulting of its usage are closed as "Won't Fix" in the issue tracker.<br/> Issues with the stick itself are considered valid.<ref>https://bugs.mojang.com/browse/MC-122323?focusedCommentId=419481&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-419481</ref><ref>{{reddit|7es23r||Just be aware that any weird state you create with it you cannot naturally create and any bugs that come from it will be shot down as 'Wont fix' :D|_Grum|November 22, 2017}}</ref>
{{issue list}}
== Trivia ==
*An [[add-on]] made by Mineplex was showcased in [[MINECON Live 2019]], which had an editor stick for {{el|be}}, similar to the Debug Stick.<ref>{{ytl|OZqNaEX8208|MINECON Live 2019 @ 1:05:02|Minecraft|September 28, 2019|t=3902}}</ref>
== Gallery ==
<gallery>
Technically Updated.jpg|Artwork of Steve and Alex wielding debug sticks.
</gallery>
== See also ==
*[[Block states]]
== References ==
{{Reflist}}
{{Items}}
[[Category:Non-renewable resources]]
[[de:Debug-Stab]]
[[es:Palo de depuración]]
[[fr:Bâton de débogage]]
[[ja:デバッグ棒]]
[[ko:디버그 막대기]]
[[pl:Patyk debugujący]]
[[pt:Graveto de depuração]]
[[ru:Палка отладки]]
[[zh:调试棒]]</li><li>[[Tag (item)|Tag (item)]]<br/>{{About|the April Fools item|the standard item used to rename mobs|Name Tag}}
{{wip}}
{{joke feature}}
{{exclusive|java}}
{{Item
| title = Tag
| image = Tag.png
| renewable = Yes
| stackable = Yes (64)
}}
Tags and Bits are items exclusive to the [[Java Edition 23w13a or b|23w13a_or_b]] [[Easter eggs#April Fools|April Fools' joke]] snapshot from 2023. They are used to craft in-game representations of [[NBT format|NBT tags]].
==Obtaining==
A [[stonecutter]] can be used to cut a [[Name Tag|name tag]] into either 16 "Name" or 16 "Tag" items. These can be cut into 16 Bit items each.
{{Stonecutting
|head=1
|showdescription=1
|Name Tag
|Name, 16; Tag, 16
|description=The resulting "Name" items must be named in an [[anvil]].
}}
{{Stonecutting
|showdescription=
|Name; Tag
|Bit, 16
|foot=1
}}
To be able to proceed from here the <code>nbt_crafting</code> vote must be approved. Bits can be used in a crafting table to craft Left Curly, Right Curly, Left Square, and Right Square. In appears like these are the only tag items that can be crafted from Bits.
A [[Crafting Table|crafting table]] can be used to convert a "Tag" item into a "Byte Tag." The amount of [[stick]]s added to the crafting recipe specifies the value of the Byte, as a [[wikipedia:Signed number representations#Two's complement|signed 8-bit value]]. For example, a "Tag" and a full stack of sticks make a Byte with the value <code>64b</code>, while 255 sticks result in <code>-1b</code>. Only one of the sticks is consumed. Two Bytes can be crafted into a "Short Tag" (equivalent to 16 bit), two Shorts into an "Int Tag" (equivalent to 32 bit), and two Ints into a "Long Tag" (equivalent to 64 bit). Many other combinations that form either 16, 32, or 64 bit are possible. For example, two Shorts and an Int make a Long. When combining values, their digits are stuck together in the given order, e.g. <code>1b</code> and <code>0b</code> make <code>256s</code> (equivalent to 0100<sub>16</sub> in [[wikipedia:Hexadecimal|hexadecimal]]). Undoing any of these crafting actions in e.g. a stonecutter is not possible.
"Float" and "Double Tags" can be crafted by adding one or two [[boat]]s to any numeric tag. A "String Tag" is crafted with a "Tag" and a piece of [[string]].
{{Crafting
|head=1
|showdescription=1
|A1= Bit; ; Bit; Bit |B1= ; Bit; Bit; Bit
|A2= ; Bit; Bit; |B2= Bit; ; ; Bit
|A3= Bit; ; Bit; Bit |B3= ; Bit; Bit; Bit
|Output= Right Curly; Left Curly; Left Square; Right Square
|ignoreusage=1
}}
{{Crafting
|Tag
|String
|Output= String Tag
|description=String tags must be named in an [[anvil]] to set their value.
|ignoreusage=1
}}
{{Crafting
|Tag; Tag; Tag
|; Stick; Stick, 64
|; ; Stick, 63
|Output= Byte Tag; Byte Tag; Byte Tag
|description=Only 1 stick is consumed. 128 and more sticks make [[wikipedia:Signed number representations#Two's complement|two's complements]]:
128 sticks = <code>-128b</code><br>
129 sticks = <code>-127b</code><br>
⋮<br>
254 sticks = <code>-2b</code><br>
255 sticks = <code>-1b</code>
|ignoreusage=1
}}
{{Crafting
|Byte Tag; Byte Tag; Byte Tag
|Byte Tag; Byte Tag; Byte Tag
| ; Byte Tag; Byte Tag
| ; Byte Tag; Byte Tag
| ; ; Byte Tag
| ; ; Byte Tag
| ; ; Byte Tag
| ; ; Byte Tag
|Output= Short Tag; Int Tag; Long Tag
|description=Shorts and Ints can be combined the same way, even mixed.
Digits are appended, e.g. two <code>1b</code> tags make <code>257b</code> (0101<sub>16</sub> in [[wikipedia:Hexadecimal|hexadecimal]]).
|ignoreusage=1
}}
{{Crafting
|Byte Tag; Short Tag; Int Tag; Long Tag
|Any Boat; Any Boat; Any Boat; Any Boat
|Output= Float Tag; Float Tag; Float Tag; Float Tag
|ignoreusage=1
}}
{{Crafting
|Byte Tag; Short Tag; Int Tag; Long Tag
|Any Boat; Any Boat; Any Boat; Any Boat
|Any Boat; Any Boat; Any Boat; Any Boat
|Output= Double Tag; Double Tag; Double Tag; Double Tag
|ignoreusage=1
}}
{{Crafting
|Left Curly; Left Curly
|Name; Name
|Byte Tag; Byte Tag
|Right Curly; Name |; Byte Tag | |; Name |; Byte Tag |; Right Curly
|Output= Compound Tag; Compound Tag
|description=Instead of Bytes any other tag can be used, including other compound tags.
|ignoreusage=1
}}
{{Crafting
|Left Square; Left Square
|Byte Tag; Byte Tag
|Right Square; Byte Tag |; Byte Tag |; Byte Tag |; Byte Tag |; Byte Tag |; Byte Tag |; Right Square
|Output= List Tag; List Tag
|description=Instead of Bytes any other tag can be used, including other list tags.
|ignoreusage=1
}}
{{Crafting
|Compound Tag; List Tag
|Compound Tag; List Tag
|Output= Compound Tag; List Tag
|description=Up to 9 can be combined.
When compound tags contain identical names, only the latest of the corresponding values is used.
|ignoreusage=1
|foot=1
}}
"Name" and "String Tags" must be named in an [[anvil]] before they can be used. Unnamed Names and Strings always produce a "Sssyntax Error". None of the other tag items can be named.
All these items can be combined in a crafting table to form a short sequence of JSON code, as long as the resulting syntax is valid. For example:
*A pair of Curlies that enclose a named "Name" item and some value, e.g. a Byte, create a "Compound Tag" with the content <code>{Example:0b}</code>.
**Because of the limited size of the crafting table only 3 name-value pairs can be put between Curlies at a time. Compound Tags of any length can be created by concatenating two or more Compound Tags.
**An empty pair of Curlies produces an empty Compound Tag with the content <code>{}</code>.
*A pair of Square brackets that enclose any number of values, e.g. 7 Bytes, create a "List Tag" with the content <code>[0b,0b,0b,0b,0b,0b,0b]</code>.
**Because of the limited size of the crafting table only 7 values can be put between Square brackets at a time. List Tags of any length can be created by concatenating two or more List Tags.
**An empty pair of Square brackets produces an empty List with the content <code>[]</code>.
**"Name" items cannot be used in a List.
The resulting Compound and List Tags can be used as values in other Compound and List Tags, as deeply nested as you want.
==Usage==
Tags appear to have no further functionality. They cannot be eaten or placed in the world, except in an item frame, as each other item can. However, Compound Tags with values like <code>{Enchantments:[{id:"minecraft:sharpness",lvl:127b}]}</code> will show the [[Enchanting|enchantment]] glint and actually act accordingly when used.<ref>https://www.reddit.com/r/Minecraft/comments/129xdyl/i_figure_out_how_the_nbtcrafting_in_the_vote/</ref> This appears to work with many weapon and tool [[Enchanting#Summary of enchantments by item|enchantments]].
In theory, an extremely lucky <code>replace_recipe_output</code> vote can change the crafting recipe for compound tags to output something else. When cheats are enabled you can test this with a command like <code>/vote rule minecraft:replace_recipe_output approve {key:"minecraft:compound_tag",value:"minecraft:netherite_sword"}</code>. However, as long as this vote is approved no other compound tag can be crafted. Use <code>/vote rule minecraft:replace_recipe_output repeal *</code> to undo all recipe replacements.
In combination with the <code>midas_touch</code> vote tag items can be converted into [[Gold Ingot|gold ingots]]. These retain their NBT data. When the world is loaded in another version of the game tag items disappear, but gold ingots persist.
==Trivia==
*This implies that a [[Name Tag|name tag]] is 128 bit.
*Compound and list tags are special in so far that the value they show in their [[tooltip]] is not merely a property of the item, but their ''actual'' [[NBT format|NBT data]]. This is also the reason why naming them is disabled as that would mess up the NBT data.
*The snapshot also contains an [[History of textures/Unused textures|unused texture]] for an {{ItemLink|End Tag}}.
==History==
{{History|java}}
{{History||23w13a_or_b|[[File:Tag.png|32px]] Added tags.}}
{{History|foot}}
==Gallery==
<gallery>
Tag.png|Tag
Bit.png|Bit
Byte Tag.png|Byte Tag
Double Tag.png|Double Tag
End Tag.png|End Tag
Float Tag.png|Float Tag
Int Tag.png|Int Tag
Left Curly.png|Left Curly
Left Square.png|Left Sqaure
List Tag.png|List Tag
Long Tag.png|Long Tag
Name (23w13a or b).png|Name
Right Curly.png|Right Curly
Right Square.png|Right Square
Short Tag.png|Short Tag
Sssyntax Error.png|Sssyntax Error
String Tag.png|String Tag
</gallery>
== References ==
{{reflist}}
{{items}}
{{jokes}}
[[pt:Tag (item)]]
[[Category:Joke items]]</li></ul> | June 22, 2015 | Jeb reveals chorus flowers on Instagram, with the words "MINECON 2015 HYPE!" | |||
| 15w31a | Added chorus flowers. | ||||
| 1.9-pre1 | Chorus flowers in the top of the world do not try to grow anymore. | ||||
Issues
Issues relating to "Chorus Flower" are maintained on the bug tracker. Report issues there.