text stringlengths 0 113k |
|---|
[SOURCE: https://minecraft.wiki/w/Cut_Copper_Slab#Oxidized] | [TOKENS: 318] |
Cut Copper Slab Yes Yes (64) 6 3 No Double slab: No Single slab: Partial (blocks light)[JE only]Partial (diffuses sky light)[BE only] Yes No No A cut copper slab is a decorative slab variant of cut copper that generates in trial chambers and is used for building. Unlike other types of slabs, cut copper slabs can oxidize over time. Contents Obtaining Cut copper slabs can be broken with stone pickaxes or higher. If mined without a pickaxe, they drop nothing. Waxed cut copper slabs generate naturally in trial chambers. Usage Non-waxed cut copper slabs have four stages of oxidation (including the initial normal state). Lightning bolts and axes can remove the oxidation on cut copper slabs. They can be waxed with a honeycomb to prevent 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 In Bedrock Edition, when a cut copper 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: Achievements Advancements History Issues Issues relating to "Cut Copper Slab" are maintained on the bug tracker. Issues should be reported and viewed there. Gallery References Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Add-on?action=edit§ion=15] | [TOKENS: 224] |
Editing Add-on (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 4 hidden categories: Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Stripped_Wood] | [TOKENS: 319] |
Stripped Wood Yes Yes (64); same type only 2 2 No No Stripped wood or stripped hyphae is a variant of wood obtained when any axe is used on wood or hyphae respectively. Contents Obtaining Stripped wood and hyphae can be broken by hand, but using an axe is the fastest. Stripped oak wood can generate in plains villages. Stripped spruce wood can generate in snowy tundra villages. Stripped wood or hyphae can be crafted out of four matching stripped logs or stems, yielding three stripped wood or hyphae as a result. Using an axe on wood or hyphae turns it into stripped wood or hyphae, which act the same as regular wood or hyphae. Usage Stripped wood and hyphae can be placed in three orientations, similarly to normal wood. Stripped wood can be used as a fuel in furnaces, smelting 1.5 items per block. Stripped hyphae cannot be used as a fuel in furnaces. Cocoa beans can be placed on the side of stripped jungle wood to grow new cocoa pods. Stripped wood and hyphae can be placed under note blocks to produce "bass" sounds. Sounds Java Edition: Bedrock Edition: Java Edition: Bedrock Edition: Java Edition: Bedrock Edition: Data values Java Edition: Bedrock Edition: Java Edition: Bedrock Edition: History Issues Issues relating to "Stripped Wood" are maintained on the bug tracker. Issues should be reported and viewed there. See also Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Tutorial:Programs_and_editors/Modding] | [TOKENS: 125] |
Tutorial:Programs and editors/Modding BlockLauncher Pro Forum Website Craften Terminal Forum Website Enigma Website Kovacic's Mod Pack Website Live_ModList Forum Magic Launcher Forum Matcher Website MCManager Forum Website MCModInstaller Forum Website MCPatcher Forum MCP Mapping Viewer Forum MCreator Website Mod Coder Pack (Formerly Minecraft Coder Pack) Website Minecraft External Modloader Forum Website Minecraft Modinstaller Website Minecraft Mod Mover Forum Minemod Omni Tool Forum Moddery Website MultiMC Forum Website Prism Launcher Website ROFL's Mod Installer Forum Website SGSoft Mod Installer Website The MCAnimator Website The Modding Table Forum Website Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/13w23a] | [TOKENS: 150] |
Java Edition 13w23a Java Edition June 7, 2013 Snapshot 1.6.1 Client (.json)Server (.exe) 67 Java SE 6 ◄ 13w22a 13w23b ► 13w23a is the eleventh snapshot for Java Edition 1.6.1, released on June 7, 2013. Contents Additions naturalRegeneration /spreadplayers Splash screens Changes Glistering melons Golden apples Status effects Resource packs Fixes 4 issues fixed From the 1.6.1 development versions From the previous development version Trivia References Navigation * indicates a reupload | † indicates a lost version | ‡ indicates a version with a variant Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Version_formats#Alpha] | [TOKENS: 3876] |
Version formats Each edition and development phase of Minecraft uses a different versioning system. Contents Java Edition During pre-Classic, versions were not numbered, and instead have retroactively been labeled by Mojang as rd- followed by the day of month, hour, and minute the version was built. For example, rd-160052 was built on May 16 at 00:52 (Sweden time). rd-20090515 is the only build not to follow this trend, instead being labeled by the year, month, and day it was built, in that order. rd stands for RubyDung, being a game Notch previously worked on. Initial versions of Classic were not numbered. The Minecraft Wiki refers to them using the system Mojang retroactively used for pre-Classic, but with a mc- prefix instead of rd-. During mc-161648, user fartron requested that Notch add a build count, which was added in the next version, 0.0.2a. This was the phase of what is now called Classic, and versions were labeled using three numbers followed by the letter "a", and bug fix patches were denoted by an underscore followed by a revision number (e.g., 0.0.18a_02 is the second bug fix patch for 0.0.18a). The "a" stands for "alpha", which is what this development phase was originally called. (This "0.0.xa" versioning system was also used by Notch in a few years earlier in his game Wurm Online.) Notch mused simplifying the format to remove the redundant "0.0." repetition, using the example of changing "0.0.13a_03" to "0.13.3a", but did not do so. During Classic version 0.0.23a_01, Notch announced that he was going to be changing the versioning system, removing one of the zeroes as well as the "a". This coincided with the development of Survival Test, so versions during this time were appended with the word "SURVIVAL TEST" (which sometimes contained underscores, such as in version 0.24_SURVIVAL_TEST). After 0.27 SURVIVAL TEST, the survival testing phase was complete, and the version format now only had two numbers (the first of which was a zero) followed by an optional underscored bug fix patch (e.g., 0.28_01). Using an underscore to separate out a revision likely originated from the versioning system Java used at this time. There are several unreleased development builds of Classic versions, which were labeled the same as their public release counterparts (e.g. 0.0.14a) in-game, despite differences in code. Classic 0.24 is the only exception to this rule, as its private development versions were labeled simply "0.24" in-game, whereas the full release was labeled "0.24_SURVIVAL_TEST". During Indev, the version number remained at 0.31 for many versions. Midway through the development of Indev, Notch changed the version number from "0.31" to just "Minecraft Indev" ("Indev" is a portmanteau of "in development"). When Infdev started, the version was just changed to "Minecraft Infdev" ("Infdev" is a portmanteau of "infinite development", as Notch added infinite world generation). Due to not having any version number visible in-game, individual Indev and Infdev versions are numbered in the launcher and on this wiki based on the year, month, and day of their release. (When necessary for disambiguation, this date is then followed on this wiki by the hour for multiple releases within the same day.) For example, Infdev 20100625-0922 is the unofficial name given to the Infdev version released on June 25, 2010, at 09:22 UTC. There are several builds of Indev 0.31 20091223-0040 which were never released to the public. Most were still labeled "0.30" in-game. Version numbers were re-added during Alpha, starting from version v1.0.1. The version format now was primarily a "v" followed by three numbers in the order "phase", "major", "minor". Minecraft was now in somewhat of a complete state, as it had left the "development" stages of Indev and Infdev, and as such, the "phase" counter was changed to "1". An optional underscored bug fix patch was also used in this development phase. For example, Alpha v1.2.3_02 is the second bug fix patch ("_02") for the third minor revision (".3") of the second major version (".2") of Alpha. Beta reset the version number back to 1.0 after Alpha v1.2.6, and Beta version numbers now only had two numbers followed by an optional underscored bug fix patch (e.g., Beta 1.1_01 was released to fix a major bug in Beta 1.1). This format was used somewhat inconsistently; for example, Beta 1.7 was followed by Beta 1.7_01, which was then followed by Beta 1.7.2. Beta also started releasing preview versions of major releases in the form of "pre-releases". These pre-releases took the form of the major version number followed by the word "Pre-release" and then a revision number. For example, Beta 1.8 Pre-release 2 was the second pre-release for Beta 1.8. Pre-releases for release 1.0.0, which was then called Beta 1.9, omitted the hyphen from the word "Pre-release". When it was decided that Beta 1.9 would be instead released as full version 1.0, future development versions were classified as release candidates, with RC1 and RC2 being the only two. The full release of Java Edition, then known as just Minecraft, reset the version number to 1.0.0. This version is the only release version not to omit the final ".0" for a major release (such as in version 1.1). Game drops, introduced in 2024, increased the minor version number like hotfixes did despite being content updates. Starting in 2026, release versions are formatted as "YY.D.H", where "YY" is the two-digit year, "D" is the drop number within that year, and "H" is the hotfix counter for that drop. Initial drop releases do not get a hotfix number. After the full release of Minecraft, public development versions called "snapshots" have been published most weeks showing the development of that version at the time. Prior to 2026, snapshots used a very different format to other releases, being of the form "YYwNNn", where "YY" is the two-digit year, "w" stands for "week", "NN" is the two-digit week number of that year, and "n" is a revision letter which increments each time a snapshot is released in that week. For example, 18w10d was released as the 4th iteration (18w10-d) in the 10th week (18-w10-d) of 2018 (18-w10d). Starting in 2026, snapshots use the same naming scheme as pre-releases and release candidates (Version Snapshot N), with the first being 26.1 Snapshot 1 (the first snapshot for 26.1). Pre-release versions between 1.2.1 and 1.7.4 took the form of full releases, which then incremented the minor version number for a new version. For example, 1.7 was a pre-release for 1.7.2. From 1.7.6 until 1.13.2, pre-releases were named as their full release counterparts followed by "-pre" and a revision counter (Except for pre-release 1.11.1, which still uses the previous pre-release format). For example, 1.12-pre7 is the seventh pre-release for 1.12. Since 1.14, the word "pre-release" is spelt out in full. (However, the launcher nonetheless continues to use the shortened form with "-pre".) For example, 1.14 Pre-Release 3 is the third pre-release for 1.14. Release candidates were reintroduced during 1.16 with 1.16 Release Candidate 1. The phrase "Release Candidate" is always spelt out in full in title case in the version string, though the launcher uses a shortened format similar to pre-releases (for example, 1.18-rc4 is used in the launcher for 1.18 Release Candidate 4). These usually come after pre-releases; however, 1.19.1 notably reverted back into its pre-release stage after the release of 1.19.1 Release Candidate 1. 1.18 introduced the idea of experimental snapshots with 1.18 Experimental Snapshot 1. Subsequent experimental snapshots for 1.18 had the name in lowercase. 1.19 also had an experimental snapshot, but it did not use this naming format, being instead called Deep Dark Experimental Snapshot 1. Experimental snapshots have not been used since Mojang started using Experiments to test 1.20 features in the 22w42a snapshot for 1.19.3. Java Edition Combat Tests are, apart from 1.14.3 - Combat Test, named with the words "Combat Test" followed by an incrementing digit, and sometimes then followed by an incrementing letter for patches to specific major combat test versions. For instance, Combat Test 4 is the next major iteration of the combat tests after Combat Test 3. After Combat Test 6, versions named with the words "Combat Test" followed by an incrementing digit are development versions of the full release, which is named after those development versions followed by a letter. For instance, Combat Test 7 and Combat Test 7b are development versions of Combat Test 7c and Combat Test 8 is a development version of Combat Test 8b. Pocket Edition Pocket Edition versions in this development phase took the form of a "v" followed by three numbers: phase, major, and minor, followed by the word "alpha". The phase number during Alpha was 0, and the major and minor numbers incremented each release (when the major version number was incremented, the minor version was reset to 0). Development builds in this phase were labeled as their parent version followed by "build" and the build counter. For example, v0.14.0 alpha build 1 was the first build for Alpha version 0.14.0. Release versions kept the same format as in Alpha, but incremented the phase number to 1 and removed the word "alpha" after the three numbers. Development versions in this time were known as "alpha" versions (not to be confused with the development phase called "alpha") and took the form of the word "alpha" followed by a four-digit version number (major.minor.patch.revision). The first three digits are the parent version (alpha 1.0.0.1 was a development build for 1.0.0) and the fourth number is the build revision, which is not necessarily incremented by 1 each release. Bedrock Edition In 1.2.0, the "Pocket Edition " subtitle was dropped, and development versions were renamed from "alpha" to "beta"; the version number format did not change (e.g., beta 1.8.0.8 was a development build for 1.8.0). From 1.14.20, Bedrock Edition minor version numbers started being having 2 or more digits, with the last digit set aside for hotfixes or platform-specific bug fixes. The exception for this is if the previous substantial version released was the first release in a major update cycle, in which case it would be 1 digit as the first version of the minor version would otherwise be 0. Previously, platform-specific bug fix updates were named through either including simply increasing the minor version number, like in 1.13.2, or adding a revision number at the end of the version, e.g. 1.14.0.12. Starting from 1.16.0, Bedrock Edition major version numbers have matched Java Edition. While initially returning to the old system for platform-specific updates (e.g. 1.16.1.03), Bedrock Edition returned to the system introduced in 1.14.20 in 1.16.10. Before this, Bedrock Edition updates changed the major version number for content updates and the minor version number for patches. However, in order to maintain major version number parity, these increase the minor version number. In the minor versions for 1.16, the minor version segment used up to three digits to denote the content of that version. Incrementing the third-to-last digit if present (e.g., 1.16.200) represented a major supplementary content update, incrementing the second-to-last digit (e.g., 1.16.210) represented a minor supplementary update, while incrementing the last digit (e.g., 1.16.201) represented a bug-fix supplementary update. Since 1.17.0, the third-to-last digit has only been used as an extension of the second-to-last digit (see 1.21.100, which followed 1.21.90), and updates to the stable channel have not used the revision number. The first digit(s) of the minor version represents the minor update cycle of the major update (if not present, the minor update cycle is 0), while the last digit is used to represent the hotfix within the minor update cycle. For the first release within a minor update cycle, the last digit is zero. These first releases are more substantiative than hotfix updates, and can include game drops, parity changes, substantial amounts of bug fixes, and technical changes, among other things. For example, 1.19.73 is the third hotfix of the seventh minor update cycle for Bedrock Edition in 1.19. Platform-specific bug fix updates also count as hotfixes. The first(A) digit indicated a version above alpha, the second was for major(M) updates, and the third was for minor(m) and hotfix(H) updates.(A.MM.mH) However, some minor update cycles have been merged with the minor update cycle following them, like 1.21.10 being merged into 1.21.20. In addition, in some occasions the first release of a minor update cycle has released with a separate version number for a different platform, for example 1.20.60 releasing as 1.20.61 on the Nintendo Switch, hence leaving the first hotfix released under the update as 1.20.62. 1.21.111 was the first version under the current version formatting scheme in which the first release of a minor update cycle had a minor version number ending with a digit other than 0 on all platforms. This is because Mojang needed to fix an additional bug at the last minute. After the 1.21.130 update cycle, a new numbering system was introduced, where the phase number was dropped (outside of some internal version numbers), and the major version number was replaced by a two-digit year number. For example, 26.0. The minor version segment increments the same way as before, though it resets to 0 when the year number increases. Betas/Previews take the form of their parent version with a last digit incremented to denote the revision number, i.e. phase.major.minor.revision (before 2026) or year.minor.revision (from 2026). This version number is prefixed with either the word "Preview" or "beta", depending on device. The revision number is not necessarily incremented by 1 each release, and where the revision number starts at the beginning of a beta/Preview cycle has changed over time. Initially they started at a low number, usually between 0 and 3, then starting with the 1.14.30 update cycle they usually started at 50 or 51, and since the 1.17.10 update cycle they have usually started at 20 or 21. On Android, the version number is internally stored as a fixed-width number — the Android version code. For instance, 982101020 is the version code for Preview 1.21.10.20; this number can be split as "98-21-010-20", with the first group representing the distribution (x86_64) and the remaining three being the major, minor, and build number.[note 1] On Android, the version number is also stored as a version name, which is usually shown in the device's settings app. Before the 2026 version update, the Android version name matched the version number. After the update, the version name is the version number with 1. at the start. For instance, the version name for Beta 26.0.25 is 1.26.0.25. Within Mojang is a private naming convention for minor releases of Bedrock Edition. This naming scheme is of the form "RnUm", where n is the major version part and m is the major segment of the minor version part. For instance, "R20U7" (release 20 update 7) refers to the first released Bedrock Edition 1.20.7x version. Legacy Console Edition The many different console versions use entirely different versioning formats. Xbox 360 Edition versions used "title updates": the letters "TU" followed by a number. Xbox One Edition updates were called "content updates" and use the same format as Xbox 360 but with the letters "CU" instead of "TU". As mandated by PlayStation software, PlayStation Editions used a decimal three-digit version number (an integer followed by a two-digit number from 00–99, starting from 1.00; version 1.99 must be followed by 2.00), which may sometimes skip numbers. Wii U Edition versions are known as "Patches", and used the word "Patch" followed by a number. Nintendo Switch Edition versions used both patches and a three-part version number starting from 1.0.1, but only incremented the minor version each release. Notes References Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/File:Cobbled_Deepslate_Stairs_JE3.png] | [TOKENS: 112] |
File:Cobbled Deepslate Stairs JE3.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 49 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:Marketplace_Hole.jpeg] | [TOKENS: 138] |
File:Marketplace Hole.jpeg Summary Kai, a wolf, a creeper, an enderman, a zombie, a bat, and a cave spider gazing upon the Minecraft Marketplace. 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 4 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/Add-on?action=edit§ion=17] | [TOKENS: 224] |
Editing Add-on (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 4 hidden categories: Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Fire_charge] | [TOKENS: 323] |
Fire Charge Common Yes Yes (64) JE: 64 A fire charge is an item that can be used as a single-use version of a flint and steel or shot as a small fireball from a dispenser. Contents Obtaining Despite firing small fireballs, blazes do not drop fire charges. When given a gold ingot, piglins have a ~8.53% (40⁄469) chance to barter a single fire charge. During ominous trials, each ominous trial spawner has a 1⁄5 chance to dispense a fire charge on top of either a player or a mob it spawns. The fire charge is directly dispensed into the world and cannot be obtained in the inventory. Usage Fire charges can be used as ammunition in dispensers or as a single-use substitute for a flint and steel. When used, it instantly places a fire, similar to flint and steel. But, unlike flint and steel, the fire charge is consumed in the process. It can prime TNT and light nether portals, campfires, candles, cakes with candles, and creepers[Java Edition only]. When a fire charge is fired from a dispenser, it shoots a small fireball. However, a player cannot simply use a fire charge while holding it to shoot a small fireball. Sounds Java Edition: Bedrock Edition: Data values Java Edition: Bedrock Edition: Achievements Advancements Videos History Issues Issues relating to "Fire Charge" are maintained on the bug tracker. Issues should be reported and viewed there. Gallery See also References External links Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/File:Start_a_New_Story.png] | [TOKENS: 108] |
File:Start a New Story.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 2 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/Nintendo_Switch_Edition_1.0.7] | [TOKENS: 88] |
Nintendo Switch Edition 1.0.7 Nintendo Switch Edition August 29, 2017 Build 1.12.1622.0 ◄ 1.0.6 1.0.8 ► 1.0.7 (Patch 7) is a version of Nintendo Switch Edition released on August 29, 2017. Contents Additions Changes Fixes 41 issues fixed See also References Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Cobbled_Deepslate_Wall] | [TOKENS: 168] |
Cobbled Deepslate Wall No Yes (64) 6 3.5 No Yes Yes No No A cobbled deepslate wall is a decorative wall variant of cobbled deepslate that generates in ancient cities and is used for building. Contents Obtaining Cobbled deepslate walls can be mined using any pickaxe. If mined without a pickaxe, they drop nothing. Cobbled deepslate walls generate naturally within ancient cities. Usage Cobbled deepslate walls can be placed under note blocks to produce "bass drum" sounds. Sounds Java Edition: Bedrock Edition: Data values Java Edition: Bedrock Edition: Java Edition: Bedrock Edition: History Issues Issues relating to "Cobbled Deepslate Wall" are maintained on the bug tracker. Issues should be reported and viewed there. Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Advancement#Hot_Tourist_Destinations] | [TOKENS: 886] |
Advancement Advancements are a way to gradually guide new players into Minecraft and give them challenges to complete, similar to the system of achievements in Bedrock Edition. Contents Obtaining Advancements can be completed in any game mode, and are obtained and saved per world. Advancements can also be granted (and revoked) using the /advancement command. Although advancements guide players logically through the game, they are independent of each other; an advancement can be completed without having completed the advancements "before" it. There are 125 advancements: 16 in the Minecraft tab, 23 in the Nether tab, 9 in The End tab, 47 in the Adventure tab, and 30 in the Husbandry tab. When an advancement is obtained, a sliding toast notification appears in the top right corner. Each notification is accompanied by a chat message, if the game rule show_advancement_messages is set to true (i.e., enabled). The color of the header text in the notification depends on the advancement; normal and goal advancements have yellow header text, while challenge advancements have pink header text. Completing a normal advancement causes the header text to display "Advancement Made!", completing a goal advancement results in a "Goal Reached!" header, and completing a challenge advancement shows "Challenge Complete!". In addition, a sound effect plays and experience is rewarded when completing most of these advancements. Unlike the others, the five "root" advancements in each tab, each of which appears as the left-most advancement in its tab, and have the same name as its tab, do not cause a chat message or notification to appear. Interface The button to access the Advancements screen is found on the pause menu screen. The player can also open this screen by pressing L (this can be changed in the in-game options menu). The advancement system involves several trees composed of advancements, each tree beginning with a root advancement from which several branches diverge. By clicking and dragging, the player can view different branches of an advancement tree. Each tree is categorized into different tabs, defined by the root advancements. Tabs are not visible if no advancements in the tab have been unlocked. There are five tabs in vanilla Minecraft: Each tab has a different background with a repeating texture. Tabs appear when at least one advancement in that tab has been made. Tabs are ordered left to right, based on when the first advancement in each tab was made. Advancement icons display a header name and description when hovered over. The advancement descriptions have a unique color depending on the type of advancement with normal and goal advancements having green descriptions and challenge advancements having purple ones. As more advancements are unlocked, new ones become visible, with up to two advancements being displayed ahead of an unlocked one. Unlocked advancements show all of its direct parents advancements (the advancements between the root advancement of the tab and it), even those that have not been unlocked (but show only up to 2 advancements downstream of advancements already unlocked). Nine advancements, "How Did We Get Here?", "Voluntary Exile", "Hero of the Village", "Arbalistic", "You've Got a Friend in Me", "Smells Interesting", "Birthday Song", "Little Sniffs", and "Planting the Past" are hidden advancements, meaning that they cannot be viewed by the player until they have been unlocked, regardless of if its child advancement(s) (any advancement after it, including all branches), if any have been unlocked, which would normally display its parent advancements (as advancements can be unlocked and completed in any order). If the player has not completed/unlocked any advancements, the interface shows a black background with white text reading "There doesn't seem to be anything here... :(". The icon frames of advancements can vary in appearance based on difficulty, and whether or not it was completed. A legend is provided below: Extra advancements and tabs can be added and customized with the use of JSON files and data packs. List of advancements The source of the effects is irrelevant for the purposes of this advancement. Other status effects may be applied to the player, but are ignored for this advancement. JSON format Sounds History Note that before 17w13a, Java Edition had a feature called Achievements that served a similar purpose. Issues Issues relating to "Advancement" are maintained on the bug tracker. Issues should be reported and viewed there. Trivia Gallery See also References Navigation More More Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Slab?section=2&veaction=edit] | [TOKENS: 833] |
Slab A slab is a half-height version of its respective block. Contents Variants There are 61 variants of slabs: Obtaining All slabs have the same crafting recipe format, with one block resulting in two slabs each. All slabs except wooden slabs and bamboo mosaic slabs can be obtained by stonecutting, at the same rate as with crafting. Usage Slabs can occupy either the top half or the bottom half of a block, or both: Slabs cannot be oriented vertically. In Bedrock Edition a single slab (top or bottom) is transparent to light and diffuses sky light, while a double slab is opaque. The empty half of a slab block is also transparent to mobs, unlike other transparent blocks such as fences and glass, which players can see through but mobs cannot. A bottom placed on top of a hopper is transparent to items; the items fall through the bottom slab into the hopper. Without a hopper attached below, a bottom slab behaves as a solid surface. Falling block entities (like sand, gravel, and concrete powder) turn into their dropped form if they land on a bottom slab, as when they fall on a torch. Mobs see a slab as a full block when pathfinding. They can spawn on top slabs and double slabs, but not on bottom slabs. This can be used to prevent mob spawning in certain areas, such as mob farms. Generally, the top face of top slabs, the bottom face of bottom slabs, and all faces of double slabs are handled as solid blocks. Due to this, blocks that require a solid surface for placement can be placed on these faces. Double slabs are handled as a single block instead of two different slabs; as such, breaking one destroys the whole block and drops two slabs, as opposed to breaking only one slab within the same block-space. "Double slabs" that are not aligned to the grid (i.e. a bottom slab on top of a top slab) are handled as separate blocks and are broken individually. Redstone dust placed on a top slab receives signals from redstone dust one block lower and adjacent, but cannot transmit signals down to that block. Due to the way blast rays propagate from an explosion, bottom slabs provide extremely effective absorption to explosions directly on top of them. In some cases, only the slab is destroyed from a TNT explosion directly on top of it. Explosions from end crystals and creepers are also weakened. Sneaking reduces the player's hitbox height to 1.5 blocks, allowing the player to fit through such a gap (for example, walking over a bottom slab with one block of air above it, or in a two block high tunnel with an upper slab on the ceiling). A player cannot walk from a block of soul sand directly up to a bottom slab without jumping – this applies not just to soul sand, but to any block 7⁄8 of a block high or shorter, because the maximum step height of the player is 0.6 of a block. The player can walk off a bottom slab while sneaking, because the sneaking prevents falling only when the distance is higher than one half block. If a single slab is placed in a water source block, or water is placed onto a single slab using a water bucket, the empty half of that slab's block is waterlogged. If a slab is placed in flowing water, a pocket of air is created in the unfilled half of the block. If the player's head is in this pocket, the player can breathe and see as clearly as from an air block. In Java Edition, if a single slab is placed in between two water sources or waterlogged blocks, the slab becomes waterlogged. A minecart on powered rails is not repelled by a slab, although it is repelled by a slab with a minecart on top. Block states Java Edition: Bedrock Edition: History Gallery Issues Issues relating to "Slab" are maintained on the bug tracker. Issues should be reported and viewed there. Trivia References External links Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/File:Frozen_River.png] | [TOKENS: 62] |
File:Frozen River.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 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/Start_a_New_Minecraft_Story_%E2%80%93_Official_Trailer] | [TOKENS: 511] |
Start a New Minecraft Story – Official Trailer Mojang cinematic Brokendoll January 12, 2023 2:05 Start a New Minecraft Story is an animated trailer, promoting several releases both official and third party on the Marketplace, with a plot concerning several players exploring the worlds of the content. Contents Summary The video begins on a shot of a large city with dozens of characters from different Marketplace content, exploring buildings labeled things such as "Hardcore Mode." Several of these people enter a building, where they are approached by a man in a top hat who welcomes them to the Minecraft Marketplace, promising that "behind every door, a new story awaits." Before he could finish, everyone rushes into the first door they see. They end up in the map Advanced Dragons 2, where one player is frightened by the sight of dragons. Another finds them cute and runs off to ride them. They eventually end up in a jungle, where someone using the Cadmus skin flicks a lever and opens up another door. They emerge in another world, which someone remarks looks the same as the last one, disappointed and bitter. Luckily, the entrepreneur appears and reveals to them the Ultra Cute texture pack. The entrepreneur next appears in a flooded hole, luring the players down into Bikini Bottom where they get to meet SpongeBob SquarePants and friends. Satisfied with that DLC, one of the players demands "more" and opens the door to the City Living DLC, before transitioning to a parody of a scene commonly seen in Scooby-Doo involving a creeper. The situation is resolved when one of the players transforms into a cat and scares the creeper away, transitioning into a brief sequence showcasing the Morph into Mobs world. Another player asks for "something magical," and is then invited into Magic Kingdom where they get to meet Mickey Mouse and friends. The video ends with the entrepreneur breaking the fourth wall and inviting the viewer to join the Marketplace. Characters Featured content Transcript Videos Quotes Whether you’re a farmer or a fighter, a builder or a burrower, discover a new chapter of ideas at Minecraft Marketplace! Trade your Minecoins for mutated mobs, magical adventures, mini-games, and more. Plus, kickstart your adventure with two fun-filled content bundles: the new Skyblock and Dinosaur packs! What’ll your next story be? Our latest trailer for Minecraft Marketplace. Two minutes of fun and mad adventures as the characters jumps between the worlds of the Marketplace favourites. 🎵 Trivia Gallery References External links Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/File:MinecraftxUniversal_NewYearsCelebration_.net_BlogEditorial_1170x500.png] | [TOKENS: 151] |
File:MinecraftxUniversal NewYearsCelebration .net BlogEditorial 1170x500.png Summary Noor, Sunny, Kai, and Makena driving a bus with various Universal characters, from How to Train Your Dragon to Jurassic Park. 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: 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/Mod#cite_ref-signature-validation_20-1] | [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/Wildfire] | [TOKENS: 164] |
Wildfire Hostile Monster The Nether The wildfire, originally known as Mob D or the "Hovering Inferno", was a proposed mob featured in the Mob Vote during MINECON Earth 2017, alongside the barnacle, the phantom and the great hunger. It was a type of blaze with its body parts looking like shields in order to defend itself from attacks. This mob would spawn with groups of blazes randomly to attack the player in the Nether with a dangerous shock wave attack. Jens Bergensten argued that viewers should vote for Mob D because it would make the Nether "even more scary and exciting". The wildfire received 24% of the votes in the first round and moved onto the second, losing with 28% of the votes. Contents Preview video History Gallery Trivia References Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Slab?action=edit§ion=3] | [TOKENS: 224] |
Editing Slab (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 3 hidden categories: Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Slab?section=3&veaction=edit] | [TOKENS: 833] |
Slab A slab is a half-height version of its respective block. Contents Variants There are 61 variants of slabs: Obtaining All slabs have the same crafting recipe format, with one block resulting in two slabs each. All slabs except wooden slabs and bamboo mosaic slabs can be obtained by stonecutting, at the same rate as with crafting. Usage Slabs can occupy either the top half or the bottom half of a block, or both: Slabs cannot be oriented vertically. In Bedrock Edition a single slab (top or bottom) is transparent to light and diffuses sky light, while a double slab is opaque. The empty half of a slab block is also transparent to mobs, unlike other transparent blocks such as fences and glass, which players can see through but mobs cannot. A bottom placed on top of a hopper is transparent to items; the items fall through the bottom slab into the hopper. Without a hopper attached below, a bottom slab behaves as a solid surface. Falling block entities (like sand, gravel, and concrete powder) turn into their dropped form if they land on a bottom slab, as when they fall on a torch. Mobs see a slab as a full block when pathfinding. They can spawn on top slabs and double slabs, but not on bottom slabs. This can be used to prevent mob spawning in certain areas, such as mob farms. Generally, the top face of top slabs, the bottom face of bottom slabs, and all faces of double slabs are handled as solid blocks. Due to this, blocks that require a solid surface for placement can be placed on these faces. Double slabs are handled as a single block instead of two different slabs; as such, breaking one destroys the whole block and drops two slabs, as opposed to breaking only one slab within the same block-space. "Double slabs" that are not aligned to the grid (i.e. a bottom slab on top of a top slab) are handled as separate blocks and are broken individually. Redstone dust placed on a top slab receives signals from redstone dust one block lower and adjacent, but cannot transmit signals down to that block. Due to the way blast rays propagate from an explosion, bottom slabs provide extremely effective absorption to explosions directly on top of them. In some cases, only the slab is destroyed from a TNT explosion directly on top of it. Explosions from end crystals and creepers are also weakened. Sneaking reduces the player's hitbox height to 1.5 blocks, allowing the player to fit through such a gap (for example, walking over a bottom slab with one block of air above it, or in a two block high tunnel with an upper slab on the ceiling). A player cannot walk from a block of soul sand directly up to a bottom slab without jumping – this applies not just to soul sand, but to any block 7⁄8 of a block high or shorter, because the maximum step height of the player is 0.6 of a block. The player can walk off a bottom slab while sneaking, because the sneaking prevents falling only when the distance is higher than one half block. If a single slab is placed in a water source block, or water is placed onto a single slab using a water bucket, the empty half of that slab's block is waterlogged. If a slab is placed in flowing water, a pocket of air is created in the unfilled half of the block. If the player's head is in this pocket, the player can breathe and see as clearly as from an air block. In Java Edition, if a single slab is placed in between two water sources or waterlogged blocks, the slab becomes waterlogged. A minecart on powered rails is not repelled by a slab, although it is repelled by a slab with a minecart on top. Block states Java Edition: Bedrock Edition: History Gallery Issues Issues relating to "Slab" are maintained on the bug tracker. Issues should be reported and viewed there. Trivia References External links Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/PlayStation_Vita_Edition_1.76] | [TOKENS: 80] |
PlayStation Vita Edition 1.76 PlayStation Vita Edition Update Aquatic September 11, 2018 ◄ 1.75 1.77 ► 1.76 is a version of PlayStation Vita Edition released on September 11, 2018. This update brought the Update Aquatic to consoles. Contents Additions Changes Fixes 3 issues fixed Gallery See also References Navigation Navigation menu |
======================================== |
[SOURCE: https://minecraft.wiki/w/Add-on?section=20&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/File:Cobblestone_Wall_(ewU)_JE4.png] | [TOKENS: 69] |
File:Cobblestone Wall (ewU) JE4.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 56 pages use this file (also see what links to it): Global file usage The following other wikis use this file: Navigation menu |
======================================== |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.