text
stringlengths
0
113k
[SOURCE: https://minecraft.wiki/w/Copper_Golem_Statue] | [TOKENS: 547]
Copper Golem Statue Yes Yes (64)[note 1] Any tool 6 3 No Yes Yes No No A copper golem statue is the result of a copper golem fully oxidizing and petrifying into a block. It can be posed in four different ways, or it can be reanimated by scraping it with an axe enough times. Contents Obtaining Copper golem statues can be broken by hand, but using a pickaxe is the fastest. A copper golem statue retains its pose when broken. Once fully oxidized, a copper golem has a 0.58% chance per tick to become a copper golem statue and take a random pose, provided it is not waxed and is fully located in air (that is, a copper golem cannot turn into a statue while underwater or standing on a partial block such as a slab, as part of its hitbox is not located within an air block). This process takes on average 8.62 seconds. During the transformation, any items held by the copper golem are dropped. Usage Interacting with a copper golem statue changes its pose, cycling through four poses: standing, sitting, running, and star. In Bedrock Edition, the player's hand must be empty in order to cycle through poses. Unwaxed copper golem statues have four stages of oxidation, including the initial normal state. Lightning bolts and axes can remove the oxidation on copper golems statues. Using a honeycomb on a copper golem statue prevents it from oxidizing. As the block begins to oxidize (exposed), it gets discolored and green spots begin to appear. As the oxidation continues (weathered), the block is a green color with brown spots. In the last stage (oxidized), the block is teal with several green spots. Using an axe on an unoxidized unwaxed copper golem statue reanimates it into an unoxidized unwaxed copper golem. Copper golem statues break when pushed by pistons, cannot be pulled by them and they don't stick to slime blocks or honey blocks. A redstone comparator can read the state of a copper golem statue and emit a signal strength based on its pose. Sounds Data values Java Edition: Bedrock Edition: Java Edition: Bedrock Edition: A copper golem statue has a block entity associated with it that holds additional data about the block. Java Edition: Bedrock Edition: Java Edition: Bedrock Edition: Advancements History Issues Issues relating to "Copper Golem Statue" are maintained on the bug tracker. Issues should be reported and viewed there. Trivia Gallery Unoxidized Exposed Weathered Oxidized Notes Navigation Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/Mod#cite_ref-23] | [TOKENS: 1752]
Mod A mod (short for modification) is a piece of unofficial code that is injected into the game for the purpose of modifying its behavior. They can be used to enhance the game by means ranging from fixing bugs, adjusting core mechanics, to completely revamping the way the game is played with unique features. Contents Overview Mods are primarily user-created content used to alter the base game to create unique experiences that are not usually present from vanilla. They allow players to customize the look and feel of the game, give more options and customization, or expand the game with new progression and mechanics. Mods have control over various aspects of the game, where developers can modify or add custom features, such as physics, graphics, user interface, and various gameplay features (such as entities, items, blocks, world generation, and dimensions, usually through the game's registries). While many mods add content, others act as utilities that are designed to improve the game while being close to vanilla. There are optimization mods that modify the game's rendering to improve frame rates and load times, making the game more accessible on lower-end hardware (see also Tutorial:Improving frame rate). Other client side mods may also fix several bugs and improve stability of the base game, such as reducing crashes and micro-stutter, and fixing several block and item duplication bugs. Mods are usually designed for specific release versions of the game. When the game is updated, the mod must also be updated accordingly, otherwise it may no longer work for future versions. Java Edition is written in Java and runs on JVM, which for technical reasons makes creating mods relatively easy. Modding strongly depend on decompilation to see the game's source code. Because Java compiles to bytecode rather than machine code, it is highly susceptible to decompilation, allowing modders to reverse-engineer the game logic easily. Due to this, a prolific modding scene exists for that edition, which has matured over a decade, and has created several programs and tools for modding, notably mod loaders. For older versions, obfuscation maps provided by Mojang and the community which ease the process of reverse-engineering the game. The unobfuscated versions of the game also lets modders directly see the game's source code without obfuscation maps. Bedrock Edition is written in C++ and runs as machine code, which makes it technically challenging to mod. Mods for that edition exist, but are much less common and less complex, both due to technical challenges, and other reasons such as low interest from the community and add-ons providing official means of adding content to the game. In Java Edition, a mod loader is used to inject modifications into the game. Mod loaders serve as an intermediary between the game's and the mod's code, they provide two main functions for modding: (1) providing system of API and tools to develop new mods and communicate with the game, and (2) managing loading mods simultaneously while keeping them compatible with each other. There are many well-known mod loaders, such as Forge, Fabric, Quilt, and NeoForge. Each mod loader supports different system and API for developing mods. Because of this, mods designed for specific mod loader are not likely interoperable with another mod loader, and vice versa. Add-ons serve as the official modding API in Bedrock Edition, they can add new content and modify existing features and customizations in the game. In comparison to Java Edition mods, add-ons may be limited in terms of features and customization, but are far more friendly and less complex for creators. An official modding API was planned for Java Edition, called "Plugin API" (dubbed "Workbench"), but was subsequently abandoned, with no further mentions or developments of it after Java Edition 1.9 (see Mentioned features § Workbench (Plugin API)). In Bedrock Edition 1.21.20, Mojang Studios removed debug information (bedrock_server.pdb file) from Bedrock Dedicated Server, making modding more difficult for Bedrock Edition. While there are other ways to change the experience of Minecraft, such as resource packs and data packs, the ability to load these is part of the vanilla game and usually not considered modding (see Game customization). Historically, the modification of features such as advancements, enchantments, dimensions, or world generation have required the usage of mods. However, in later versions of the game, the additions and expansions of data packs and resource packs have allowed several of these features to be implemented into the game without any modification of or addition to the game's code. Most modern mod loaders allow data packs and resource packs to be included alongside a mod to provide additional data and resources, such as models or recipes. Types of mods Client mods are direct modifications of the Minecraft game files. They control and add custom content for mobs, particles, items, and blocks, such as models, sounds, textures, and GUIs, but require the server to implement the game mechanics behind them (see § Server-based). They usually modify the client software, or client.jar file. Functional client mods like Sodium and OptiFine modify and enhance client side features of the game, such as graphics fidelity and rendering, while not adding or changing any gameplay features, making them perfectly compatible with vanilla server without any modifications. Server mods are modifications to the official Minecraft server software. They control features that are handled exclusively in the server, primarily the game mechanics, such as physics, mob AI, chat, commands, player interactions (e.g. crafting, smelting, opening chests or inventory, block placement and destruction), world generation, and much more. They cannot control client side features, and are limited in terms of custom content. Most mods are installed together on the server and client side, allowing for more freedom and complete game customization. Server mods are commonly used to enhance server administration with more functionality and ease of use. They can provide tools to protect against griefing and cheating, implement tiered privileges for commands, automate server backup, monitor server performance, optimize gameplay features, and more. Most server mods are compatible with vanilla client, without requiring the same modifications on their end (see semivanilla). Most multiplayer minigames, such as spleef, capture the flag, sky wars and bed wars, are implemented using server mods. Server mods may be referred to as plugins, mainly on Spigot mod loader and its derivatives. Some are implemented as wrappers, which do not modify the server software directly, instead monitoring its output and sending commands to it, typically using the RCON protocol. A shader pack is a client mod used to alter the visuals and looks of Minecraft. They primarily change the game's graphics, and enhance it by adding shadows, lightnings, reflections, and other customization. Shader packs require a mod designed to load them, such as Iris Shaders or OptiFine. When combined with resource pack, shader packs can drastically transform the game's appearance, allowing players to customize into different styles and settings like medieval, realistic, cinematic, and cartoonish. Additionally, resource pack can include custom material data loaded by shader packs for use in physically based rendering (PBR). Modern shader packs can implement path tracing and global illumination (GI) for Minecraft, most notably, SEUS PTGI and Continuum RT have done this. A mod pack is a collections of mods that have been put together and configured so that they work together. Mod packs are often centered around a general theme like tech, quests, or magic. Mod packs often have either custom launchers or installers that make installing and running the mod pack easy. Some of the most popular mod packs include Feed The Beast, Tekkit, RLCraft, and Hexxit. In addition to making it easy to install mod pack clients, certain launchers can also download server mod packs. Modded flag If Minecraft crashes, a modified game is flagged in the crash report. This is possible by first checking the client or server brand is vanilla branded, then verifying if the Java class (where the game crashed from) is signed from a signature file, which is stored on the META-INF directory with .SF file extension in the JAR archive. These checks are done on both client.jar and server.jar files. The signature file that comes from the vanilla build of the game is named MOJANGCS.SF, and stored on the META-INF directory like any other signature files. The creator of the signature file is listed as Microsoft. The crash report text includes one of these lines near the bottom: A shortened example crash report is given below: Trivia Gallery See also Notes References External links Navigation See here for more information Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/File:Netherite_Spear_BE1.png] | [TOKENS: 183]
File:Netherite Spear BE1.png Summary Netherite Spear in inventory. 1. "Minecraft LIVE - September 2025" – Minecraft on YouTube, September 27, 20252. "Unveiling: Mounts of Mayhem" by Sophie Austin – Minecraft.net, September 27, 2025. Recreated by SeaOfPixels Source by Mojang Studios See below. 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 8 pages use this file (also see what links to it): Global file usage The following other wikis use this file: Metadata This file contains additional information, probably added from the digital camera or scanner used to create or digitize it. If the file has been modified from its original state, some details may not fully reflect the modified file. Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/File:PopCultureTab.png] | [TOKENS: 105]
File:PopCultureTab.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 page uses this file (also see what links to it): Global file usage The following other wikis use this file: Metadata This file contains additional information, probably added from the digital camera or scanner used to create or digitize it. If the file has been modified from its original state, some details may not fully reflect the modified file. Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/Copper_Grate] | [TOKENS: 356]
Copper Grate Yes Yes (64) 6 3 No Yes Yes No No Copper grates are a variant of copper blocks that have perforations that can be seen through. Contents Obtaining Copper grates can be mined with a stone pickaxe or better. If a copper grate is broken without a pickaxe, it drops nothing. Waxed copper grates of various oxidization stages generate naturally within the corridors of trial chambers, mostly serving as wall-mounted walkways between different rooms. They are also featured on some walls and floors and can form dead ends within the halls, mostly with a chest in front. Usage Copper grates are decorative transparent blocks that can oxidize. Copper grates do not conduct redstone, and mobs cannot spawn on top of them. They can also be waterlogged. Copper grates adjacent to other copper grates are invisible when viewed through a copper grate that is identical in states of oxidation and wax. Non-waxed copper grates have four stages of oxidation (including the initial normal state). Lightning bolts and axes can remove the oxidation on copper grates. Using a honeycomb on a copper grate prevents it from oxidizing. As the block begins to oxidize (exposed), it gets discolored and green spots begin to appear. As the oxidation continues (weathered), the block is a green color with brown spots. In the last stage (oxidized), the block is teal with several green spots. Sounds Java Edition: Bedrock Edition: Java Edition: Bedrock Edition: Data values Java Edition: Bedrock Edition: Java Edition: Achievements Advancements History Issues Issues relating to "Copper Grate" are maintained on the bug tracker. Issues should be reported and viewed there. Trivia Gallery References Navigation Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/File:Speed_JE1_BE1.png] | [TOKENS: 66]
File:Speed JE1 BE1.png Summary 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 11 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/File:Copper_Lantern_JE2.gif] | [TOKENS: 109]
File:Copper Lantern JE2.gif Summary 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 29 pages use this file (also see what links to it): Global file usage The following other wikis use this file: Metadata This file contains additional information, probably added from the digital camera or scanner used to create or digitize it. If the file has been modified from its original state, some details may not fully reflect the modified file. Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/Copper_Lantern] | [TOKENS: 632]
Copper Lantern Yes Yes (64) 3.5 3.5 Yes (15) Yes Yes No No A copper lantern is a copper variant of a lantern that displays a green flame and oxidizes over time. Contents Obtaining A copper lantern can be mined with anything, but pickaxes are the fastest. A copper lantern also breaks and drops itself if a piston extends or pushes a block into its location, or if its supporting block is moved or destroyed. Usage Copper lanterns can be placed on the top or bottom surfaces of most solid blocks, although some require sneaking. More information can be found at Opacity/Placement. When placed below a block the copper lantern appears to hang. They connect to copper chains seamlessly. Copper lanterns can be placed on the ground (if a supporting floor block is present) or hung (if a ceiling block is present). The type of the block (solid, opaque, transparent, etc...), given the block has top/bottom solid surface, does not affect the ability to hang of a copper lantern, similar to torches. Press use on the targeted block or a block adjacent to the air block the copper lantern is going to occupy to place it. If the latter is used and both the support/ceiling block is presented: If the block the copper lantern is placed on receives a block update that makes it so it can no longer support the placement of the copper lantern, the copper lantern is removed and dropped as an item (e.g: the copper lantern is placed on a trapdoor, and then the trapdoor is flipped). The copper lantern is among the most luminous of light sources, emitting a light level of 15. Copper lanterns also melt snow layers within 2 blocks and ice within 3 blocks (taxicab distance). When the Render Dragon Features for Creators experiment is enabled in Minecraft Preview, the inside of all copper lanterns emits colored point lighting with #86ca59 for the unaffected unwaxed variant, and #e8c398 for all other variants. The casing of the copper lantern blocks a part of the light and casts some shadows around the lantern. Non-waxed copper lanterns have four stages of oxidation (including the initial normal state). Lightning bolts and axes can remove the oxidation on copper lanterns. Using a honeycomb on a copper lantern prevents it from oxidizing. As the block begins to oxidize (exposed), it gets discolored and green spots begin to appear. As the oxidation continues (weathered), the block is a green color with brown spots. In the last stage (oxidized), the block is teal with several green spots. Unlike copper bulbs, the light level of a copper lantern is unaffected by its oxidation stage; even an oxidized copper lantern will still emit a light level of 15. Sounds Java Edition: Bedrock Edition: Java Edition: Bedrock Edition: Data values Java Edition: Bedrock Edition: Java Edition: Bedrock Edition: Advancements History Issues Issues relating to "Copper Lantern" are maintained on the bug tracker. Issues should be reported and viewed there. Gallery Navigation Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/File:ErrorScreenMarketplace.png] | [TOKENS: 106]
File:ErrorScreenMarketplace.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 page uses this file (also see what links to it): Global file usage The following other wikis use this file: Metadata This file contains additional information, probably added from the digital camera or scanner used to create or digitize it. If the file has been modified from its original state, some details may not fully reflect the modified file. Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/Experience#cite_ref-fractional_5-1] | [TOKENS: 1434]
Experience 5HP In Java Edition: Height: 0.5 blocksWidth: 0.5 blocks In Bedrock Edition: Height: 0.25 blocksWidth: 0.25 blocks Experience (EXP or XP for short) can be gained from defeating mobs or performing many kinds of other actions. Experience has no direct effect on the player character, but it can be used to enhance their equipment through enchanting, or by using an anvil to repair, rename, or combine enchantments on equipment. Most sources of experience are produced in the form of experience orbs. In Java Edition, experience gained affects the player's score on the death screen. Experience orbs also recover durability on items with Mending that are being worn or are in-hand. Contents Sources Experience can be gained from several different sources. Most sources drop experience in the form of orbs, which can be claimed by any player, while a few methods directly award the player experience upon completing the action. Gathering experience points increases the player's experience level by gradually filling a bar on the bottom of the screen until a new level is achieved when the bar is full. When the player dies, they drop experience orbs worth 7 * current level experience points, up to a maximum of 100 points (enough to reach approximately 7.5 levels), and all of the other experience vanishes. If the gamerule keepInventory is set to true, the experience is kept even if the player dies. Experience orbs Most experience sources drop experience in the form of experience orbs, which can then be claimed by any player. Experience orbs fade between green and yellow colors and float or glide toward the player up to a distance of 7.25 blocks (calculated from the center of player's feet and the center of the experience orb), speeding up as they get nearer to the player. Experience orbs pulled toward a player are slowed by cobwebs. Experience orbs can also be pulled around or away from the player by running water currents. When collected, experience orbs make a bell-like sound for a split second. Unlike items, experience points are picked up gradually: no matter how many orbs are in the range of the player, they are added to the player's experience one at a time (10 orbs/second). In extreme cases, this can result in the player being followed by a swarm of orbs for many seconds. If an experience orb isn't collected within 5 minutes of its appearance, it despawns. Experience orbs vary in value. The general worth of an orb is reflected by its size, with eleven possible sizes corresponding to specific values. The three smallest sizes are the most commonly encountered, as the majority of experience dropped by mobs and blocks is less than ten. Dense experience orbs with values 17 or higher have orange "eyes" or "cores", and are less frequently encountered, most commonly from defeating the ender dragon, wither and other players, disenchanting objects on a grindstone, breaking spawners, and collecting items from high-traffic furnaces. For performance improvement, experience orbs of the same value can merge into a single entity, but they do not create a higher value orb. Naturally spawned orbs always have an integer value of 1–11, 17, 37, 73, 149, 307, 617, 1237, or 2477. Fishing, breeding, and trading drop a single orb with a random value in the appropriate range. Breaking blocks, killing mobs and players, smelting items, and bottles o' enchanting calculate their total experience amount and then split it into the base values of orbs by size (1, 3, 7, 17, 37, 73, 149, 307, 617, 1237, and 2477). Higher values are chosen first, so, for example, a total value of 1000 would be dropped as orbs with values 617, 307, 73, and 3. While the first ender dragon in a world drops 12,000 experience, it is dropped in 10 waves of 1000 and one of 2000, so no orbs of value 2477 are dropped. Such orbs can exist in the world via furnaces that have had a lot of traffic. Like items, experience orbs float when on water. Experience orbs can be destroyed by fire, lava, explosions, and cacti, and can trigger pressure plates and tripwires. Experience orbs can also stop minecarts. In Bedrock Edition, although mob drops spawn the instant the final blow is dealt to the mob, experience orbs do not appear until the mob entity disappears and the smoke appears. In Java Edition, experience orbs appear in the same spatial and temporal location as loot when an entity is killed. Orbs with negative values can be created using the /summon command, either using values below 0 or above 32767 due to 16-bit integer overflow. They use the smallest texture of experience orb. Negative orbs behave differently from positive orbs, namely that they do not deduct experience when collected by the player. They deduct durability from a tool enchanted with Mending, provided the tool is already damaged prior to collection of the orbs. The following mobs and similar entities do not drop experience when killed: Leveling up The formulas for figuring out how many experience orbs needed to get to the next level are as follows: One can determine how much experience has been collected to reach a level using the equations: Likewise, to get the number of levels from the total experience value, one can utilize the following inverse equations: Score The score is the number of experience the player has collected since their last death. This number is the total experience the player has collected, rather than the amount of experience they had upon death. When the player dies, the score is displayed on the death screen. Sounds Java Edition: Experience orbs do not use entity-dependent sound events. Bedrock Edition: Data values Java Edition: Bedrock Edition: Experience orbs have entity data associated with them that contain various properties. Java Edition: Bedrock Edition: Videos History The experience level costs were heavily revised in snapshot 12w22a and 12w23a, and again in version 1.8. Before these, reaching level 50 (the maximum usable on a single enchantment) required 4625 experience, corresponding to defeating 925 hostile mobs (assuming the "common" ones.) Afterward, considerably less experience is needed to get into higher levels. Higher levels cost more experience than lower ones, but the levels are still easier to get than in 1.2.5. Now, level 30 is the maximum for enchantments, and that cost is equivalent of 279 "common" enemies, less than 1/3 the old price. A player dropping excessive experience orbs upon death may cause performance degradation in the game. Issues Issues relating to "Experience" or "Orb" are maintained on the bug tracker. Issues should be reported and viewed there. Trivia Gallery References Navigation More More Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/File:Beach.png] | [TOKENS: 72]
File:Beach.png Summary An image of a Beach generated in Minecraft. 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 5 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/SpongeBob_SquarePants_Add-On] | [TOKENS: 194]
SpongeBob SquarePants Add-On Spark Universe 1,510 Minecoins August 20, 2024 SpongeBob SquarePants Add-On in Minecraft Marketplace | Minecraft "The SpongeBob add-on is here" – Minecraft.net. SpongeBob SquarePants Add-On is an official add-on made based off of the SpongeBob SquarePants Nickelodeon animated series. Contents Additions Quotes Are ya ready, kids? Bring SpongeBob and his friends into your worlds with this add-on! Includes buildings, mobs, vehicles, weapons, tools, and all of your favorite friends and foes from the SpongeBob universe. SpongeBob is bubbling up from Bikini Bottom and joining your worlds! Let characters like SpongeBob and Patrick follow you on your travels, defeat foes like Plankton, unlock iconic Bikini Bottom buildings, and drive your own boatmobile! Are ya ready, kids? Grab the add-on today! Videos History Gallery See also Navigation Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/File:Universal_New_Year%27s_Gifts.png] | [TOKENS: 107]
File:Universal New Year's Gifts.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 page uses this file (also see what links to it): Global file usage The following other wikis use this file: Metadata This file contains additional information, probably added from the digital camera or scanner used to create or digitize it. If the file has been modified from its original state, some details may not fully reflect the modified file. Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/Experience#cite_ref-fractional_5-2] | [TOKENS: 1434]
Experience 5HP In Java Edition: Height: 0.5 blocksWidth: 0.5 blocks In Bedrock Edition: Height: 0.25 blocksWidth: 0.25 blocks Experience (EXP or XP for short) can be gained from defeating mobs or performing many kinds of other actions. Experience has no direct effect on the player character, but it can be used to enhance their equipment through enchanting, or by using an anvil to repair, rename, or combine enchantments on equipment. Most sources of experience are produced in the form of experience orbs. In Java Edition, experience gained affects the player's score on the death screen. Experience orbs also recover durability on items with Mending that are being worn or are in-hand. Contents Sources Experience can be gained from several different sources. Most sources drop experience in the form of orbs, which can be claimed by any player, while a few methods directly award the player experience upon completing the action. Gathering experience points increases the player's experience level by gradually filling a bar on the bottom of the screen until a new level is achieved when the bar is full. When the player dies, they drop experience orbs worth 7 * current level experience points, up to a maximum of 100 points (enough to reach approximately 7.5 levels), and all of the other experience vanishes. If the gamerule keepInventory is set to true, the experience is kept even if the player dies. Experience orbs Most experience sources drop experience in the form of experience orbs, which can then be claimed by any player. Experience orbs fade between green and yellow colors and float or glide toward the player up to a distance of 7.25 blocks (calculated from the center of player's feet and the center of the experience orb), speeding up as they get nearer to the player. Experience orbs pulled toward a player are slowed by cobwebs. Experience orbs can also be pulled around or away from the player by running water currents. When collected, experience orbs make a bell-like sound for a split second. Unlike items, experience points are picked up gradually: no matter how many orbs are in the range of the player, they are added to the player's experience one at a time (10 orbs/second). In extreme cases, this can result in the player being followed by a swarm of orbs for many seconds. If an experience orb isn't collected within 5 minutes of its appearance, it despawns. Experience orbs vary in value. The general worth of an orb is reflected by its size, with eleven possible sizes corresponding to specific values. The three smallest sizes are the most commonly encountered, as the majority of experience dropped by mobs and blocks is less than ten. Dense experience orbs with values 17 or higher have orange "eyes" or "cores", and are less frequently encountered, most commonly from defeating the ender dragon, wither and other players, disenchanting objects on a grindstone, breaking spawners, and collecting items from high-traffic furnaces. For performance improvement, experience orbs of the same value can merge into a single entity, but they do not create a higher value orb. Naturally spawned orbs always have an integer value of 1–11, 17, 37, 73, 149, 307, 617, 1237, or 2477. Fishing, breeding, and trading drop a single orb with a random value in the appropriate range. Breaking blocks, killing mobs and players, smelting items, and bottles o' enchanting calculate their total experience amount and then split it into the base values of orbs by size (1, 3, 7, 17, 37, 73, 149, 307, 617, 1237, and 2477). Higher values are chosen first, so, for example, a total value of 1000 would be dropped as orbs with values 617, 307, 73, and 3. While the first ender dragon in a world drops 12,000 experience, it is dropped in 10 waves of 1000 and one of 2000, so no orbs of value 2477 are dropped. Such orbs can exist in the world via furnaces that have had a lot of traffic. Like items, experience orbs float when on water. Experience orbs can be destroyed by fire, lava, explosions, and cacti, and can trigger pressure plates and tripwires. Experience orbs can also stop minecarts. In Bedrock Edition, although mob drops spawn the instant the final blow is dealt to the mob, experience orbs do not appear until the mob entity disappears and the smoke appears. In Java Edition, experience orbs appear in the same spatial and temporal location as loot when an entity is killed. Orbs with negative values can be created using the /summon command, either using values below 0 or above 32767 due to 16-bit integer overflow. They use the smallest texture of experience orb. Negative orbs behave differently from positive orbs, namely that they do not deduct experience when collected by the player. They deduct durability from a tool enchanted with Mending, provided the tool is already damaged prior to collection of the orbs. The following mobs and similar entities do not drop experience when killed: Leveling up The formulas for figuring out how many experience orbs needed to get to the next level are as follows: One can determine how much experience has been collected to reach a level using the equations: Likewise, to get the number of levels from the total experience value, one can utilize the following inverse equations: Score The score is the number of experience the player has collected since their last death. This number is the total experience the player has collected, rather than the amount of experience they had upon death. When the player dies, the score is displayed on the death screen. Sounds Java Edition: Experience orbs do not use entity-dependent sound events. Bedrock Edition: Data values Java Edition: Bedrock Edition: Experience orbs have entity data associated with them that contain various properties. Java Edition: Bedrock Edition: Videos History The experience level costs were heavily revised in snapshot 12w22a and 12w23a, and again in version 1.8. Before these, reaching level 50 (the maximum usable on a single enchantment) required 4625 experience, corresponding to defeating 925 hostile mobs (assuming the "common" ones.) Afterward, considerably less experience is needed to get into higher levels. Higher levels cost more experience than lower ones, but the levels are still easier to get than in 1.2.5. Now, level 30 is the maximum for enchantments, and that cost is equivalent of 279 "common" enemies, less than 1/3 the old price. A player dropping excessive experience orbs upon death may cause performance degradation in the game. Issues Issues relating to "Experience" or "Orb" are maintained on the bug tracker. Issues should be reported and viewed there. Trivia Gallery References Navigation More More Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/Commands?section=17&veaction=edit] | [TOKENS: 1848]
Commands Commands (also known as console commands or slash commands) are a mechanic that execute specific actions when entered as text or triggered by blocks or certain entities. Contents Usage In the client, commands are entered via the chat window, which is displayed by pressing the T / ↵ Enter / ‌[BE only] / ‌[BE only] or / key. Using the / key also enters the forward-slash that commands require as a prefix, so it is a useful shortcut. The ↑ Up / and ↓ Down / keys can be used to view previously entered text, including all previously executed commands. When the cursor is at a location corresponding to some types of argument (such as an entity ID), a list of applicable values appears above the text box. If the argument already contains characters, the list displays only those values containing the typed text. Pressing ↹ Tab while entering commands cycles through possible commands or arguments, and can be used to auto-enter them. Commands may also be entered in a multiplayer server's console but are not preceded by a / when entered this way. A server owner running commands in this way is often referred to as "ghosting". Commands in command blocks can be preceded by a slash, but it is not required. Commands can be executed in the following ways: In Bedrock Edition, commands can be executed through specified hotkeys on keyboard & mouse controls, known as command macros. The keybinds with commands can be customized below all other keybinds in the settings. For up to 10 macros, a command can be entered in a text input, which can be quickly executed in-game by pressing Alt + Key. Command macros can be preceded by a slash, but it is not required. This feature is not to be confused with Java Edition's function macros, where functions may reference additional parameters and use them in macro lines (see Function (Java Edition) § Macros). Commands guide In Java Edition: In Bedrock Edition: In both Java Edition and Bedrock Edition, square bracket decorator ([entry]) mean that an entry is optional. Entries decorated with square brackets can only be at the end of a command. Multiple entries decorated with square brackets are allowed at the end of a command, for example, a [b] [c] at the end of a command indicates that only a, a b, and a b c are valid. Most commands require the executor to have a high enough permission level. That means most commands are only available in the singleplayer world if cheats are enabled, and are only available in multiplayer servers if the player is an operator. See permission level for details. Some commands have restrictions on who can use the command or in what context. Cheats can be enabled when creating a new world by Allow Commands‌[Java Edition only] / Cheats‌[Bedrock Edition only] options. In Java Edition, the "Allow Commands" option when creating a new world only affects the player in a singleplayer world or the owner of a LAN world. The "Allow Commands" option when opening a LAN world affects all players in the LAN world. In Java Edition, in singleplayer worlds where cheats were not enabled at creation, they can be enabled on a temporary basis by opening the current game session to LAN play ( Esc → "Open to LAN", then "Allow Cheats" button and "Start LAN World"). The player does not actually need to be on a LAN or have others join. This is not permanent but allows the use of commands until the player quits the world, and changes the player makes via commands (items spawned, etc.) are saved with the world. The player can do this each time the player starts playing the world again. Note that this disables game pausing for the duration, so while open to LAN, the player should get somewhere safe or reload their world before using the Game Menu. The player can disable the LAN world by reloading the world. To permanently enable cheats, the level.dat file has to be edited. In Bedrock Edition, cheats can be toggled at any time in the "Cheats" tab of the settings menu. Enabling cheats in a world permanently prevents players from unlocking achievements in that world, even if cheats are later turned off. In Bedrock Dedicated Server, /changesetting command can be used to toggle cheats. There are different argument types for arguments in commands. Coordinates, target selector, SNBT, text component, and so on are commonly used formats in arguments. The command performing on the server side is divided into two stages: command parsing and command execution. During the command parsing stage, the game identifies the string as a command and checks whether the command is complete and whether arguments are specified correctly. During the command execution stage, the command fulfills its purpose. When typing a command in the chat, or command block, the command is also be parsed in the client side first to provide autocompletion and help the player detect typing mistakes. In Bedrock Edition, when entering into a command block, the command is parsed on the server side once the command block screen is closed. If the command is unparseable in the server side, a syntax error message is outputted into its output box. When attempting to execute an unparseable command, an error message is displayed. Commands in functions are all parsed when loading the function. If any command in a function file is unparseable, the function cannot be loaded by the game. In Java Edition, macro lines are parsed when attempting to run the function, see also Function (Java Edition) § Macros and Function (Java Edition) § Loading and parsing. In Bedrock Edition, if a command in a script is unparseable, an error is thrown when trying to execute the command. After trying to execute a command, it may yield output values, including success count and stored values‌[Java Edition only]. Success count is the value a command passes to the command block executing it. A command block can power a redstone comparator facing away from it (may be separated by a block) with signal strength being the success count. The signal strength reflects the success count of the last command executed. Even after the command block is deactivated, the success count is retained until the command is executed again. In Bedrock Edition, the success count is also returned to the script executing the command. In Java Edition, commands that cannot be executed in command blocks have no success count. In Bedrock Edition, commands that cannot be executed in command blocks or scripts still have a success count, but it cannot be obtained. In Java Edition, success count is always 0 or 1, except the /execute command. In Bedrock Edition, success count is an integer between 0 to 2,147,483,647 (both inclusive) related to the command (e.g., the number of players affected by the command, the number of blocks that were altered, etc.) Stored values‌[JE only] include success value and result value, which are the values passed by other commands to the /execute command, when a command is executed by a /execute command. These two values can be stored to a specified location by the store subcommand in the /execute command. The success value is always 0 or 1. The result value is an integer (rounded down if not). All commands may yield these two stored values after execution, with only two exceptions: /execute command itself does not yield these two stored values; /function command may not yield these two stored values in certain situation. After trying to execute a command, it has a certain result. Possible results include "Unparseable", "Failed", "Successful", "Void"‌[JE only], "Terminated"‌[JE only], and "Error"‌[JE only]. List of commands The tables below will summarize all commands. Debugging commands are not accessible by default, but can be enabled using debug properties. These commands are unavailable in general cases. Most of them can be accessed with a Websocket Server, NPC, the Scripting API or cheats‌[edu only]. Note: You can easily check if a command is still in the game by typing /help <nameOfCommand> into a server console, or the ingame chat. If you do so, and it says Syntax error, then the command does not exist. If it either gives help on the command or says unknown command, then it is still in the game - for example, the command /help gettopsolidblock will return Unknown command: gettopsolidblock. Please check that the command exists and that you have permission to use it., while the command /help something will return Syntax error: Unexpected "something" at "/help >>something<<". /achievement Developer commands are only enabled in internal development builds of Bedrock Edition, and are not normally accessible in release versions. Superseded by /agent These commands only exist in April Fools' Day joke versions of the game. History Issues Issues relating to "Commands" are maintained on the bug tracker. Issues should be reported and viewed there. See also References External links Navigation All commands Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/Monolith] | [TOKENS: 437]
Monolith Any No Monoliths were glitched areas of terrain that happened in the later versions of Infdev and early Alpha stages of the game. These monoliths would cause the terrain to abruptly invert, with natural terrain generation replacing the air/water up to the height limit and vice versa. Contents Generation Monoliths would generate in seemingly random locations throughout the world. They tended to generate around flattish terrain. They were caused by an error in the Perlin noise generator. Specifically, the hilliness of the terrain (the "terrain scale") was controlled by a noise map. The reciprocal of the value of this noise was then used as the intensity of a gradient applied to the terrain. Because the reciprocal is used, flatter terrain is caused by lower values (where the terrain bias gradient drops off faster), and hillier terrain is caused by higher values. Because the reciprocals of small negative numbers are very large negative numbers, the terrain abruptly changes when zero is crossed, causing the gradient to bias higher elevations toward being ground, and lower elevations toward being air. Thus, when terrain scale becomes negative, terrain generates upside-down, generating monoliths. This was possible in early Alpha because the noise map that determined terrain scale could return a negative value. (This may be the same 2d noise map used in Classic, where adding multiple octaves together could result in unpredictably high or low values.)​[more information needed] Structure The monoliths would cause the terrain to abruptly generate up to the height limit, with natural grass block and ore generation. They could theoretically generate arbitrarily tall, being stopped only by the height limit, which - at this point in the game's development - was 128 blocks. The area below the monoliths was completely hollow, except for water generating at sea level and a layer of bedrock at the bottom, making the normal terrain seem like inverse monoliths. It is possible to find small crevices in large monoliths, where normal terrain was generated. History Issues Monoliths are an issue, and due to their removal, can be considered already fixed. Trivia Gallery Navigation Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/Minecraft_Wiki:Hey_Wiki#mw-head] | [TOKENS: 726]
Minecraft Wiki:Hey Wiki Minecraft Wiki Main contributors Java 1.8.0 June 1, 2024 ~228 KiB LGPL-3.0 Yes (GitHub) Hey Wiki is a client mod for Java Edition made by the Minecraft Wiki community. It allows players to quickly open the wiki page of the block, item, or entity that the camera is aimed at, whether it is from the vanilla game or another mod. Download on Modrinth Download on CurseForge Contents Features It is also supported to use MCBrowser and MCEF for in-game browsing. Optionally, the following behaviors in the config menu can be changed: These commands are available: Opening a page with a command does not cause the confirmation screen to appear. Hey Wiki supports [[wiki links]] in chat. When a message is sent with [[wiki link]] syntax, it will automatically be replaced with a clickable link. Interwiki links and other namespaces are supported. For example: Supported wikis The latest version of Hey Wiki supports the following wikis: Resource packs can be used to add support for other wikis. An issue can be filed in case a wiki should be added to the default list. APIs Hey Wiki provides several ways mod, mod pack, data pack, and custom server developers can leverage to support their creation. Hey Wiki supports using resource pack to add support for other wikis. To do so, create a JSON file in the assets/<namespace>/wiki_family/ folder in your resource pack with the following format: You also want to include a translation file in assets/<namespace>/lang/ folder with the following format: Data pack and custom server authors can use heywiki:identifier, heywiki:translation_key and heywiki:fallback_title in custom_data data component to provide custom namespace and name for an item. However, this only accounts for custom items. For 1.20.4, you can populate these fields directly in NBT. You need to use the method above to register a new wiki with a custom namespace using resource pack. If it is not feasible to ask your players to download a resource pack, we can also ship it with the mod itself. For example, on "niceserver", to have a bone item to resolve to the "Drill" page, you will first need to register the "niceserver" namespace per above. Then you can give the player this item: Dependencies For Fabric: For NeoForge: Versioning Hey Wiki uses Semantic Versioning in the format <major>.<minor>.<patch>[-<prerelease>]. The version number is incremented based on the following rules: Changelogs for Hey Wiki can be seen at MCW:Hey Wiki/Releases. Hey Wiki supports multiple versions of Minecraft. Every Minecraft version is assigned a support status: The current Minecraft release and the master branches are always Active. Pull requests should almost always go to master. If they're accepted, they should be cherry-picked to other Active branches. When a new snapshot releases, master branch is updated to that snapshot. Snapshots might receive only one version or no version at all. Only Fabric is supported for snapshots. Old Minecraft versions are provided with Long Term Support (LTS) based on their popularity and the community's interest. LTS versions receive Active support at first. After some time, they will be downgraded to Maintenance. Old snapshots are not supported. The following table shows which versions are supported: Language support Hey Wiki is available in multiple languages. It is translated by the community on Crowdin. It currently supports the following languages: Navigation Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/File:StaffPicks.png] | [TOKENS: 105]
File:StaffPicks.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 page uses this file (also see what links to it): Global file usage The following other wikis use this file: Metadata This file contains additional information, probably added from the digital camera or scanner used to create or digitize it. If the file has been modified from its original state, some details may not fully reflect the modified file. Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/Copper_Torch] | [TOKENS: 359]
Copper Torch Yes Yes (64) Any tool 0 0 Yes (14) Yes No No A copper torch is a non-solid block that emits light. Copper torches can also be used to craft copper lanterns. Contents Obtaining Copper torches can be broken instantly using anything, and drop themselves as an item. A copper torch is removed and drops itself as an item if: Usage Copper torches can be placed on the top or the sides of most solid blocks, although some blocks require sneaking. Being non-solid, copper torches have no collision box. More information about placement can be found at Opacity/Placement. Gravity-affected blocks like sand and gravel do not start falling if the space immediately beneath is occupied by a copper torch. Falling blocks break if they fall onto a solid block with a copper torch above it. If there is an air block under the copper torch, the falling blocks fall through the copper torch onto the surface below. Copper torches do not oxidize. The copper is being used as part of the torch's fuel and not the base. Copper torches give off a light level of 14. Copper torches also melt snow layers within 2 blocks and ice within 3 blocks (taxicab distance). When the Render Dragon Features for Creators experiment is enabled in Minecraft Preview, the top part of copper torches emits colored point lighting with #86ca59. This causes the bottom part of the copper torch to render a small square shadow. Sounds Java Edition: Bedrock Edition: Data values Java Edition: Bedrock Edition: Java Edition: Wall Bedrock Edition: History Issues Issues relating to "Copper Torch" are maintained on the bug tracker. Issues should be reported and viewed there. Trivia Gallery References Navigation Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/Marketplace?action=edit&section=20] | [TOKENS: 212]
Editing Marketplace (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. Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/Polished_Tuff] | [TOKENS: 196]
Polished Tuff No Yes (64) 6 1.5 No No No No 43 TERRACOTTA_GRAY Polished tuff is a polished variant of the tuff block. Polished tuff's appearance matches to that of other polished rock materials, having two lighter edges and two darker edges on each face to mimic the appearance of a singular large and smoother stone. Contents Obtaining Polished tuff drops as an item if mined by any pickaxe. If mined without a pickaxe, it drops nothing. Polished tuff blocks generate naturally in trial chambers as the primary ceiling block of many rooms. Usage Polished tuff can be placed under note blocks to produce "bass drum" sounds. Sounds Java Edition: Bedrock Edition: Data values Java Edition: Bedrock Edition: Videos History Issues Issues relating to "Polished Tuff" are maintained on the bug tracker. Issues should be reported and viewed there. Gallery References Navigation Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/Minecraft_Wiki:Hey_Wiki#searchInput] | [TOKENS: 726]
Minecraft Wiki:Hey Wiki Minecraft Wiki Main contributors Java 1.8.0 June 1, 2024 ~228 KiB LGPL-3.0 Yes (GitHub) Hey Wiki is a client mod for Java Edition made by the Minecraft Wiki community. It allows players to quickly open the wiki page of the block, item, or entity that the camera is aimed at, whether it is from the vanilla game or another mod. Download on Modrinth Download on CurseForge Contents Features It is also supported to use MCBrowser and MCEF for in-game browsing. Optionally, the following behaviors in the config menu can be changed: These commands are available: Opening a page with a command does not cause the confirmation screen to appear. Hey Wiki supports [[wiki links]] in chat. When a message is sent with [[wiki link]] syntax, it will automatically be replaced with a clickable link. Interwiki links and other namespaces are supported. For example: Supported wikis The latest version of Hey Wiki supports the following wikis: Resource packs can be used to add support for other wikis. An issue can be filed in case a wiki should be added to the default list. APIs Hey Wiki provides several ways mod, mod pack, data pack, and custom server developers can leverage to support their creation. Hey Wiki supports using resource pack to add support for other wikis. To do so, create a JSON file in the assets/<namespace>/wiki_family/ folder in your resource pack with the following format: You also want to include a translation file in assets/<namespace>/lang/ folder with the following format: Data pack and custom server authors can use heywiki:identifier, heywiki:translation_key and heywiki:fallback_title in custom_data data component to provide custom namespace and name for an item. However, this only accounts for custom items. For 1.20.4, you can populate these fields directly in NBT. You need to use the method above to register a new wiki with a custom namespace using resource pack. If it is not feasible to ask your players to download a resource pack, we can also ship it with the mod itself. For example, on "niceserver", to have a bone item to resolve to the "Drill" page, you will first need to register the "niceserver" namespace per above. Then you can give the player this item: Dependencies For Fabric: For NeoForge: Versioning Hey Wiki uses Semantic Versioning in the format <major>.<minor>.<patch>[-<prerelease>]. The version number is incremented based on the following rules: Changelogs for Hey Wiki can be seen at MCW:Hey Wiki/Releases. Hey Wiki supports multiple versions of Minecraft. Every Minecraft version is assigned a support status: The current Minecraft release and the master branches are always Active. Pull requests should almost always go to master. If they're accepted, they should be cherry-picked to other Active branches. When a new snapshot releases, master branch is updated to that snapshot. Snapshots might receive only one version or no version at all. Only Fabric is supported for snapshots. Old Minecraft versions are provided with Long Term Support (LTS) based on their popularity and the community's interest. LTS versions receive Active support at first. After some time, they will be downgraded to Maintenance. Old snapshots are not supported. The following table shows which versions are supported: Language support Hey Wiki is available in multiple languages. It is translated by the community on Crowdin. It currently supports the following languages: Navigation Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/File:Copper_Trapdoor_JE2_BE2.png] | [TOKENS: 161]
File:Copper Trapdoor JE2 BE2.png Summary Copper trapdoor render Java Edition revision 2 Bedrock Edition revision 2 This is a file pertaining to Minecraft. Render created by uploader using Minecraft assets Render: JjlrjjlrAssets: Mojang Studios 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 63 pages use this file (also see what links to it): Global file usage The following other wikis use this file: View more global usage of this file. Metadata This file contains additional information, probably added from the digital camera or scanner used to create or digitize it. If the file has been modified from its original state, some details may not fully reflect the modified file. Navigation menu
========================================
[SOURCE: https://minecraft.wiki/w/File:Resistance_JE1_BE1.png] | [TOKENS: 66]
File:Resistance JE1 BE1.png Summary 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 10 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/Special:EditPage/Template:Navbox_mods] | [TOKENS: 219]
Editing Template:Navbox mods 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: Navigation menu
========================================