text stringlengths 0 113k |
|---|
[SOURCE: https://minecraft.wiki/w/Enchanting#cite_note-3] | [TOKENS: 2184] |
Enchanting Enchanting is the process of improving armor, tools, and weapons. A glint animation appears on items to show that they are enchanted. Contents Enchanting equipment Enchanting methods There are four ways to enchant an item in Survival mode: A player may also obtain items already enchanted: Server operators and players in singleplayer worlds with cheats enabled can also enchant items using commands such as /enchant. When enchanted with the /give command, the maximum enchantment level is 255 on Java Edition. In Creative mode, items can be enchanted via an anvil and enchanted books, with no experience points required. Enchanted books are available in the Creative mode inventory, with individual book displays for the highest level of each enchantment and other levels available via the "Search" tab. The enchanted golden apple, despite its name and glint, is not the enchanted form of any item and is completely different from the golden apple. An item can be enchanted by using an enchanting table and placing the item and 1–3 lapis lazuli in the input slots. Upon placing the item, three (pseudo)randomized options appear on the right of the GUI. The glyphs, written in Standard Galactic Alphabet, do not affect the enchantment, but hovering over a presented enchantment shows one enchantment to be applied. On mobile devices, the player can tap an enchantment before putting in the lapis lazuli or hold the enchantment before release. The only choices available have a level requirement equal to or below the player's current level and a lapis lazuli requirement equal to or below the number of lapis lazuli placed in the table. Each option imbues the item with a randomized set of enchantments that are dependent on the number of experience levels required (e.g. a level 30 enchantment can give a pickaxe the "Efficiency IV" enchantment); the actual level cost and the number of lapis lazuli required have no effect. Although the player must have at least the level requirement to get an enchantment, the number of levels that the player is charged is the same as the lapis lazuli requirement. For example, if the third enchantment listed is a level 30 enchantment, the player must have at least 30 levels, but pay only 3 levels and 3 lapis lazuli. The level requirement influences the quantity, type, and level of enchantments instilled in the item, with a higher experience level generally resulting in more and/or higher-level enchantments. Nevertheless, there is a significant random factor, and even a level 30 enchantment (the maximum) doesn't guarantee more than one enchantment, or even that enchantments are "maximum strength" — a level 30 enchantment can still yield Fortune II or Efficiency III alone, for example. On the other hand, multiple different enchantments can be given from one use of the enchanting table. For example, a level 30 enchantment applied to a pickaxe may yield both Efficiency IV and Unbreaking III. However, certain selected enchants never give any additional enchantment, regardless of which tool is enchanted, such as Efficiency IV and Knockback II.[BE only][verify] To increase the enchantment level, bookshelves can be placed next to the enchanting table while keeping one block of air between them. To gain access to the previously mentioned level 30 enchantments, a minimum of 15 bookshelves needs to be placed around the enchanting table. See the Enchantment Mechanics page for more detailed information on this. Enchanting a book produces an enchanted book, which does nothing on its own, but effectively "saves" the enchantment for later application to another item with an anvil. Unlike with an anvil, using the enchanting table while on Creative still costs experience. However, if the player doesn't have enough experience, then experience reduces to zero and the enchantment still works, even when using the enchanting table while already at level zero. Enchanting any item at any enchantment level changes the player's enchantment seed, which changes the possible enchantments for every item at every enchantment level. Thus, if none of the available enchantments for a tool are desired, 1 lapis lazuli and 1 level could be spent to enchant a book or a different tool to refresh the list. The possible enchantments depend on the player's enchantment seed, the item type, and material, and the enchantment level (1–30). The following actions do not affect the possible enchantments: Changing the enchantment levels offered by adding, removing, or blocking bookshelves alters the enchantments shown, but does not change possible enchantments; using another enchanting table with the previous bookshelf number still shows the previous enchantments. The enchantments for a particular enchantment level (with the same seed and item) do also differ depending on which row they appear in, but they are not "better" or "worse" based on the row despite the different resource costs. An anvil can be used to combine the enchantments of two items, sacrificing one of them and repairing the other. The items must be compatible; they must either be the same type and material (such as two iron swords) or an item and an enchanted book with an applicable enchantment (such as a bow and an Infinity enchanted book). Combining two enchanted items, books or one of each with the same enchantment at the same level produces an item or book with the next higher level of that enchantment up to the maximum allowed in Survival mode; for example, a book with Thorns I and Unbreaking II combined with a book with Unbreaking II produces a book with Thorns I and Unbreaking III. To combine items, the player places the target item in the anvil's first slot and the sacrifice item in the second slot. If the combination is allowed, the resulting enchanted item appears in the anvil's output slot and an experience level cost, labeled "Enchantment Cost", appears below (green if the player has enough experience levels, red if they don't). To complete the enchantment, the player removes the enchanted item from the anvil's output slot, and their experience level is reduced accordingly. The experience cost depends on the enchantments, with highly enchanted items costing more. If the target item is also being repaired, that costs more as well. The target item can also be renamed, at additional cost. There is also an accumulating surcharge for prior work done on anvils. In Survival mode, work that costs more than 39 levels of experience is refused, although it may still be possible to perform the same work in steps. For example, a damaged enchanted bow may be repaired on an anvil with an ordinary bow, and then another enchanted bow may be used to combine enchantments with the repaired bow. Enchanted books can be made by enchanting a book in an enchanting table at the cost of experience points. They can also be found in the chests of several structures, purchased with emeralds from a librarian villager, or caught while fishing. Enchanted books can be applied to tools, weapons, and armor, or combined with other enchanted books in an anvil. In this way, some enchantments that cannot normally be obtained on an item through use of the enchanting table can still be applied to those items, such as applying Thorns to boots. Although enchanted books can have multiple enchantments of any type, only enchantments appropriate to a given item type are applied to that item when combined in an anvil. For example, an enchanted book may have both the Respiration and Power enchantments, but the Respiration enchantment is lost if the book is applied to anything but a helmet. Likewise, the Power enchantment is lost if the book is applied to anything but a bow. In Creative mode, enchanted books can be used to apply any enchantment to any item, such as a stick having Knockback II on Java Edition. However, mutually-exclusive enchantments, such as Infinity and Mending, cannot be applied this way or even via /enchant (though both enchantments function as normal when obtained on a bow through the /give command). The experience costs for using books are considerably less than for combining items with similar enchantments since the books themselves cost levels to create. However, it's still an extra cost, and enchanting items directly has a chance to get multiple enchantments. The advantage of books is that they can be stockpiled for use on an item of choice and allow for controlled combinations. For example, a Silk Touch book can be used on an axe, pickaxe, or shovel, and the player can decide which item receives which enchantment. Use Order Calculator to minimize experience loss when merging two items. Disenchanting The main way to disenchant items is via the grindstone or by repairing the items via the crafting grid. Using the grindstone removes all enchantments (except for curses) but gives some experience back based on the level of the enchantment(s) and their value. If a block is placed, it loses all the enchantments it has. Summary of enchantments Each enchantment in the table below includes attributes that are possible for the player to acquire legitimately in Survival mode. Other combinations are possible in Creative mode or with cheats, mods, or third-party software. Summary of enchantments by item Enchantments that have multiple levels are shown with their maximum level numbers. Mutually exclusive enchantments can be combined using commands (e.g., /give @s bow[enchantments={infinity:1,mending:1}]). Also, a player can exceed the maximum levels of enchantments (e.g., /give @s netherite_sword[enchantments={fire_aspect:10}]). However, if that number goes above 10 the translation string is exposed and it looks like this: The tables below summarize the enchantments that can be obtained on specific items in Bedrock Edition and in Java Edition Survival mode (Any enchantment can be applied to any item in Java Edition Creative mode). Enchantments that can be applied to both hand slot items and armor slot items are listed in both tables. Depth Strider (III) Maximum effective values for enchantments The table below shows the effective limits for enchantments (also found here). Mending Data values Java Edition: Bedrock Edition: Sounds Java Edition Bedrock Edition: Videos History Issues Issues relating to "Enchanting", "Enchantment", or "Enchanted" are maintained on the bug tracker. Issues should be reported and viewed there. Gallery Trivia See also References External links Navigation More More Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/File:Chest_(S)_JE2.png] | [TOKENS: 109] |
File:Chest (S) JE2.png Summary Render of a Chest. Animated version: File:Chest.gif. Licensing File history Click on a date/time to view the file as it appeared at that time. You cannot overwrite this file. File usage More than 100 pages use this file. The following list shows the first 100 pages that use this file only. A full list is available. View more links to this file. Global file usage The following other wikis use this file: View more global usage of this file. Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Spear?action=edit§ion=21] | [TOKENS: 223] |
Editing Spear (section) Please note that all contributions to Minecraft Wiki are considered to be released under the CC BY-NC-SA 3.0 license, except for pages imported from wiki.vg or pages derived from such pages, which are considered to be released under the CC BY-SA 3.0 license. See Minecraft Wiki:Copyrights for details. If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here. You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission! You may also post content obtained from Mojang, its websites, manuals and guides, concept art and renderings, press and fansite kits, and other such copyrighted material that Mojang has made available to the general public, to the Minecraft Wiki. All rights, title and interest in and to such content shall remain with Mojang, as applicable, and such content is not licensed pursuant to the Terms of Use. This page is a member of 12 hidden categories: Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Java_Edition_removed_features#Potions] | [TOKENS: 11741] |
Java Edition removed features Since the beginning of the development of Java Edition, there have been a number of features that were removed from the game. These features may have been replaced, or a developer decided against the feature later on. Note: This page documents only game features that were removed; features of a particular game element that were removed are noted in that element's history. See Java Edition unused features for features that are still currently in the game. Contents Blocks Items Mobs Recipes Player features In Survival Test and early Indev versions, the score was displayed in the upper right corner. This was removed in Java Edition Indev 0.31 20100130. In early Indev versions, the player could open the inventory screen and view their name and three stats: "ATK", "DEF", and “SPD”, probably standing for attack, defense, and speed. These existed only briefly; when asked, Notch stated he could not remember exactly why they were implemented and subsequently removed, and he assumed they were placeholders for "vague plans". An inventory rewrite was originally partially implemented in snapshot 14w07a, but it was reverted before the release of 1.8.[more information needed] During Survival Test and early Indev versions, an arrow indicator appeared above the hotbar which indicated how many arrows player has left. Prior to Java Edition Beta 1.8 before hunger bar was added, eating food directly increased health. It was possible to use a sword in main-hand to block attacks with right click. This feature was removed in 1.9 and attacks are now blocked with shield instead. Before 1.6.1, on player death while playing in multiplayer, the player would stay standing, leap a little bit, and then disappear. In 1.6.1, this was replaced with the player falling onto the side and then disappearing. Before the 1.6.1 update, custom player skins would revert to the default Steve skin on the death screen. This feature was removed sometime during the 1.6 full release update's development. Removed in 1.14 for performance reasons. Before changed, the player could not look directly upwards or downwards. Before 1.3.1, players named "Notch" would drop an apple along with the rest of their inventory upon death. Apples were otherwise unobtainable before Beta 1.8 Pre-release. Starting with Classic 0.0.2a, all subsequent versions until RC2 had text displayed in the top left corner of the screen that displayed the version. Versions between Beta 1.6.5 and Beta 1.7.3 did not have this text. From Classic 0.0.2a to Indev 0.31 20100206-1437, only the version number was displayed, but after Indev it switched from being "0.31" to being called "Minecraft Indev" (Indev 20100206-2034), the word "Minecraft" was shown before the version number. In the Alpha development stage, the text read "Minecraft Alpha v#.#.#(_0#)." In the Beta development stage, the text read "Minecraft Beta #.#(_0#)." This feature was only partially removed, for, among other things, the version number can now be shown by opening the debug screen while in-game. Before Alpha v1.2.2, the version number did not display on the main menu screen. From Beta 1.6 Test Build 3 to Beta 1.7.3, a message reading "Minecraft Beta #.#.#(_0#) Unlicensed Copy :( (Or logged in from another location). Purchase at minecraft.net" was shown in the top-left corner if the player was detected to be running an unlicensed or cracked version of the game.[more information needed] This would also force the version number to be displayed, including in Beta 1.6.5 and later which normally had the version number hidden. The message was removed in Beta 1.8. Achievements were available between Beta 1.5 and full release 1.11.2 (snapshot 17w06a). They were ultimately replaced by advancements. Editions other than Java Edition still have achievements instead, although they use a different system, being synced per Xbox Live or PlayStation account and not separated by worlds. Before Alpha v1.0.9, the walking animation for the player and the human mob was different; the player and the human mob would swing their arms wildly to their sides while walking like cartoons. Different versions in Minecraft's history had items pre-spawned in the player's inventory. Here is a table below: Since Java Edition 1.3.1, creating a new world in Creative mode no longer spawns the player with any items in their inventory. High-distance anomalies Many of the game's mechanics would break down in strange ways when at a large distance from the origin of the world. The vast majority of these effects have been patched, or at least minimised, in modern versions. For elements of the game which are integer-aligned, such as the positions of blocks, Java Edition uses integer data types, which can be either 32-bit or 64-bit. 32-bit integers were more commonly used in older versions, which allowed for 4,294,967,296 possible distinct integer values, ranging from -2,147,483,648 to 2,147,483,647. Exceeding these boundaries, such as by using an external editor to move the player to beyond 2,147,483,647 blocks from the origin as to force the game to load blocks beyond this position, often would result in major game-breaking bugs and crashes. Accessing such regions is now much more difficult than it was previously, as distance is now much more restrictive, requiring modifications to the game to allow these limits to be exposed. For elements of the game which are not integer-aligned, such as the positions of entities, Java Edition uses 64-bit floating point (or "double") values for arithmetic and storage of relevant variables. However, there are odd cases in which a 32-bit floating point value is used instead. Such cases are rare in the modern game (a full list of those which still exist in 1.20 can be found at Java Edition distance effects), however older versions of the game used 32-bit values (or unnecessarily casted from and to them, resulting in data loss which could have easily been avoided without this pointless casting) much more heavily, resulting in a plethora of strange gameplay bugs which were tied to how far the player was from the center of the world, getting twice as intense for every integer power of 2 blocks the player went from the center. One of the most notable floating point precision loss bugs is where the rendering of the world stops being accurate depending on the player's position. Commonly experienced alongside (and frequently, and incorrectly, blamed on) the Far Lands, the position at which blocks render does not match up with that of entities and other world elements such as the hitboxes of blocks. At 8,388,608 blocks and beyond, the game assumes the player is standing at the edge or corner of each block, and always renders the blocks of the world as if they player is standing at one of those corners. This effect is difficult to describe in text, and is best experienced firsthand. Most of the other issues regarding floating point imprecision deal with the creation of particles, spawning of entities, and (prior to their standardisation in 1.8 with json files, which fixed all of these permanently) the geometrical distortion of block models. A comprehensive list of since-fixed issues, as well as breakdowns of how they progress, can be found at Java Edition distance effects/Historical effects. Boundary effects refer to oddities which arise due to hardcoded numerical limits in the game, such as the 30 million wall (as opposed to hard limits, which are defined by the programming language and/or computer architecture rather than the game code). The current world boundary as of 1.21 is a "pseudo-wall" which exists at 30 million blocks from the origin, a chunk beyond the world border. (This is defined as a "pseudo-wall" rather than a true wall as rather than being solid and preventing passage like the world border or a solid block does, the player's position is instead set to 30 million by the game if the player attempts to exceed it, which can be seen by the fact that the walking animation, step sounds and view bobbing can still be experienced by walking into the wall, as does the sounds of flying with an elytra.) However, previous versions had much stranger effects at great distances. The world boundary was something commonly experienced in Classic and Indev due to worlds being small by design. The first versions of Infdev, which did away with such boundaries, therefore had no such effects, instead exposing the existing hard limits of the game (although experiencing these was effectively impossible due to floating point bugs rendering the game unplayable much earlier). The version of Infdev released on March 13, 2010 reimplemented a boundary at 32 million blocks, likely to prevent access to the then-relatively-new Far Lands which existed at a bit over 33 million blocks. This boundary was considerably different and buggier than those from Indev, although this was largely to be expected due to it being effectively impossible to reach legitimately. Beyond this 32 million limit, blocks would no longer exist at all, and give way to an empty void. When major changes to world generation brought the Far Lands much closer to the world origin later that same month, however, the world boundary still remained at 32 million, meaning the Far Lands were completely possible to reach without modding the game. Updating blocks next to this void would cause the game to freeze due to it having to calculate an immense amount of lighting updates. This void could still be traversed by entities normally until the April 13 build, in which entities that render it would become stuck in place and jitter eternally. This was later fixed in an unknown version. In Alpha v1.2.0, the boundary effects would get stranger than before. While previously no blocks would render beyond this point, Alpha v1.2.0 and onwards would cause a strange phenomenon in which chunks would appear to generate, but would be intangible, appear fully lit, and generated features such as trees and ores would not generate at all in these chunks. For reasons which remain completely unknown to this day, Beta 1.8 would shrink the world boundaries inwards from 32 million blocks out to only 30 million blocks out. While the effects would remain similar, with blocks beyond the 30 million boundary appearing fully lit and ignoring collision and feature generation, these fake chunks would only generate a small distance out from this boundary, stopping at 30,000,064, or four chunks from the boundary. In addition, any entity attempting to surpass 30,000,032 would again be stuck in a jittery stasis, with players in particular having their heads twist unnaturally if looking around after this point (a bug that was patched in 12w03a, where facing direction would no longer change and preventing this unnatural twisting). With the client-server split in snapshot 12w18a for 1.3 (a change which broke many other things about the game), the stasis bug was actually fixed, and fake chunks could be generated beyond the 30,000,064 point, allowing for the player to keep flying outwards until 32,000,000 blocks, where they would be kicked out of the game due to being in an illegal position, revealing that not all elements of the 32,000,000 limit had been removed from the game yet. 12w27a, a later snapshot for 1.3, would clamp nether portal positions to be within the 30 million limit. 1.7 and 1.8 started to make major changes to the world boundary to bring it to its modern state. 1.7 first made all blocks beyond 30 million completely solid, including air. Said wall could still be surpassed, however, by flying over it, as it only extended to the 32-bit limit on the Y-axis, allowing for 32 million blocks to be reached once more and the illegal position game crash triggered. The boundary became more unstable from version to version throughout 1.8's development, with the end result on its release being that chunks beyond 30 million blocks would no longer render, and teleporting beyond 30 million would crash the game. 1.9 would allow chunks beyond 30 million blocks to render once more, and prevent teleportation beyond 30 million blocks at all. Little has changed about the world boundary between this point and 1.21. The Far Lands were a complex terrain phenomenon which arise due to a major bug in terrain generation works. Generally, "far lands" are the result of what happens when a given noise generator exceeds the largest value it can handle, resulting in an integer overflow and resulting in the generated values reaching unnatural magnitudes. The term "Far Lands" in isolation most commonly refers to what results from "low noise" and "high noise" overflowing simultaneously. Due to many occurrences at high distance being lumped together with each other, confusion often arises as to what is related to or caused by the Far Lands, and what is not. The following is a list of things which are commonly misattributed to being a product, effect or even type of the Far Lands, despite not being so. Precision loss errors are not caused by the Far Lands The position where the world appears to render is considerably offset at the point where the Far Lands begin in Java Edition Beta 1.7.3 and earlier, with a magnitude of one block, with the player appearing to be at the edges and corners of blocks at all times. However, this is purely a floating-point bug, and exists whether or not the Far Lands themselves do. This can be demonstrated by the following: This is also true of every other precision loss bug, especially those which were not fixed in Beta 1.8 and persisted into later versions after the Far Lands were removed in said version, demonstrating that they are two completely different things which are associated with each other due to happening at high distances. The Stripe Lands are not a type of Far Lands The Stripe Lands, a mostly Bedrock Edition-exclusive phenomenon which can be seen in Java Edition only through extensive modding, are another example of floating-point precision loss, and are not a terrain bug. Fake chunks are not caused by the Far Lands "Fake" chunks at the world boundary are another anomaly that happens at high distances. Occurring considerably past the Far Lands' beginning, they are commonly said to be a "part" or "layer" of the Far Lands. While they are among the interesting effects which can be experienced when moving high distances from the world origin, their occurrence is a distinct phenomenon, and, to an extent, actually intended. This is further reinforced by them being at a rather round number (32 million), rather than the seemingly overall arbitrary 12,550,824 of the Far Lands, or power-of-two values such as 16,777,216 where precision loss worsens. Hard limits are not caused by the Far Lands While the Far Lands themselves are technically a hard limit due to arising from integer overflow, they are treated solely as a terrain phenomenon, and the game still functions fine with them. Integer overflows in other cases such as player position are much more dangerous and much harder to reach, and are considered separately. In their most well-known iteration, the Far Lands manifested as a sort of "wall" which would extend from the lowest point of the world to the very top. This wall contained a series of holes in it, with these holes reaching back almost infinitely, with only minor changes even after millions of blocks. The density of a cross-section of this wall was roughly 50%, with solid portions and hollow portions being around equal. Given their positions at the four sides of a world, there regions are often referred to as the "Edge Far Lands" when distinction from other regions of a world is necessary, and, due to their "Swiss cheese"-like formation, informally as "The Loop". Since the Far Lands existed on both the X and Z axes, it is entirely possible for them to "intersect" each other when surpassing their starting point on both axes. The resulting terrain, named the "Corner Far Lands" in analogy to the vertices of a square, is markedly different from that of the edge regions: the world appears to be solid layers of terrain arranged on top of each other with air gaps in between. Due to this distinctive morphology, the Corner Far Lands are also informally referred to as "The Stack". The terrain seen in these regions is comparable to that which is seen in the Nether. Often, major diagonal or oblique patterns can be seen within the generated terrain, which, if they exist, are especially obvious at the beginning of the corner Far Lands. In the unmodified game, only four sets each of the edge and corner Far Lands can exist in a world, from the noise overflowing on the X and Z axes. However, game modifications can modify aspects of either chunk saving or terrain generation in ways that ultimately allows for noise to overflow on the Y axis as well. Such modifications reveal two more sets of Edge Far Lands for a total of six sets (corresponding to the faces of a cube), eight sets of Corner Far Lands from these Y axis Edge Far Lands intersecting X and Z axis Edge Far Lands for a total of twelve sets (corresponding to the edges of a cube), and new regions in which all three axes simultaneously overflow due to Y axis Edge Far Lands intersecting the existing Corner Far Lands, with eight of these regions in total (corresponding to the vertices of a cube). These regions, referred to as the "Vertex Far Lands", are incredibly unstable; sometimes these regions are completely solid, other times are completely empty, and other times still feature incredibly strange terrain atypical of even "The Loop" or "The Stack". With default settings, the noise would overflow at twice the distance on the Y axis as it does on the X and Z axes, at around 25,101,640 blocks. The Farther Lands is the name given to another noise overflow which, by default, happens at a greater distance than the normal Far Lands. Whereas the usual Far Lands arise from the overflowing of "low noise" and "high noise", the Farther Lands sees "selector noise" break down instead. Low noise and high noise are two different noise generators which the game uses to generate the potential fundamental shape of terrain, whereas selector noise chooses whether low noise or high noise is used to actually generate the terrain at that given point. When the conventional Far Lands start, despite both low noise and high noise overflowing simultaneously, selector noise still functions normally, meaning that there is still a large amount of possible variation in the shape of the Far Lands. When selector noise does eventually break, which happens at roughly 1,004,065,920 blocks from the world origin, it follows that the variation between low and high noise also breaks down. Like how the usual Far Lands is a series of straight tunnels, the Farther Lands divides the world into a series of straight regions, with low noise used exclusively in one region and high noise in others. As such, the variation usually seen in the Far Lands vanishes after the Farther Lands. The Corner Farther Lands take this effect to an extreme: while the normal Corner Far Lands are rich in nuance, the Corner Farther Lands are almost devoid of it. The beginning of the corner makes this all the more obvious, and also highlights edge Farther Lands-corner Far Lands intersections, making the aforementioned straight line regions clear to see. Terrain generation was much simpler in versions before March 27, 2010. While in modern versions, the noise generator used for terrain is 3D, earlier versions used a purely 2D noise generator for the world instead. The resulting terrain was much more cliff-based as a result, and overhangs were an impossibility. In addition, noise incremented much slower than the modern noise generator does, resulting in it overflowing at 33,554,432 blocks out (coincidentally a power of 2). Rather than featuring a series of holes, this noise generator instead created a huge, featureless wall as it broke, as the purely 2D nature of the noise forbids any overhangs from generating. This wall is completely solid stone and extends infinitely outwards when it starts. Occasionally, the faces of this wall may appear ridged like a radiator or heat sink, resulting in a slightly more gradual transformation of the terrain. While largely removed as of Beta 1.8, simple modifications to the game can effectively reintroduce them, in which case they behave effectively identically to how they did before, but much more stable due to the fixing of the vast majority of high-distance precision loss effects in earlier versions which caused lag and hindered movement. In addition, several aspects of the Far Lands persisted into later versions: Modding has allowed for y-axis Far and Farther Lands, the Fartherer and Farthest Lands, and 64-bit versions of the Far and Farther Lands (distinct from the Fartherer and Farthest Lands in while they appear at the same locations as them, they result from 64-bit noise breaking normally rather than the modulo that prevents 32-bit noise from breaking itself) to be seen in their natural habitats. Generated structures Brick pyramids were tall experimental generated structures made up exclusively of bricks. They were added in Java Edition Infdev 20100227-1414 and they were removed from the game in Java Edition Infdev 20100327. These were entirely composed of bricks - the pyramids did not have any rooms inside, however caves could generate through them Java Edition Infdev 20100325-1640 due to caves being able to generate through any blocks at the time (including trees and other structures they should not be able to). These were most likely intended for testing structure generation in infinite worlds. As blocks did not drop items at the start of Infdev due to entity code still being reworked, brick blocks could not be collected from pyramids for most of their existence. The starting house was a building which generated at the center of Indev maps. The player would spawn inside of the starting house when the world was first generated. This structure was added in Java Edition Indev 0.31 20100124-2119, and was initially comprised of mossy cobblestone, with two Torches inside. The starting house was reworked in Java Edition Indev 20100213, having a stone floor and walls made of oak planks. Early iterations of the starting house contained a series of chests, which would harbor almost every block and item in the entire game at that point. These chests went through a series of changes, before being removed from the starting house entirely in later iterations. The starting house was removed at Java Edition Infdev 20100227-1414 due to terrain generation being redone to accommodate infinite worlds, ditching the limited worlds of Indev and earlier. In Java Edition Infdev 20100227-1414, two obsidian walls generated in the world as to mark the orthogonal directions. One of these walls would appear where the X-axis was at 0, and another where the Z-axis was 0. The player would spawn at the point where these two walls intersected. Like with the brick pyramids, these were a debugging feature, and were not implemented as a source of obsidian for players due to the inability for blocks to drop items at the time. These walls would no longer generate as of Java Edition Infdev 20100313. Monoliths were a terrain bug which existed from late Infdev to late Alpha. Occurring when the noise generators for handling the shape of terrain output specific values, these structures would consist of the terrain being "inverted" in a given region of space. Outwardly, they appear as sheer stone cliffs which reach the top of the world. Ore and sediment blobs could be seen to generate in the sides of these, as could water and lava springs. Further examination of these reveal that the area underneath these monoliths is completely empty all the way down to the bedrock layers, further proving that the terrain is "inverted", as air regions and solid regions have completely switched places. Water would generate in this empty space below monoliths, as the game would consider any air space below a given point that did not belong to a cave or other structure as an "ocean", and fill it with water accordingly. Due to being "inverted" sections of terrain, it is exceedingly likely that monoliths would generate up infinitely (or at least up until the vertical Far Lands) were they given sufficient space. Due to their version range, they were limited to 128 blocks. Monoliths could also fully enclose regions of normal terrain - when seen from below, these would appear as sheer cliffs, like all non-monolith terrain. Monoliths came with the Java Edition Infdev 20100611, which overhauled terrain a third time in the Infdev development period, they persisted up until Java Edition Alpha v1.1.2_01. Alpha v1.2.0 redid terrain generation once more, such that completely different noise generators were used for terrain, which no longer had the potential to cause these bugs. However, despite this, Old Customized worlds were still capable of generating monolith structures by defining a negative "Biome Scale Weight" value from snapshot 14w17a for Java Edition 1.8 to snapshot 18w05a for 1.13, prior to the removal of the "Customized" world type altogether in the next 1.13 snapshot 18w06a. Monoliths could also be generated from 1.16 to 1.17.1 by using customized worlds to set a biome's scale to a negative number. There are several cases in the game in which unique species of tree use the logs and leaves primarily associated with other trees. Two prominent examples are pine trees, which use spruce logs and leaves, and swamp trees, which use oak logs and leaves, rather than either of these having dedicated blocks. As a result of this, they cannot be grown from saplings, and can only be encountered when generating new chunks. In Java Edition 1.7.2's development, when biomes were being added to the game, two trees were added to the then-new biomes which also reused the logs and leaves of existing trees. However, these were a temporary measure, as later in development, they were given logs and leaves of their own, alongside saplings, planks and further wood products. Specifically, these were the acacia tree, and the dark oak tree. The acacia tree reused jungle logs and oak leaves, and dark oak trees used spruce logs and oak leaves. Villages have seen multiple changes in generation since their introduction. Due to these changes, some may consider villages which generated in previous versions, or at least certain buildings within them, as "removed" structures. Old villages and old zombie villages could generate in plains, savanna, taiga, and desert biomes. The type of village, and therefore the style of all structures within it, was determined by the biome where the village well was located. All village biome variants were essentially palette swaps of each other. The "old villages" were not known as such until Java Edition 1.14. Before Java Edition 1.10, villages used gravel with cobblestone underneath to signify roads; however, in Java Edition 1.10, grass paths were added to signify village roads. However, grass paths sensibly were only generated where they replaced grass blocks, and gravel paths still existed until Java Edition 1.14, when the jigsaw system broke it. Prior to Java Edition 1.10, plains villages would generate in savanna biomes. Plains villages was replaced by savanna villages made out of acacia derived blocks. Prior to Java Edition 1.3.1, plains villages would generate in desert biomes. Plains villages was replaced by desert villages made out of sandstone derived blocks. Prior to Java Edition 1.8, plains wells would generate in desert villages. Plains wells was replaced by desert wells made out of sandstone derived blocks. Any No Glass Glass pillars were a debug element of end portal rooms used to mark the location of strongholds, since the eye of ender's functionality of pointing toward strongholds did not exist yet. One pillar extended from the main entrance and another from the portal room, both from the Stone Bricks to the build limit. They were accidentally left in the public release of Java Edition Beta 1.9 Prerelease 3, and were removed in the next update. Prior to Java Edition Beta 1.8, clay blobs were a terrain feature that existed as a way for clay blocks to generate naturally. They were removed and clay is now found as disks instead. Prior to Beta 1.8, beaches existed as a terrain feature and generated in two variants (sand beaches and gravel beaches). Beaches were removed in Beta 1.8, then returned as biome in Java Edition 1.1 but without gravel variant. Prior to Java Edition 1.18, water lakes were small bodies of water source blocks in the Overworld. They could generate both on the surface and underground, in the latter case, air pockets would generate above them. Water lakes generated in almost all Overworld biomes (except desert). Water lakes were removed in Java Edition 1.18 and replaced with aquifers. Map settings In Indev versions of Minecraft, it was possible to customize the color of the sky, fog, and clouds via map editing, but this feature was removed in Infdev. Unlike some customizations now available via custom world generation, these are yet to see a return. In the Indev versions of Minecraft, players could take a screenshot of the map from an isometric perspective using F7. When the game captured an isometric image, it would save the current location of all mobs and show any and all alterations to the map the player had made that would be visible from the perspective of the sun (at sunrise). The player would not be visible unless the player was in third-person view before taking the isometric screenshot. The isometric screenshot would save to their local user folder as "mc_map_####.png" where #### represents the number of the screenshot starting at 0000 up to 9999. There are some limitations that existed with the screenshots: This feature was removed in Infdev due to the addition of infinite worlds. Was replaced by Infinite Map Visualizer. During the development of Indev, there were settings to change level's theme, type, shape and size. "Winter Mode" was a randomly occurring map type in Alpha. It was added on July 9, 2010, in Alpha v1.0.4 and was the first "biome" to appear in Minecraft. There were a couple of differences compared to normal worlds. First, there was the presence of snowflakes, which fell constantly. There were four different kinds of snowflakes. These snowflakes would create snow on surfaces directly exposed to the sky, provided that it was a solid block. Due to a lack of unfrozen water, reeds were rare. The second element unique to "Winter Mode" was the presence of ice. When a map was generated, most exposed water blocks would be frozen into ice. The water did not freeze completely near gravel beaches. The third element was a decrease in the spawning rate of passive mobs. Whether a world was in "Winter Mode" was determined with a 25% chance at creation. "Winter Mode" was removed in Alpha v1.2.0 with the addition of proper biomes. The "Default 1.1" world type was added in 1.2.1 (snapshot 12w03a). Initially it was permanently applied to old worlds in order to prevent chunk borders but from snapshot 12w07a onwards, this world type only got used during the conversion process from the Region file format to the Anvil file format which stored biomes in chunk data. After conversion, old worlds would switch back to the default world type which allowed for world generation to create jungles. The world type was accessible in later versions by changing the "generatorName" property in the level.dat of a world created in 1.2 to "default_1_1" and it would persist across world saves. When it was first added, the "Default 1.1" world type was simply the same as the default world type but without jungles. In 1.7.2, it was changed to match the updated biome generation with the only difference being that warm climate regions were replaced with regions containing biomes from 1.1, those being deserts, forests, extreme hills, swamps, plains and taigas. With another biome overhaul occurring in 1.18 (experimental snapshot 1), the "Default 1.1" world type was removed. Versions prior to 1.7.2 had two biomes that were later removed from the world generator. Despite being unused, they continued to exist until Java Edition 1.18, in which mountain edge got removed. The following biomes became unused in 1.7.2: In Beta 1.8, biomes received a major overhaul, removing and changing many of them. Prior to these changes, there were 13 biome types that were much smaller and less distinct. In 1.18, terrain height is no longer controlled by biome, so the following height variations biome have been removed and had their code merged into the main one: "Customized" was a world type that gave control over many settings that affected terrain generation, such as ores, sea level, biomes, structures, and many variables that govern the random shape of the terrain. It was introduced in snapshot 14w17a for 1.8, and was removed in snapshot 18w06a for 1.13. Although customized worlds were added back in the 1.16 snapshot 20w21a, there is currently no in-game menu to modify worlds; custom worlds can be generated only by importing a JSON file. Several historical file formats existed before the current Anvil file format during early development of Minecraft. Sounds Loops were unused sounds, found in the game files, and were possibly meant for when the player is in a specific type of location (i.e., in caves, forests, oceans and beside a waterfall). These sound effects only appeared in C418's June 4, 2009 Sound Test. They were found in .minecraft/resources/sound/loops/, and could be converted to reveal four loops, of birds chirping, cave chimes, ocean and waterfall noises. calm4.ogg was a music track that was included accidentally in Java Edition Alpha 1.1.1 when he used it to test the music system. Unused These features never had any functionality in-game. An unclickable "Play Tutorial Level" button was added to the main menu during Indev. With the addition of texture packs in Alpha v1.2.2, the button was removed. No tutorial level had actually existed during that time. In Infdev, a texture called Fluff.png was added. It was used as a texture for clouds from Infdev 20100611 to Infdev 20100618, but became unused in Infdev 20100624 and was removed by Alpha v1.2.2. The texture from the minecart model is rarely visible. The texture appears to be dirt, which is an artifact of when the minecart used to act as a portable chest. The "dirt" level used to raise when items were put into it. The texture still appeared inside minecarts until Java Edition 1.18 Pre-release 2. Purple arrows were shot by skeletons in Survival Test versions from 0.25. They acted the same as regular arrows, but could not be picked up. The purple arrow used a texture on the same sheet as the normal arrows, but the texture is not currently in use. Despite being unused, their texture was updated with the normal arrow's in the April Fools' snapshot 15w14a. With the addition of a new arrow texture in Java Edition 1.9, the original arrow texture, including the purple arrows, became entirely unused. The original texture was removed in snapshot 21w13a. From 1.8 (snapshot 14w30a) to 1.13 (snapshot 17w45a), the file en_us.lang contained translation strings for a /chunkinfo command, which never existed in game. The following keys existed: It is unknown if this command was used for development or was simply a dropped feature. command_blocks.pdn was an unused file added in 15w34a and quickly removed in the next snapshot. This file was created with the Paint.NET program and, presumably, was used in the creation of the textures for the impulse, chain and repeat types of command block, added in the same snapshot. The file also contains multiple layers. From 10 layers, by default, only "Back Shadow", "Back Panel", and "Orange Back" layers are visible, forming the back texture for the impulse command block. The "Background" name is given to the first created layer in an image created by Paint.NET. This layer contains the old texture for command block, which implies that all other layers were created based upon it. Compared to the final textures, the layers included in command_blocks.pdn lack animation frames and use different colors for the individual “lights” on each “panel”. Other Prior to Java Edition 1.13, all blocks and items had unique numeric IDs alongside namespaced IDs. Numeric IDs were removed during The Flattening in 1.13 and all blocks and items now have only namespaced IDs. In Java Edition Alpha v1.2.2a, players had the ability to spawn nether portals by pressing F4. In Alpha v1.2.2b, spawning nether portals using F4 was removed. In early Indev versions, pressing F5 would toggle between rain and clear. In Beta 1.8 Pre-release, as a result of remaining debug code, players had the ability to use F6 and F7 to control in-game time. In Beta 1.8 Pre-release 2, the functionality of F6 and F7 was removed. In Indev 20100129-1447, it was possible to access 3x3 crafting grid by pressing B. This was intended only as temporary way, and it was removed shortly after in Indev 20100129-2332 after addition of crafting tables. Between 0.0.12a and Beta 1.7.3, pressing F would toggle render distance. In pre-Classic and early Classic, it was possible to spawn human mobs by pressing G. As human mobs were removed from normal gameplay in Survival Test, this functionality was also removed as well. In pre-Classic, early Classic and late Classic (except for versions with Survival mode), it was possible for player to respawn on default position in world by pressing R, which was especially useful if player was stuck somewhere. This was removed in Indev. Prior to Beta 1.8, entity numbers shown above mobs when player opened debug screen with F3. This feature was removed probably to prevent unfair progress, because it allowed players to see where caves and dungeons were located due to monsters in them being labeled by numbers. Between Infdev 20100629 and Alpha 1.0.3, a "Loading..." screen with dirt background appeared upon starting the game. This was removed in Alpha 1.0.4 and replaced with Mojang splash screen. Save level, Load level and Generate new level were features in game menu between Classic and Indev. Save level allowed player to save world which was currently opened, Load level allowed player to load previously saved worlds, while Generate new level allowed player to generate new world. This was removed in Infdev 20100327 and replaced with Select World menu and Autosave. In 0.24_SURVIVAL_TEST, Save level and Load level options were disabled. Between Infdev 20100327 and Beta 1.2_02, players could create only up to 5 worlds. If players wanted to create a new world, they had to delete an existing world. World slots were removed in Beta 1.3 and players could create as many worlds as they want. Block indicator was added in rd-20090515 to indicate currently selected block. It was located on upper right corner of screen. Block indicator was removed in 0.0.19a and replaced with hotbar. Texture packs were added in Alpha v1.2.2, and were replaced with resource packs in snapshot 13w24a for 1.6.1. The "Super Secret Settings", added in snapshot 13w38a for 1.7.2, were removed in snapshot 15w31a for 1.9 due to an internal rewrite. It was a button under the options menu that, when pressed, would blare a random game sound with a lower pitch, and activate a shader. "3D Anaglyph" was an option (added in Java Edition Classic 0.24_SURVIVAL_TEST) in video settings that applies a red-cyan stereoscopic effect, enabling the use of red-cyan 3D glasses to experience the game in more depth. This option was removed in snapshot 17w43a for 1.13 due to 3D glasses becoming less popular.[citation needed] Note: It sometimes leaves a stain on your skin when you turn it off. "Limit Framerate" was an option (added in 0.26 SURVIVAL TEST) in video settings that allowed player to toggle framerate of game. Prior to Beta 1.6.5, it had only OFF and ON states. In Beta 1.6.5, this option was renamed to "Framerate cap" and instead of single OFF/ON switch, states 200, 90 and 40 FPS were added. It was removed in Beta 1.6.6 and replaced with "Performance" option. "Performance" was an option (added in Java Edition Beta 1.6.6) in video settings that allowed player to configure framerate of game. It had three states, Balanced (limits to 120 maximum FPS), Power Saver (constantly limits to 35 FPS) and Max FPS (sets no limit to maximum FPS). It was removed in Java Edition 1.7.2 and replaced with Max Framerate slider. "Maximum" and "Minimum" (added in Java Edition 1.5) were states of the Smooth lighting option. "Minimum" state used the original smooth lighting rendering that existed since Beta 1.3, while "Maximum" state existed as way to correct lighting of certain blocks (like back of stairs). Over time, there wasn't any difference between these states and in Java Edition 1.19.3 RC1, the "Minimum" state of smooth lighting was removed and the "Maximum" state was renamed to ON. "Advanced OpenGL" was an option (added in Java Edition Beta 1.5) in video settings that allowed players to use occlusion culling which means it didn't rendered blocks that the player can't "see" which helped to gain performance in graphics cards that supported it, but many players complained that it was counterproductive. This option was removed in 1.8. "Use VBOs" was an option (added in Java Edition 14w29a) in video settings that allowed players to toggle VBOs which offered a ~10% performance increase when set to ON. It was removed in Java Edition 18w44a and VBOs are now always used. "Show FPS" was an option (added in Java Edition Classic 0.0.23a) that allowed players to show debug screen. It was removed in Alpha 1.1.1 and debug screen is now opened with F3 key. "Alternate Blocks" was an option (added in Java Edition 14w28a) that allowed players to enable (or disable) weighted alternative block models. When turned off, the least complex highest priority model is always used for each block. It was removed in Java Edition 1.9. "Server Textures" was a client-side option (added in Java Edition 1.3.1) in video settings that allowed players to enable (or disable) texture pack/resource pack used by server. It was removed in Java Edition 1.7.6 and replaced with server-side "Server Resource Packs" option and moved from video settings to Edit Server Info. "Hide Address" was an option in Edit Server Info that allowed players to toggle display of IP addresses in server list. It was removed in Java Edition 1.7.2, probably for privacy reasons. The "Player Activity" button in "Minecraft Realms" was added in 1.5, but it was removed in 1.14.4 for unknown reasons. This button was used to show the online activities of players. Chat preview was a feature (added in Java Edition 1.19) which displayed a server-controlled preview above the chat edit box, showing how messages appeared when sent. Chat preview sent chat messages to the server as they were typed, even before they were sent, the server then sent back the styled preview in real time. This allowed servers to apply dynamic message stylings while still allowing chat to be securely signed. Chat preview was removed in Java Edition 1.19.3. Native Twitch.tv integration was added in snapshot 13w47a for 1.7.4, and was removed in snapshot 15w31a for 1.9. It integrated Twitch chat into the game. Note: When a line of splash text is removed, the line it occupied in splashes.txt is deleted, meaning the line number of all subsequent splashes lowers by one. Prior to 1.3, this splash read "SOPA means LOSER in Swedish", without an exclamation point. The specific bill SOPA had not been a current issue for several years, by the time of the splash's removal. Prior to the release of Launcher 2.1.497x, the launcher contained multiple easter eggs. If the player hovered their cursor over the "Play" button for a few seconds, a random mob would appear in the bottom right corner of the launcher. In the top left corner of the launcher, the player could see a translucent creeper face. There was about a 1⁄11 chance of the creeper face being replaced with a shrugging kaomoji, ¯\_(ツ)_/¯. When the player clicked on either of these, they turned solid white. Clicking them again would return them to their translucent state. In addition, if the player pressed Ctrl+B, the experience orb pickup sound would play (). The conduit was added in snapshot 18w15a with particles, but those particles were changed in the next snapshot, 18w16a. From Java Edition Beta 1.8 Pre-release up to its removal in Java Edition 14w34c, a fog effect and particles would appear in the lower 16 blocks of the world. From snapshot 14w07a for 1.8, dispensers had the ability to place command blocks, when activated. This feature was removed as of 1.8.6 to solve a security issue. In 1.8, mobs ran away from creepers that were about to explode. In 1.8.1-pre1, this feature was removed because every mob that had the ability to run from a creeper was looking for an exploding creeper every tick, degrading performance. In snapshot 18w45a for 1.14, ravagers were originally meant to spawn in pillager patrols rather than raids. In 18w46a, ravagers were removed from pillager patrols which made them briefly unused, and in 18w47a, ravagers were now spawning in raids instead. In snapshot 18w43a for 1.14, ravagers were fleeing away in presence of rabbits. This feature was removed in 18w44a because it didn't fit with ravager's lore. In snapshot 14w27a for 1.8, it was possible to tame rabbits with carrots. In 14w34a, taming functionality was removed and rabbits can no longer be tamed. Prior to 1.14, cats were initially meant to be tamed from ocelots. In 1.14, ocelots can no longer be tamed and cats can be tamed from stray cats instead. Attempting to tame ocelots, a player can gain an ocelot's trust instead by feeding it raw cod or salmon until heart particles show, causing it to no longer flee from players. In snapshot 17w14a for 1.12, parrots were cycling through variants if music was playing on a nearby jukebox. In 17w15a, this behavior was removed and parrots no longer cycle through variants. Prior to 1.9, baby horses were gradually growing when fed or when certain amout of time passed. This was removed in 1.9 and baby horses now grow only after they turn adult. Prior to 1.4.2, wheat was used for feeding chickens and pigs. In 1.4.2, this was changed and chickens are now fed with seeds, while pigs are fed with carrots and potatos. In snapshot 17w13a for 1.12, cookies were used for feeding parrots. In Java Edition 1.12 Pre-release 3, this was changed and parrots are now fed with seeds. Parrots will die when player attempts to feed them with cookies. Prior to 1.14, bone meal, ink sac, cocoa beans and lapis lazuli were used as white, black, brown and blue dyes. In 1.14, this was changed and white dye, black dye, brown dye and blue dye were added as separate dye items while bone meal, ink sac, cocoa beans and lapis lazuli are no longer used as dyes. In snapshot 16w20a for 1.10, water evaporated on top of magma blocks when randomly ticked. From snapshot 18w07a for 1.13, whirlpool bubble columns are produced on top of magma blocks instead. Prior to Java Edition 1.4.2, it was possible to open and close wooden doors by hitting them with left click. This feature was removed, probably because destroying doors was more difficult. In Java Edition Classic 0.30, it was possible to defuse primed TNT by hitting it with left click. This feature was removed in Indev. Between Indev and Beta 1.6.6, hitting sheep with left click made them drop wool. This feature was removed in Beta 1.7 due to addition of shears. Prior to Java Edition 1.9, crashing boats instantly broke them into planks and sticks. In 1.9, this behavior was removed as many players complained about it. Prior to Java Edition Beta 1.6, tilling a grass block with a hoe had a small chance of dropping wheat seeds. This feature was removed and wheat seeds are now obtained by breaking a short grass instead. Prior to Java Edition 1.1, players (and other mobs as well) could trample farmland by walking on it. To avoid this, players had to use sneaking. This feature was removed and farmland is now trampled only when a player jumps onto it. Prior to Java Edition Beta 1.6, fire spreading was very aggressive and fire was able to spread infinitely. This behavior was removed in Beta 1.6 and fire spreading was severely nerfed. Prior to Java Edition 1.8, it was possible to shuffle enchantment options by swapping items in the input slot. From 1.8, this behavior was removed and enchantments the player would get on a specific kind of item do not change until the enchantment happens. Between Java Edition Beta 1.8 and 1.5.2, it was possible to break blocks with swords in Creative mode. This ability was removed in 1.6.1, probably to prevent players from accidentally destroying their buildings while fighting mobs. Between Java Edition Beta 1.8 and Beta 1.9 Pre-release 4, monsters were trying to attack players in Creative mode. This behavior was removed in Beta 1.9 Pre-release 5 and all monsters remained neutral towards Creative mode players, unless player provoked them by hitting (until versions 1.6.1 and 1.7.2 where provocation was gradually removed). In pre-Classic and early Classic versions, block interactions behaved differently. Between pre-Classic and early Indev, it was possible to place plants (saplings, mushrooms, and flowers) on any blocks, even on top of another plant, and not only on grass blocks or dirt. Last version where this was possible is Java Edition Indev 0.31 20100202-2330 (the exact removal date is uncertain because Indev versions between 20100202-2330 and 20100206-2103 are not archived). Survival Test introduced block drops, which were mapped as follows: Block drops were reworked in Indev. In Survival Test, item drops were restricted to the cube shape used for blocks. The projected texture was the same on all faces and the texture scale was closer to those of blocks, making it look cropped. In Survival Test, mobs (pigs, sheep, skeletons, zombies, spiders and creepers) had different walking animations. In Survival Test, creepers did melee damage (4HP) to the player. In Indev 0.31, this feature was removed. When 1.3 split client and server logic, several features lost significant functionality. While some of these have been effectively restored or at least substituted, many of them remain removed to this day. Ghasts used to expand slightly before shooting fireballs. This was accidentally removed in 1.3. Baby villagers used to accept poppies (originally roses) offered to them by iron golems since their addition in Java Edition 12w08a. This feature was removed at some point during the development of Java Edition 1.14. Iron golems still offer poppies to baby villagers, but they don't take the flower from the golem's hand. Erosions, also known as basins, are terrain features that strip away the surface layer of blocks in a small area, exposing the stone underneath. They were accidentally removed in 1.18 (Java Edition 21w41a). Mushrooms generated in caves from Java Edition Classic 0.24_SURVIVAL_TEST until 1.18 (Java Edition 21w39a), when underground mushroom patches were (probably accidentally) removed from Java Edition, and have yet to be re-added. Between Java Edition Beta 1.2 and Beta 1.2_02, it was possible to milk squids with an empty bucket. This feature was removed in Beta 1.3. In Java Edition Beta 1.9 Pre-release, it was possible to gain experience points by jumping. This was only a testing feature and was removed in Java Edition Beta 1.9 Pre-release 2. entity.hanging.place and entity.hanging.pop were two sound effects added in snapshot 15w49a and removed in the next snapshot, 15w49b. The sound effects were blank audio files and were likely intended as sound effects for the lead. There was a locate command called /locate New_Village. This was implemented in snapshot 18w48a for Village & Pillage before the village structures from Update Aquatic and prior were removed. Once these "old" villages were officially taken from the game's structure spawn list in snapshot 19w02a, /locate New_Village was replaced by /locate Village as the New_Village ID was no longer needed. The water_hacked and waterlogged tags were added in snapshots 18w07a and 18w07b for 1.13 respectively and removed in 18w10c. Before the removal, these tags functioned as follows: Notes References Navigation See here for more information Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Pet_Cat] | [TOKENS: 180] |
Pet Cat 10HP Passive Animal Adult:Height: 0.7 blocksWidth: 0.6 blocks Baby:Height: 0.35 blocksWidth: 0.3 blocks 0.3 On mine start when "Pet Cat" unlock is active A pet cat is a pet variant of the cat introduced in 25w14craftmine. Contents Spawning A pet cat spawns next to the player on mine start when the "Pet Cat" Player Unlock is active. Drops Pet cats drop nothing when killed. Behavior The behaviors between pet cat and the cat in regular versions are almost the same, but there are still some differences: Sounds Issues Issues relating to "Pet Cat" are not maintained on the bug tracker because it is an April Fools' joke, and is therefore not in the newest stable version or snapshot. Issues reported there are closed as "Invalid". Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Magenta_Terracotta] | [TOKENS: 295] |
Stained Terracotta Yes Yes (64) 4.2 1.25 No No No No Stained terracotta[note 1] is a dyed variant of terracotta obtained by crafting undyed terracotta with dyes. Some of the variants are found in badlands biomes, and all variants can be smelted into glazed terracotta. Contents Obtaining All 16 colors of terracotta can be mined using any pickaxe. If mined without a pickaxe, it drops nothing. Badlands Red, orange, yellow, brown, white, and light gray terracotta can be found naturally in badlands biomes, which yield massive amounts of stained terracotta. Villages White terracotta can be found as a housing material in plains villages. Yellow, orange and red terracotta generates in some houses in savanna villages. Lime terracotta generates in the mason houses of desert villages. Others Once terracotta has been dyed, the color cannot be changed or removed: the crafting recipe is irreversible. Usage All 16 colors of terracotta can be placed under note blocks to produce a "bass drum" sound. Sounds Java Edition: Bedrock Edition: Data values Java Edition: Bedrock Edition: Videos History Issues Issues relating to "Stained Terracotta" are maintained on the bug tracker. Issues should be reported and viewed there. Gallery Notes Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Polished_Deepslate_Slab] | [TOKENS: 234] |
Polished Deepslate Slab No Yes (64) 6 3.5 No Double slab: No Single slab: Partial (blocks light)[JE only]Partial (diffuses sky light)[BE only] Yes No No 59 DEEPSLATE A polished deepslate slab is a decorative slab variant of polished deepslate that generates in ancient cities and is used for building. Contents Obtaining Polished deepslate slabs can be mined using any pickaxe. If mined without a pickaxe, they drop nothing. Polished deepslate slabs generate as part of ancient cities. Usage Polished deepslate slabs can be placed under note blocks to produce "bass drum" sounds. Sounds In Bedrock Edition, when a polished deepslate slab is combined into a double slab, the block's use sound is played. Java Edition: Bedrock Edition: Data values Java Edition: Bedrock Edition: Java Edition: Bedrock Edition: History Issues Issues relating to "Polished Deepslate Slab" are maintained on the bug tracker. Issues should be reported and viewed there. References Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/File:Dark_Forest.png] | [TOKENS: 62] |
File:Dark Forest.png Licensing File history Click on a date/time to view the file as it appeared at that time. You cannot overwrite this file. File usage The following 7 pages use this file (also see what links to it): Global file usage The following other wikis use this file: Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Marketplace?section=8&veaction=edit] | [TOKENS: 1101] |
Marketplace The Marketplace (known as the Store on PlayStation) is an in-game platform where players can purchase access to content created by both Minecraft and members of the Minecraft Partner Program. Contents Usage The Marketplace is opened from the title screen, game menu (Browse Add-ons!), or dressing room, the former showing an animated button promoting new DLC and sometimes a tag. Throughout the menus are other buttons redirecting to the Marketplace, such as in resource pack or world template selection menus. Furthermore, Marketplace content is often promoted with pop-ups or inbox messages. It is only available with a stable Internet connection and a Microsoft account, and not in the trial version. The Marketplace is also available from minecraft.net, where packs can be browsed similar to the in-game menu, purchased once signed in, and even the game can be launched opening the selected pack's page in the Marketplace. The menu promotes various types of content organized into sections. With the Search tool, the player can filter for name, pack type, price, ratings, tags, individual creators, or Marketplace Pass availability. Every pack has a purchase page with more information, tags, images and videos, and purchase or download options. Packs can be added to the Wishlist using the heart icon, and the link to the pack on minecraft.net can be shared. Once obtained, packs can be downloaded to the device at any time. Depending on the type of pack, it can then be activated or played. The bottom of the purchase page allows to rate owned packs stars, which will be shown by the pack. Downloaded packs are automatically updated while in the menus; this can be toggled in the settings. Most content in the Marketplace costs money, and is purchased using Minecoins, although some content is free. Minecoins are obtained in the Marketplace with real money in selected packs, or along with promoted content in content bundles. They are saved to a player's Xbox account; on PlayStation they are called tokens and sold separately. All purchased content instantly syncs to the player's Microsoft account unless not signed into the Microsoft or console account on consoles, in which case it is saved locally to the player's device. Marketplace Pass is a monthly subscription that allows any subscribers to get access to a variety of Marketplace content that changes monthly as long as they pay a monthly fee. Included content can be activated directly from its own tab in screens with Marketplace content, such as the Create from Template screen. The Marketplace Pass is included in Realms Plus subscriptions. Content There are 5 different categories of content available on the Marketplace, including skin packs, worlds, add-ons, texture packs, and mash-up packs. All content is submitted by official Minecraft partners and is approved by the Minecraft Content Team. The Minecraft Wiki only documents officially promoted DLC, third-party content usually has its own documentation. Skin packs are collections of custom skins that players can use in both singleplayer and multiplayer games. Depending on the specific content, some skin packs provide 1 or 2 free skins to use without needing to purchase. Skin packs can be seen in the Dressing Room, allowing to enable included skins. Worlds are pre-built maps that offer wide variety of in-game experiences. Not to be confused with mash-up packs, worlds can also include custom textures, blocks, items and mobs and be bundled with bonus skins. Worlds in the Marketplace are distributed as world templates; they can be downloaded in the Create from Template screen allowing to create a world using the template. Dynamic worlds don't have a set build like normal pre-built ones, instead they can be generated like a Minecraft world. These worlds allow for a whole new experience every time because they generate differently depending on the seed. Sometimes they also include add-ons and texture packs as well. Adventure maps are self-contained experiences that focus on exploring and other types of guided gameplay. These types of worlds can range from PvP arenas to simulators and can be designed for singleplayer, multiplayer or both. Minigames are compact worlds with a specific theme or goal that are designed to be repeatable. These can feature a set of different gamemodes and variants or be designed to reset continuously. Survival spawns are starter maps that players can explore, gain loot from and expand. Maps of this type can sometimes add an entirely new aspect to the game but still allows players to experience the world as they normally would in survival mode. Texture packs, built from resource packs, allow players to change the visual appearance of worlds. These packs can also customize other in-game elements such as sounds, items, the GUI, the geometry/shape of mobs, animations, and Vibrant Visuals. Texture packs are only able to alter existing features in Minecraft and cannot add new mobs, blocks or items. Texture packs can be enabled from the Global Resources settings tab in the main menu. Unless a world or server disables global resources, they can always be enabled locally on the player's device. Mash-up packs are special bundles that combine a world, texture pack and skins. Unlike worlds, texture packs included in mash-up packs can be used across other singleplayer worlds and even servers. Add-ons are resource and behavior packs that can fully customize the game by adding new items, blocks, mobs, and more. Add-ons can be added to any world. They can be played and accessed on both singleplayer and multiplayer. History Issues Issues relating to "Marketplace" are maintained on the bug tracker. Issues should be reported and viewed there. Trivia Gallery References Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Pale_oak] | [TOKENS: 382] |
Pale Oak Pale Garden Creaking (from creaking heart). Yes A pale oak is a type of tree that generates in pale gardens. Naturally-generated pale oaks have a chance of containing creaking hearts in them. The trees have a similar shape to dark oak. Players can grow a pale oak by placing four pale oak saplings in a 2×2 square; pale oaks grown from saplings never contain creaking hearts. Contents Appearance Pale oaks have some similarities with dark oak trees, including thick 2×2 trunks, irregular logs connected to the trunk and a similar canopy shape. However, they are grey in color and have pale hanging moss attached to the canopy. Naturally generated pale oak trees sometimes have creaking hearts hidden inside. Generation The pale oak only spawns naturally in the pale garden biome. It has a 20% chance to spawn a creaking heart. The spawn attempt fails if there is no log that is completely hidden by other logs. Blocks and items These items can be obtained from all variants of pale oak: Planting Pale oak saplings can be planted on: Growing these trees requires four pale oak saplings arranged in a 2×2 grid; they do not grow if planted individually. They require a 3×3 column of unobstructed space at least 7 blocks above the sapling to grow (8 blocks including the sapling itself). This column is centered on the northwestern sapling. Additionally, pale oak trees require a 5×5 column without obstruction for the next 3 layers of its final height. No horizontal clearance is needed at the base of the tree (saplings planted in a 2×2 hole 1 block deep still grow). Data values History Issues Issues relating to "Pale Oak" are maintained on the bug tracker. Issues should be reported and viewed there. Gallery Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/File:Custom_world_generation_mod_and_shader_pack.jpg] | [TOKENS: 84] |
File:Custom world generation mod and shader pack.jpg Summary An image example of a Minecraft world with custom world generation mod and shader pack. Licensing File history Click on a date/time to view the file as it appeared at that time. You cannot overwrite this file. File usage The following 3 pages use this file (also see what links to it): Global file usage The following other wikis use this file: Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Add-on?section=8&veaction=edit] | [TOKENS: 1118] |
Add-on An add-on is a package format and a type of downloadable content that provides additional custom game features beyond the base game in Bedrock Edition. It contains a set of programming interfaces used for constructing and customizing certain game objects and elements, such as entities, blocks, items, biomes, structures, the user interface, and more. It is officially supported by Mojang Studios, who provide the Creator Documentation for developers. Add-ons consist of three main APIs: a resource pack for managing assets and resources, a behavior pack for defining data-driven behaviors, and the Script API for writing a set of procedural instructions to perform custom behaviors and interactions. These functions and utilities are used for video game modding. Add-ons are officially hosted on the Marketplace, where players can download or purchase them on their devices using an in-game digital currency called Minecoins. They must be submitted by members in the Minecraft Partner Program and approved by the Minecraft Content Team. Contents Overview Add-ons can be created with two types of data packs: behavior packs and resource packs. Behavior packs can be used to change gameplay and allow adding and customizing entity behaviors, loot tables, spawn rules, item behaviors, item recipes, biome characteristics, and much more. Resource packs affect how the game looks and have no effect on gameplay, and they allow adding and customizing textures, models, music, texts, and interfaces. Definitions are written in JSON files, which are organized in multiple folders by their features. This system allows users to override and modify certain features in the base game, or add unique features with their own pack. All contents of an add-on can be packaged together in a zipped .mcaddon file. An add-on file can be automatically imported by the game, which will organize all contents in the dedicated directories in com.mojang. Resource packs and behavior packs can contain other packs inside the root, known as sub-packs. A sub-pack has the same format as the main pack and the directory of a sub-pack can have any name. Sub-packs need to be specified in the manifest.json file of the main pack, where a name and minimum memory tier can also be added. For example, a pack can have multiple less resource-intensive sub-packs for lower memory tiers, but it can also be used for other types of settings. The memory tier, affecting which sub-pack is used, can be adjusted in the pack's settings menu in-game. Molang is a simple expression-based language designed for fast, data-driven calculation of values at run-time, and with a direct connection to in-game values and systems. It is used in Bedrock Edition in their add-on system with its purpose being to enable low-level systems like animation to support flexible data-driven behavior for both internal and external creators, while staying highly performant. Scripting is an add-on feature used to write a set of procedural instructions for the game to perform custom behaviors and interactions at a certain time or in response to events and actions. It lets users control behaviors of entities, blocks, and items; characteristics of the world; or an entire game loop. It is fundamentally different from the behavior pack system, the latter uses a component system with preset definitions provided by the game. Script files are written in the JavaScript programming language and loaded by the game under the scripts directory inside an add-on. Users may use TypeScript, a dialect of JavaScript, which provides better error reporting and a static type system. The Scripting API provides script modules for users to interact with the game, each module must be added as a dependency in the manifest.json, some notable ones are: The Scripting API also provides a way to define and register custom commands. The Scripting API version 2 is a major update to the Scripting API, which provides a new API to define custom components along with other major API changes that aren't backward compatible with the previous version. The Marketplace is an in-game platform where creators may sell their add-ons to the player-base. All Marketplace content must be submitted by members in the Minecraft Partner Program and approved by the Minecraft Content Team. Purchased content in the Marketplace is synchronized to the player's Microsoft account, and if they are not signed in, it is saved locally on their device. Add-ons are usually added to the Marketplace every Tuesday (originally Wednesday)[citation needed], although occasionally appearing on other days. Free add-ons are released as part of special events, for occasions such as to promote the release of A Minecraft Movie for Minecraft's 15 Years celebration and the eventful McDonald's X A Minecraft Movie promotion. In addition to the Marketplace, there are community websites dedicated to hosting community-made add-ons, although such add-ons may only be loaded on PCs and phones, whereas consoles can only access those add-ons through Realms. Loading tips Extra loading tip messages would appear if the player is loading a world with add-ons applied. The loading message box is titled "Modified World", and loading tip messages would primarily warn the player about the add-ons or resource packs applied. Here's the list of add-on applied loading tips: History Videos Tutorials from the official Minecraft Creator Channel. Quotes Within Minecraft, there are so many ways to be creative and build the worlds of your dreams. But when you want to extend Minecraft even further and introduce new mobs, items and other artifacts into your world, you’ll want to go to the next level of creation by building new Add-On packs that can transform Minecraft. Gallery See also References External links Resource and Behavior Example Packs Script API Example Packs Navigation More More Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Identifier] | [TOKENS: 1359] |
Identifier Identifiers (also known as resource locations, namespaced IDs, namespaced identifiers, resource identifiers, or namespaced strings) are a way to declare and specify game objects in Minecraft, which can identify built-in and user-defined objects without potential ambiguity or conflicts. Contents Introduction Identifiers are used as plain strings to reference blocks, items, entity types, and various other objects in vanilla Minecraft. A valid identifier has a format of namespace:path, where only certain characters can be used. The namespace and the path of a identifier should only contain the following symbols: The following characters are illegal in the namespace, but acceptable in the path: The preferred naming convention for either namespace or path is snake_case. The namespace and the path of a namespaced ID can contain all symbols with the exception of slashes and colons. The following characters are illegal in the namespace, but acceptable in the path of loot tables and functions. The preferred naming convention for either namespace or path is snake_case. An identifier is converted to a string by concatenating its namespace with a : (colon) and its path. Examples: All identifiers can be converted to strings; however, not all strings can be converted to identifiers. For a string to be converted, it must follow these restrictions: When the : is present, the part of the string before the : becomes the namespace, and the part of the string after the : becomes the path. In Java Edition, and in some cases in Bedrock Edition, when the : is absent, minecraft becomes the namespace and the whole string becomes the path. It is recommended to always include a : in the string format of identifiers. Java Edition usage In Java Edition, identifiers act mainly as main keys of objects in registries or file paths of contents in data packs and resource packs. Some non-customizable contents also use identifiers to identify them. All registries and objects therein have identifiers to represent them. At the root of all registries is a registry with the identifier of minecraft:root into which all other registries are registered. Most registries are intended only for use internally by the game and by extension by mods, but some dynamic registries can have content added to them through data packs, marked in the list below with an asterisk (*). Identifiers are also used to represent file paths in data packs or resource packs. Given that objects in resource packs and data packs are files, the identifiers are constructed from their path relative to the data or assets folder. Though the locations vary by object type and the pack type the object type belongs to, there is a pattern to follow. In general, the location is in the fashion of pack_type/namespace/object_type/name.suffix, where all the / (forward slash) symbol (may be part of object_type or name) is replaced by operating system-dependent directory separator. Given the type of content we want to locate, we can find out the corresponding pack_type, object_type, and suffix. Then, we can substitute in and find out the final file location of the content. Examples A registried pack content refers to pack content that is registered into a registry when the pack is loaded. For a registried pack content, its identifier works as both main key of registry entry and path of its resource file. List of registered pack contents Bedrock Edition usage Unlike Java Edition, where there is a unified standard and handling methods of them, namespaced identifiers are usually treated as normal strings in Bedrock Edition. Moreover, some objects are identified based on their path (e.g. the identifier for recipes and trades) rather than what was defined in their file. In these cases, it is recommended that a folder named after the namespace is parented before the file at hand. The following is a list of all places that use namespaced identifiers: A registried add-on entry refers to any add-on content that is registered with an identifier declared within the content's file definition. Custom content under these types are able to be created. Here is a list of registried add-on entries whose identifiers are namespaced. Some custom fields in add-on files can also be namespaced, such as custom block properties and entity component groups, which aren't listed here. Some content may also be registered within the scripts of behavior packs. These are read as the world is generating. Namespaces This isn't a new concept, but I thought I should reiterate what a "namespace" is. Most things in the game has a namespace, so that if we add something and a mod (or map, or whatever) adds something, they're both different somethings. Whenever you're asked to name something, for example a loot table, you're expected to also provide what namespace that thing comes from. If you don't specify the namespace, we default to minecraft. This means that something and minecraft:something are the same thing. A namespace is a domain for content. It is to prevent potential content conflicts or unintentional overrides of objects of the same name. For example, two data packs add two minigame mechanisms to Minecraft; both have a function named start. Without namespaces, these two functions would clash and the minigames would be broken. When they have different namespaces of minigame_one and minigame_two, the functions would become minigame_one:start and minigame_two:start, which no longer conflict. Minecraft reserves the minecraft namespace. When a namespace is not specified, a identifier falls back to minecraft[Java Edition only]. As a result, the minecraft namespace should only be used by content creators when the content needs to overwrite or modify existing Minecraft data, such as adding a function to the minecraft:load function tag. The namespace should be distinct for different projects or content creations (e.g. a data pack, a resource pack, a mod, backing data/resource packs for a custom map, etc.) To prevent potential clashes, it is recommended that the namespace should be as specific as possible: In either case, these poorly chosen namespaces reduce the exposure of a project and bring difficulties for debugging when there are multiple content creations applied to the game. In Java Edition, the vanilla Minecraft resource pack declares Realms-oriented language files in the realms namespace (located at assets/realms/lang/.json) and game-related language files in the minecraft namespace, even though translation keys are not identifiers. The realms jar itself also declares its en_us.json language file and its various textures in the realms namespace. In the IDs of command argument types, a brigadier namespace also appears for command argument types that are native to Brigadier. In Bedrock Edition, the internal resource and behavior packs for Bedrock Editor contain some entities and items namespaced with editor. History See also References External links Navigation All commands Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Red_Mushroom] | [TOKENS: 680] |
Red Mushroom Yes Yes (64) Any tool 0 0 No Yes No No 28 COLOR_RED A red mushroom is a variety of fungus that grows and spreads in dark areas. Mushrooms can generate small or huge in size. Contents Obtaining Red mushrooms can be instantly mined with any tool, including by hand. Mining a red huge mushroom block drops up to 2 red mushrooms. Fortune does not affect the drop rate of mushrooms in any form. A red mushroom also breaks instantly and drops as an item if: Red mushrooms naturally generate in poorly lit areas (light level of 12 or less). If this condition is met, each chunk has a 1⁄8 (12.5%) chance to generate red mushrooms in the form of random patches. Mushrooms also generate on the surface of a swamp, old growth spruce taiga, old growth pine taiga, or mushroom fields biome, along with anywhere in the Nether. Unlike plants, they are able to generate on top of nearly any block type. In Java Edition, they are commonly found in patches on the Nether roof, and are the only blocks that can generate there. Witch huts have a flower pot with a red mushroom inside. Mushrooms also generate inside "mushroom farm" rooms in woodland mansions. Red mushrooms planted on podzol can also be found around bogged and cave spider trial spawners in trial chambers. Fallen trees can have up to 2 mushrooms generated on them. Mining a red huge mushroom has a chance of dropping red mushrooms for each block mined. Java Edition: Bedrock Edition: Shearing a red mooshroom drops 5 red mushrooms and permanently turns it into a normal cow. Shearing a bogged drops 2 mushrooms, both of which have a chance to be red. An enderman holding a red mushroom drops it upon death. A zombie riding a zombie horse has a 50% chance to drop a red mushroom upon death. Usage Red mushrooms can be planted and grown on blocks that have a full top surface in light levels below 13 and not directly underneath the sky, unless on podzol, mycelium, or nylium. Red mushrooms can be used to heal or tempt zombie horses. When bone meal is applied to a red mushroom, the mushroom has a chance to grow into a red huge mushroom, provided that it is on a proper block (grass block, dirt, coarse dirt, rooted dirt, mud, muddy mangrove roots, moss block, or pale moss block at a light level of 12 or below; on podzol, mycelium or nylium at any light level) and is free of solid blocks within 5 blocks directly above the mushroom. When receiving a random tick, a red mushroom has a 4% chance of spreading to a nearby block (including even above and below diagonally) if there are fewer than five red mushrooms in a 9×9×3 volume around the original mushroom. Red mushrooms can be planted in a flower pot. Placing a mushroom into a composter has a 65% chance of raising the compost level by 1. Sounds Data values Java Edition: Bedrock Edition: History Issues Issues relating to "Red Mushroom" are maintained on the bug tracker. Issues should be reported and viewed there. Trivia Gallery References External links Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Pet_Creeper] | [TOKENS: 165] |
Pet Creeper 8HP Passive Monster Height: 1.95 blocksWidth: 0.6 blocks ? On mine start when "Pet Creeper" unlock is active The pet creeper is a pet variant of the creeper introduced in 25w14craftmine. Contents Spawning A pet creeper spawns next to the player on mine start when the "Pet Creeper" Player Unlock is active. Drops Pet creeper drops nothing when it's killed. Behavior The pet creeper is similar to the regular creeper, but there are still some differences: Sounds Issues Issues relating to "Pet Creeper" are not maintained on the bug tracker because it is an April Fools' joke, and is therefore not in the newest stable version or snapshot. Issues reported there are closed as "Invalid". Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Deepslate_Tile_Slab] | [TOKENS: 223] |
Deepslate Tile Slab No Yes (64) 6 3.5 No Double slab: No Single slab: Partial (blocks light)[JE only]Partial (diffuses sky light)[BE only] Yes No No A deepslate tile slab is a decorative slab variant of deepslate tiles that generates in ancient cities and is used for building. Contents Obtaining Deepslate tile slabs can be mined using any pickaxe. If mined without a pickaxe, they drop nothing. Deepslate tile slabs generate as part of ancient cities. Usage Deepslate tile slabs can be placed under note blocks to produce "bass drum" sounds. Sounds In Bedrock Edition, when a deepslate tile slab is combined into a double slab, the block's use sound is played. Java Edition: Bedrock Edition: Data values Java Edition: Bedrock Edition: Java Edition: Bedrock Edition: History Issues Issues relating to "Deepslate Tile Slab" are maintained on the bug tracker. Issues should be reported and viewed there. References Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Searge] | [TOKENS: 215] |
Searge Michael Stoyke Technical Lead German English, German Searge @SeargeDP Searge seargedp Michael "Searge" Stoyke is a technical lead working at Mojang Studios. He is currently working on Minecraft. His employment at Mojang was announced on November 2, 2013 at the "Future of Minecraft" panel at MINECON 2013. His first day at the Mojang office was January 2, 2014. He is most well known for founding the Mod Coder Pack. He is the founding member of ModJam and was known for his 'secret feature' game where he adds secret features, mainly command block ones, to the game in secret and waits for users to find them and report them on Twitter. On February 13, 2015, Searge announced on Twitter that the 'secret feature' game would stop when snapshots are released for Java Edition 1.9, claiming that it was getting 'a bit old'. Contents Trivia Gallery References Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/File:Cherry_Fence_Gate_JE1_BE1.png] | [TOKENS: 68] |
File:Cherry Fence Gate JE1 BE1.png License File history Click on a date/time to view the file as it appeared at that time. You cannot overwrite this file. File usage The following 46 pages use this file (also see what links to it): Global file usage The following other wikis use this file: Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Add-on#cite_note-16] | [TOKENS: 1118] |
Add-on An add-on is a package format and a type of downloadable content that provides additional custom game features beyond the base game in Bedrock Edition. It contains a set of programming interfaces used for constructing and customizing certain game objects and elements, such as entities, blocks, items, biomes, structures, the user interface, and more. It is officially supported by Mojang Studios, who provide the Creator Documentation for developers. Add-ons consist of three main APIs: a resource pack for managing assets and resources, a behavior pack for defining data-driven behaviors, and the Script API for writing a set of procedural instructions to perform custom behaviors and interactions. These functions and utilities are used for video game modding. Add-ons are officially hosted on the Marketplace, where players can download or purchase them on their devices using an in-game digital currency called Minecoins. They must be submitted by members in the Minecraft Partner Program and approved by the Minecraft Content Team. Contents Overview Add-ons can be created with two types of data packs: behavior packs and resource packs. Behavior packs can be used to change gameplay and allow adding and customizing entity behaviors, loot tables, spawn rules, item behaviors, item recipes, biome characteristics, and much more. Resource packs affect how the game looks and have no effect on gameplay, and they allow adding and customizing textures, models, music, texts, and interfaces. Definitions are written in JSON files, which are organized in multiple folders by their features. This system allows users to override and modify certain features in the base game, or add unique features with their own pack. All contents of an add-on can be packaged together in a zipped .mcaddon file. An add-on file can be automatically imported by the game, which will organize all contents in the dedicated directories in com.mojang. Resource packs and behavior packs can contain other packs inside the root, known as sub-packs. A sub-pack has the same format as the main pack and the directory of a sub-pack can have any name. Sub-packs need to be specified in the manifest.json file of the main pack, where a name and minimum memory tier can also be added. For example, a pack can have multiple less resource-intensive sub-packs for lower memory tiers, but it can also be used for other types of settings. The memory tier, affecting which sub-pack is used, can be adjusted in the pack's settings menu in-game. Molang is a simple expression-based language designed for fast, data-driven calculation of values at run-time, and with a direct connection to in-game values and systems. It is used in Bedrock Edition in their add-on system with its purpose being to enable low-level systems like animation to support flexible data-driven behavior for both internal and external creators, while staying highly performant. Scripting is an add-on feature used to write a set of procedural instructions for the game to perform custom behaviors and interactions at a certain time or in response to events and actions. It lets users control behaviors of entities, blocks, and items; characteristics of the world; or an entire game loop. It is fundamentally different from the behavior pack system, the latter uses a component system with preset definitions provided by the game. Script files are written in the JavaScript programming language and loaded by the game under the scripts directory inside an add-on. Users may use TypeScript, a dialect of JavaScript, which provides better error reporting and a static type system. The Scripting API provides script modules for users to interact with the game, each module must be added as a dependency in the manifest.json, some notable ones are: The Scripting API also provides a way to define and register custom commands. The Scripting API version 2 is a major update to the Scripting API, which provides a new API to define custom components along with other major API changes that aren't backward compatible with the previous version. The Marketplace is an in-game platform where creators may sell their add-ons to the player-base. All Marketplace content must be submitted by members in the Minecraft Partner Program and approved by the Minecraft Content Team. Purchased content in the Marketplace is synchronized to the player's Microsoft account, and if they are not signed in, it is saved locally on their device. Add-ons are usually added to the Marketplace every Tuesday (originally Wednesday)[citation needed], although occasionally appearing on other days. Free add-ons are released as part of special events, for occasions such as to promote the release of A Minecraft Movie for Minecraft's 15 Years celebration and the eventful McDonald's X A Minecraft Movie promotion. In addition to the Marketplace, there are community websites dedicated to hosting community-made add-ons, although such add-ons may only be loaded on PCs and phones, whereas consoles can only access those add-ons through Realms. Loading tips Extra loading tip messages would appear if the player is loading a world with add-ons applied. The loading message box is titled "Modified World", and loading tip messages would primarily warn the player about the add-ons or resource packs applied. Here's the list of add-on applied loading tips: History Videos Tutorials from the official Minecraft Creator Channel. Quotes Within Minecraft, there are so many ways to be creative and build the worlds of your dreams. But when you want to extend Minecraft even further and introduce new mobs, items and other artifacts into your world, you’ll want to go to the next level of creation by building new Add-On packs that can transform Minecraft. Gallery See also References External links Resource and Behavior Example Packs Script API Example Packs Navigation More More Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Add-on?action=edit§ion=] | [TOKENS: 227] |
Editing Add-on Please note that all contributions to Minecraft Wiki are considered to be released under the CC BY-NC-SA 3.0 license, except for pages imported from wiki.vg or pages derived from such pages, which are considered to be released under the CC BY-SA 3.0 license. See Minecraft Wiki:Copyrights for details. If you do not want your writing to be edited mercilessly and redistributed at will, then do not submit it here. You are also promising us that you wrote this yourself, or copied it from a public domain or similar free resource. Do not submit copyrighted work without permission! You may also post content obtained from Mojang, its websites, manuals and guides, concept art and renderings, press and fansite kits, and other such copyrighted material that Mojang has made available to the general public, to the Minecraft Wiki. All rights, title and interest in and to such content shall remain with Mojang, as applicable, and such content is not licensed pursuant to the Terms of Use. Pages included on this page: This page is a member of 4 hidden categories: Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Marketplace?section=11&veaction=edit] | [TOKENS: 1101] |
Marketplace The Marketplace (known as the Store on PlayStation) is an in-game platform where players can purchase access to content created by both Minecraft and members of the Minecraft Partner Program. Contents Usage The Marketplace is opened from the title screen, game menu (Browse Add-ons!), or dressing room, the former showing an animated button promoting new DLC and sometimes a tag. Throughout the menus are other buttons redirecting to the Marketplace, such as in resource pack or world template selection menus. Furthermore, Marketplace content is often promoted with pop-ups or inbox messages. It is only available with a stable Internet connection and a Microsoft account, and not in the trial version. The Marketplace is also available from minecraft.net, where packs can be browsed similar to the in-game menu, purchased once signed in, and even the game can be launched opening the selected pack's page in the Marketplace. The menu promotes various types of content organized into sections. With the Search tool, the player can filter for name, pack type, price, ratings, tags, individual creators, or Marketplace Pass availability. Every pack has a purchase page with more information, tags, images and videos, and purchase or download options. Packs can be added to the Wishlist using the heart icon, and the link to the pack on minecraft.net can be shared. Once obtained, packs can be downloaded to the device at any time. Depending on the type of pack, it can then be activated or played. The bottom of the purchase page allows to rate owned packs stars, which will be shown by the pack. Downloaded packs are automatically updated while in the menus; this can be toggled in the settings. Most content in the Marketplace costs money, and is purchased using Minecoins, although some content is free. Minecoins are obtained in the Marketplace with real money in selected packs, or along with promoted content in content bundles. They are saved to a player's Xbox account; on PlayStation they are called tokens and sold separately. All purchased content instantly syncs to the player's Microsoft account unless not signed into the Microsoft or console account on consoles, in which case it is saved locally to the player's device. Marketplace Pass is a monthly subscription that allows any subscribers to get access to a variety of Marketplace content that changes monthly as long as they pay a monthly fee. Included content can be activated directly from its own tab in screens with Marketplace content, such as the Create from Template screen. The Marketplace Pass is included in Realms Plus subscriptions. Content There are 5 different categories of content available on the Marketplace, including skin packs, worlds, add-ons, texture packs, and mash-up packs. All content is submitted by official Minecraft partners and is approved by the Minecraft Content Team. The Minecraft Wiki only documents officially promoted DLC, third-party content usually has its own documentation. Skin packs are collections of custom skins that players can use in both singleplayer and multiplayer games. Depending on the specific content, some skin packs provide 1 or 2 free skins to use without needing to purchase. Skin packs can be seen in the Dressing Room, allowing to enable included skins. Worlds are pre-built maps that offer wide variety of in-game experiences. Not to be confused with mash-up packs, worlds can also include custom textures, blocks, items and mobs and be bundled with bonus skins. Worlds in the Marketplace are distributed as world templates; they can be downloaded in the Create from Template screen allowing to create a world using the template. Dynamic worlds don't have a set build like normal pre-built ones, instead they can be generated like a Minecraft world. These worlds allow for a whole new experience every time because they generate differently depending on the seed. Sometimes they also include add-ons and texture packs as well. Adventure maps are self-contained experiences that focus on exploring and other types of guided gameplay. These types of worlds can range from PvP arenas to simulators and can be designed for singleplayer, multiplayer or both. Minigames are compact worlds with a specific theme or goal that are designed to be repeatable. These can feature a set of different gamemodes and variants or be designed to reset continuously. Survival spawns are starter maps that players can explore, gain loot from and expand. Maps of this type can sometimes add an entirely new aspect to the game but still allows players to experience the world as they normally would in survival mode. Texture packs, built from resource packs, allow players to change the visual appearance of worlds. These packs can also customize other in-game elements such as sounds, items, the GUI, the geometry/shape of mobs, animations, and Vibrant Visuals. Texture packs are only able to alter existing features in Minecraft and cannot add new mobs, blocks or items. Texture packs can be enabled from the Global Resources settings tab in the main menu. Unless a world or server disables global resources, they can always be enabled locally on the player's device. Mash-up packs are special bundles that combine a world, texture pack and skins. Unlike worlds, texture packs included in mash-up packs can be used across other singleplayer worlds and even servers. Add-ons are resource and behavior packs that can fully customize the game by adding new items, blocks, mobs, and more. Add-ons can be added to any world. They can be played and accessed on both singleplayer and multiplayer. History Issues Issues relating to "Marketplace" are maintained on the bug tracker. Issues should be reported and viewed there. Trivia Gallery References Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Pale_moss_carpet] | [TOKENS: 311] |
Pale Moss Carpet Yes Yes (64) 0.1 0.1 No Yes Yes Yes 22 COLOR_LIGHT_GRAY A pale moss carpet is a block that causes vine-like pale moss to grow on the side of neighboring blocks. Contents Obtaining Pale moss carpets can be mined using any tool or by hand, but a hoe is the quickest way to break it. Pale moss carpets can be found on pale moss patches inside of pale gardens. Using bone meal on a pale moss block has a chance to grow pale moss carpets. Usage Similar to moss carpets, pale moss carpets have most of the properties of the standard carpets, cannot be pushed by pistons, cannot be equipped on llamas, and do not occlude vibrations from sculk sensors. When placed next to a block, the pale moss carpet causes a vine texture to appear on the block's adjacent surfaces. If a second block is stacked above, when placed, the pale moss carpet has a 50% chance to cause a two block tall vine texture to appear. The player may break the second vine texture to keep it at one block tall, or use bone meal on the carpet or the first vine texture to grow the second vine texture. Placing a pale moss carpet into a composter has a 30% chance of raising the compost level by 1. Sounds Data values Java Edition: Bedrock Edition: Java Edition: Bedrock Edition: History Issues Issues relating to "Pale Moss Carpet" are maintained on the bug tracker. Issues should be reported and viewed there. Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Pet_Fox] | [TOKENS: 166] |
Pet Fox 10HP Passive Animal ? Height: 0.7 blocksWidth: 0.6 blocks On mine start when "Pet Fox" unlock is active A pet fox is a pet variant of the fox introduced in 25w14craftmine. Contents Spawning A pet fox is spawned next to the player on mine start when the "Pet Fox" Player Unlock is active. Drops Pet fox drops nothing when it's killed. Behavior Unlike normal foxes, it cannot pick up items, however it will follow the player like a tamed wolf, including teleporting. Sounds Issues Issues relating to "Pet Fox" are not maintained on the bug tracker because it is an April Fools' joke, and is therefore not in the newest stable version or snapshot. Issues reported there are closed as "Invalid". Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Polished_Tuff_Slab] | [TOKENS: 234] |
Polished Tuff Slab No Yes (64) 6 1.5 No Double slab: No Single slab: Partial (blocks light)[JE only]Partial (diffuses sky light)[BE only] Yes No No 43 TERRACOTTA_GRAY A polished tuff slab is a decorative slab variant of polished tuff that generates in trial chambers and is used for building. Contents Obtaining Polished tuff slabs can be mined using any pickaxe. If mined without a pickaxe, they drop nothing. Polished tuff slabs generate in trial chambers, next to all ominous vaults. Usage Polished tuff slabs can be placed under note blocks to produce "bass drum" sounds. Sounds In Bedrock Edition, when a polished tuff slab is combined into a double slab, the block's use sound is played. Java Edition: Bedrock Edition: Data values Java Edition: Bedrock Edition: Java Edition: Bedrock Edition: Videos History Issues Issues relating to "Polished Tuff Slab" are maintained on the bug tracker. Issues should be reported and viewed there. References Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Add-on#cite_note-17] | [TOKENS: 1118] |
Add-on An add-on is a package format and a type of downloadable content that provides additional custom game features beyond the base game in Bedrock Edition. It contains a set of programming interfaces used for constructing and customizing certain game objects and elements, such as entities, blocks, items, biomes, structures, the user interface, and more. It is officially supported by Mojang Studios, who provide the Creator Documentation for developers. Add-ons consist of three main APIs: a resource pack for managing assets and resources, a behavior pack for defining data-driven behaviors, and the Script API for writing a set of procedural instructions to perform custom behaviors and interactions. These functions and utilities are used for video game modding. Add-ons are officially hosted on the Marketplace, where players can download or purchase them on their devices using an in-game digital currency called Minecoins. They must be submitted by members in the Minecraft Partner Program and approved by the Minecraft Content Team. Contents Overview Add-ons can be created with two types of data packs: behavior packs and resource packs. Behavior packs can be used to change gameplay and allow adding and customizing entity behaviors, loot tables, spawn rules, item behaviors, item recipes, biome characteristics, and much more. Resource packs affect how the game looks and have no effect on gameplay, and they allow adding and customizing textures, models, music, texts, and interfaces. Definitions are written in JSON files, which are organized in multiple folders by their features. This system allows users to override and modify certain features in the base game, or add unique features with their own pack. All contents of an add-on can be packaged together in a zipped .mcaddon file. An add-on file can be automatically imported by the game, which will organize all contents in the dedicated directories in com.mojang. Resource packs and behavior packs can contain other packs inside the root, known as sub-packs. A sub-pack has the same format as the main pack and the directory of a sub-pack can have any name. Sub-packs need to be specified in the manifest.json file of the main pack, where a name and minimum memory tier can also be added. For example, a pack can have multiple less resource-intensive sub-packs for lower memory tiers, but it can also be used for other types of settings. The memory tier, affecting which sub-pack is used, can be adjusted in the pack's settings menu in-game. Molang is a simple expression-based language designed for fast, data-driven calculation of values at run-time, and with a direct connection to in-game values and systems. It is used in Bedrock Edition in their add-on system with its purpose being to enable low-level systems like animation to support flexible data-driven behavior for both internal and external creators, while staying highly performant. Scripting is an add-on feature used to write a set of procedural instructions for the game to perform custom behaviors and interactions at a certain time or in response to events and actions. It lets users control behaviors of entities, blocks, and items; characteristics of the world; or an entire game loop. It is fundamentally different from the behavior pack system, the latter uses a component system with preset definitions provided by the game. Script files are written in the JavaScript programming language and loaded by the game under the scripts directory inside an add-on. Users may use TypeScript, a dialect of JavaScript, which provides better error reporting and a static type system. The Scripting API provides script modules for users to interact with the game, each module must be added as a dependency in the manifest.json, some notable ones are: The Scripting API also provides a way to define and register custom commands. The Scripting API version 2 is a major update to the Scripting API, which provides a new API to define custom components along with other major API changes that aren't backward compatible with the previous version. The Marketplace is an in-game platform where creators may sell their add-ons to the player-base. All Marketplace content must be submitted by members in the Minecraft Partner Program and approved by the Minecraft Content Team. Purchased content in the Marketplace is synchronized to the player's Microsoft account, and if they are not signed in, it is saved locally on their device. Add-ons are usually added to the Marketplace every Tuesday (originally Wednesday)[citation needed], although occasionally appearing on other days. Free add-ons are released as part of special events, for occasions such as to promote the release of A Minecraft Movie for Minecraft's 15 Years celebration and the eventful McDonald's X A Minecraft Movie promotion. In addition to the Marketplace, there are community websites dedicated to hosting community-made add-ons, although such add-ons may only be loaded on PCs and phones, whereas consoles can only access those add-ons through Realms. Loading tips Extra loading tip messages would appear if the player is loading a world with add-ons applied. The loading message box is titled "Modified World", and loading tip messages would primarily warn the player about the add-ons or resource packs applied. Here's the list of add-on applied loading tips: History Videos Tutorials from the official Minecraft Creator Channel. Quotes Within Minecraft, there are so many ways to be creative and build the worlds of your dreams. But when you want to extend Minecraft even further and introduce new mobs, items and other artifacts into your world, you’ll want to go to the next level of creation by building new Add-On packs that can transform Minecraft. Gallery See also References External links Resource and Behavior Example Packs Script API Example Packs Navigation More More Navigation menu |
======================================== |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.