Minecraft Version 1.13

Minecraft Version 1.13

- in Minecraft Stable Releases
43128
0

Download Version 1.13

Minecraft Version 1.13

Minecraft Version 1.13 is a free download which contains plenty of upcoming changes and unconfirmed features. It is a coming major update without a set release date. As mentioned, the version that you expect will bring bug fixes and technical features.

Download PC Gamer Minecraft Demo

The PC Gamer Minecraft Demo is a demo version of Minecraft Beta 1.3, that was bundled with the June 2011 issue of PC Gamer magazine (American edition, issue 214). It provides 100 minutes (equal to five days in-game) of gameplay, after which it will tell the player to buy the game in order to continue playing on the current map.

Download here!

General

Options

  • FS (Fullscreen) Resolution
    • Is used to change the resolution.
  • An option in chat settings to toggle automatic command suggestions (defaults on, otherwise hit tab to bring them up).
  • Options when editing a world to make a backup and open the backups folder.

Data packs

  • Like resource packs, but for loot tablesadvancementsfunctions, and structures.
    • Can be changed from world to server side.
    • Used by placing them into the world or server file, and it is also possible to use multiple data packs, or none at all
  • Data packs are .zipfiles or folders with a mcmeta in the root. See: Tutorials/Creating a resource pack#pack.mcmeta. The packs are located in (world)/datapacks/.
  • Structures will load from (world)/generated/structures/(namespace)/(file).nbtbefore checking data packs.
    • However, this directory should notbe used to distribute structures. Instead, move these files into data packs.
  • Reloadable using /reload
  • Structure: mcmeta, datafolder containing a namespace folder determining the namespace of its contents
    • A namespace should only contain the following symbols: 01​​234​5​6​78​9abcdefghijklmnopqrstuvwxyz-_
    • Inside the namespace folder, there can be folders for functions, loot_tables, advancementsand structures.

Blocks

  • Trapdoors, buttons and pressure plates made from all six types of wood.
  • A pumpkin block, without the face. The previous pumpkin block has been renamed “Carved Pumpkin”.
    • Right-clicking a pumpkin block with a shear will turn it into a carved pumpkin and make it spit out 4 pumpkin seeds.

Items

  • Items for bark blocks for all six types of wood.
  • Items for smooth quartz, smooth red sandstone, smooth sandstone, and smooth stone.
  • Debug stick to cycle between different block states. Used by right-clicking on a block.
  • The fade effects on fireworks can now be added by combining the firework star with dyes.

Commands

General

  • A command UI when typing commands in the chat.
    • Different components of commands will be displayed in different colors.
    • Errors will be displayed in red without having to run the command.
  • An nbtargument in target selectors.
  • A new command parsing library known as brigadier.

Specific commands

/data

  • A command that allows the player to get, merge, and remove entity and block nbt data
  • /dataget block <pos> [<path>] [<scale>]
    • Will return the NBT data from the block at posas its result (if a path is specified). A path can be specified to only retrieve that nbt data, but this is limited to numeric tags. An optional scale can be provided to scale the number retrieved.
  • /dataget entity <target> [<path>] [<scale>]
    • Will return the NBT data from one targetentity as its result (if a path is specified). A path can be specified to only retrieve that nbt data, but this is limited to numeric tags. An optional scale can be provided to scale the number retrieved.
  • /datamerge block <pos> <nbt>
    • Will merge the block nbt data at poswith the specified nbt
  • /datamerge entity <target> <nbt>
    • Will merge the entity nbt data from targetwith the specified nbt Merging player nbt data is not allowed.
  • /dataremove block <pos> <path>
    • Will remove nbt data at pathfrom the block at pos.
  • /dataremove entity <target> <path>
    • Will remove nbt data at pathfrom one target Removing player nbt data is not allowed.
  • Data paths look like this: bar[0].”A [crazy name]”.baz.
    • barmeans foo’s child called bar.
    • foo[0]means element 0 of foo.
    • “quoted strings” may be used if a name of a key needs to be escaped.
  • Examples of old commands:
    • /entitydata<target> {} is now /data get entity <target>
    • /blockdata<pos> <nbt> is now /data merge block <pos> <nbt>
  • Examples of new functionalities:
    • /dataget entity @e[type=pig,limit=1] Saddle 2
    • /dataremove block 17 45 34 Items

/datapack

  • A command to control loaded data packs.
  • Has the following subcommands:
    • enable <name>- will enable the specific pack.
    • disable <name>- will disable the specific pack.
    • list [available|enabled]- will list all data packs, or only the available/enabled ones.
  • Data packs are enabled by default, but if you disable it you can re-enable it with these commands:
    • enable <name>- will enable the specific pack, putting it in its default position.
    • enable <name> first- will enable the specific pack, putting it before any other pack (lowest priority)
    • enable <name> last- will enable the specific pack, putting it after any other pack (highest priority)
    • enable <name> before <existing>- will enable the specific pack, putting it before (lower priority) <existing> pack
    • enable <name> after <existing>- will enable the specific pack, putting it after (higher priority) <existing> pack

Changes

General

The “flattening”

  • Numeric block metadata completely phased out in favor of block states.
  • Split, merged, created, deleted, and renamed a lot of blocks, blockstates and items.
    • Blocks and items previously differing because of damage value have gotten their own id, for example white_woolinstead of wool:0
    • Damage has been moved to the tagtag and is only used by tools and armor; maps use a map
    • Files and commands no longer use dataor set_data.
  • Structures do not run an upgrade path for this.
    • To update your structures, load them all in 1.12, then update to 1.13 and save all structures again.

Other

  • Game library updates
    • Upgraded to LWJGL 3
  • Loading or creating a world shows the percentages of the loading stages.
    • Preparing spawn areanow shows as a loading stage.

Blocks

  • The upper limit of the block IDhas dissappeared.
  • Blocks which used to have no bottom texture (like repeaters, comparators, torches, etc.) now have a bottom texture.
  • Flicking a lever on now displays redstone particles.
  • Beds now require a block below it as a support. Previously this was only required when placing the bed and the block could be destroyed afterwards without the bed being destroyed.
  • Chestsand trapped chests can be put directly next to their double variants instead of requiring one block between them.
    • Shift right-clicking a chest or trapped chest next to a chest or trapped chest respectively will not make the two chests or 2 trapped chests combine into a double chest or double trapped chest.
  • Placing pumpkinsand fence gates no longer requires a block below them.

Mobs

Horse

  • The model has been changed to be more consistent with other mobs[3]
  • Some animations like opening its mouth when grazing have been removed from the model as well.

Commands

General

  • Commands and functions are much faster and more efficient.
  • Most commands are now more case-sensitive. Lowercase is preferable wherever possible.
    • For example, this is no longer allowed: /scoreboardObJeCtIvEs …
  • The output signal of a command block used to be its “success count”, but now is its “result”.
  • Statistics are being updated.

Functions

  • Functions are now completely parsed and cached on load.
    • This means if a command is incorrect for any reason, the player will know about it on load.

Specific Commands

/advancement

  • Removed /advancementtest in favor of entity selectors.

/blockdata

  • Removed in favor of /data.

/clear

  • The syntax of /clearhas changed.
    • /clear[<target>] [<item>] [<data>] [<count>] [<nbt>] will become /clear [<target>] [<item>] [<count>]
    • See the item argument type for more details.

/clone

  • The syntax of /clonehas been changed.
    • /clone<begin> <end> <destination> filtered [force|move|normal] [<block>] [<data>] will become /clone <begin> <end> <destination> filtered [<block>] [force|move|normal]
    • /clone<begin> <end> <destination> [replace|masked] [force|move|normal] [<block>] [<data>] will become /clone <begin> <end> <destination> [replace|masked] [force|move|normal]

/defaultgamemode and /gamemode

  • Now only accepts string IDs, not shorthand or numeric.
    • /gamemode2 will become /gamemode adventure
    • /defaultgamemodesp is now /defaultgamemode spectator

/difficulty

  • /difficulty[<value>] now only accepts string IDs, not shorthand or numeric.
    • /difficulty2 is now /difficulty normal
    • /difficultyp is now /difficulty peaceful
  • You can now query for the current difficulty by using /difficultywithout any arguments.

/effect

  • The syntax of /effecthas been split off, to avoid ambiguity.
    • /effect<entity> <effect> is now /effect give <entity> <effect>
    • /effect<entity> clear is now /effect clear <entity> [<effect>]
  • Giving an effect will now fail if it didn’t actually do anything.
    • Some mobs are immune (for example an ender dragon).
    • Stronger existing effects prevent new weaker ones.

/enchant

  • Removed in favor of /modifyitem.

/entitydata

  • Removed in favor of /data.

/execute

  • The syntax of /executehas been split off.
    • Modifier sub-commands can change how the command is run:
      • /executeas <entity> <chained command> executes a command using the entity <entity> (but doesn’t change position).
      • /executeat <entity> <chained command> executes a command using the position of <entity> (but doesn’t change entity).
      • /executeoffset <pos> <chained command> executes a command using the position of <pos>.
      • /executealign <axes> <chained command> executes a command after aligning the current position to the block grid (rounding down), <axes> is any combination of x y and z (for example: x,xz,zyx and yz).
        • Examples:
          • x=-1.8,y=2.3,z=5.9using x will become x=-2,y=2.3,z=5.9
          • x=2.4,y=-1.1,z=3.8using yxz will become x=2,y=-2,z=3
        • Conditional sub-commands can let you prevent the command from running at all:
          • /execute(if|unless) block <pos> <block> <chained command> executes a command if (or unless) <pos>matches <block>.
          • /execute(if|unless) blocks <begin> <end> <destination> (all|masked) <chained command>executes a command if (or unless) the region between <start> and <end> matches <destination>.
          • /execute(if|unless) entity <entity> <chained command> executes a command if (or unless) <entity>exists (returns 1 or more entities).
          • /execute(if|unless) score <target> <targetObjective> (<|<=|=|>=|>) <source> <sourceObjective> <chained command>executes a command if (or unless) <target>’s score relates to <source>’s score based on the chosen criterium.
        • As replacement for /stats, a new sub-command storelets you store the result or success of a command somewhere:
          • resultis the result of a command, which replaces these old stats: AffectedBlocks, AffectedEntities, AffectedItems, QueryResult.
          • successis how many times the command was successful. This is usually 0 or 1, but if the command split up (for example as @a) then it may be more than 1. This replaces SuccessCount.
          • The value will be stored when the full command has finished executing.
          • If a command isn’t successful (successis 0), result will always be set to 0.
          • It will be made clear what the expected result of each command is.
          • /executestore (result|success) score <name> <objective> <chained command>
            • The value is stored into the scoreboard under <name>and <objective>.
            • The objectivemust exist, but unlike with /stats you don’t need to set an initial value for <name>.
          • /executestore (result|success) block <pos> <path> (byte|double|float|int|long|short) <scale> <chained command>
            • The value is stored in the nbt data at pathof the block at pos as a byte, double, float, int, long, or short.
          • /executestore (result|success) entity <target> <path> (byte|double|float|int|long|short) <scale> <chained command>
            • The value is stored in the nbt data at pathof one target entity as a byte, double, float, int, long, or short.
          • Data paths look like this: bar[0].”A [crazy name]”.baz.
            • barmeans foo’s child called bar.
            • foo[0]means element 0 of foo.
            • “quoted strings” may be used if a name of a key needs to be escaped.
          • Examples:
            • /executestore success score @a foo run say hi
            • /executeas @e[type=pig] at @s store success entity @s Saddle byte 1 if entity @p[distance=..5]
          • You can chain all sub-commands together.
            • After every sub-command you need to write another sub-command.
            • When you’re done with chaining sub-commands, runlets you write the actual command to be executed.
              • /is no longer allowed before the command.
            • /executeas somebody at somebody run say hi
          • Example of old commands:
            • /execute@e ~ ~ ~ detect ~ ~ ~ stone 0 say Stone! is now /execute as @e at @s if block ~ ~ ~ stone run say Stone!
            • /execute@e ~ ~ ~ detect ~ ~ ~ grass 0 summon pig is now /execute at @e if block ~ ~ ~ grass run summon pig
            • /execute@e ~ ~ ~ say Hello! is now /execute as @e run say Hello!

/experience

  • /xpis now an alias for /experience.
  • Split up into 3 different subcommands:
    • /experienceadd <players> <amount> [points|levels]
      • Adds <amount>of either points or levels to the target <players> (defaults to points).
      • Adding points can cause players to level up, as usual.
      • Negative numbers are supported, to subtract points instead.
      • Subtracting points can cause players to level down.
    • /experienceset <players> <amount> [points|levels]
      • Sets <amount>of either points or levels on the target <players> (defaults to points).
      • You cannot set more points than their current level allows.
      • When changing levels, the points will stay at the same percentage as the previous level.
    • /experiencequery <player> (points|levels)
      • Returns either the number of points or levels on the given <player>.

/fill

  • The syntax of /fillhas been changed.
    • /fill<begin> <end> <block> <data> replace [<replaceBlock>] [<replaceData>] is now /fill <begin> <end> <block> replace [<filter>]
    • /fill<begin> <end> <block> [<data>] [destroy|hollow|keep|outline|replace] [<nbt>] is now /fill <begin> <end> <block> [destroy|hollow|keep|outline|replace]

/function

  • /functionno longer accepts [if|unless] <entity>
    • This has been moved into /execute.
    • /functionfoo if @e is now /execute if entity @e run function foo

/gamerule

  • /gameruleno longer accepts unknown rules (“custom gamerules”).
    • You can use functionsor scoreboards as replacements, with no loss of functionality.
    • Existing custom gamerules will just not be accessible. Only built-in rules will be available.
  • Values to /gameruleare now type checked (giving a string if it wants an int is a very obvious error).

/give

  • The syntax of /givehas changed.
    • /give<players> <item> [<count>] [<data>] [<nbt>] is now /give <players> <item> [<count>]
    • See the item argument type for more details.

/kill

  • A targetis now mandatory

/locate

  • The y-coordinate is now returned as 64instead of ?.
  • The resultof the command, used by /execute store, will be the absolute distance to the structure.

/particle

  • The <params>argument has been removed, instead the parameters for particles like block can be specified right after the <name> argument using the new block argument.
    • /particleblock polished_granite ~ ~ ~ 0 0 0 0 1
  • Particle names have been changed.

/playsound

  • Will Tab ↹auto-complete custom sound events.

/replaceitem

  • The syntax of /replaceitemhas changed.
    • /replaceitemblock <pos> <slot> <item> [<count>] [<data>] [<nbt>] is now /replaceitem block <pos> <slot> <item> [<count>]
    • /replaceitementity <target> <slot> <item> [<count>] [<data>] [<nbt>] is now /replaceitem entity <target> <slot> <item> [<count>]
    • See the item argument type for more details.
  • The slotargument no longer requires .
    • For example, hotbar.1now is hotbar.1

/scoreboard

  • /scoreboardhad [<dataTag>] removed from its commands in favor of the nbt argument in entity selectors.
  • /scoreboardplayers tag and /scoreboard teams Replaced by /tag and /team respectively.
  • /scoreboardplayers test removed in favor of /execute (if|unless) score, entity selectors and /scoreboard players get <target> <objective>.

/setblock

  • The syntax of /setblockhas changed.
    • /setblock<pos> <block> [<data>] [<mode>] [<nbt>] is now /setblock <pos> <block> [<mode>]
    • See the block argument type for more details.

/stats

  • Now part of /execute.
  • The new /executeone isn’t a direct replacement, the behavior has changed:
    • It’s now per-command, instead of per-entity or per-block.
    • There’s only resultand success, which covers all the old stat types.

/stopsound

  • *can now be used instead of source to stop all sounds with a certain name, across all sources.

/tag

  • Replaces /scoreboardplayers tag.
  • Keeps the same syntax.
    • /tag<players> add <tag> to add <tag> to <players>.
    • /tag<players> remove <tag> to remove <tag> from <players>.
    • /tag<players> list to list all tags on players.

/team

  • Replaces /scoreboardteams.
  • Keeps the same syntax.
    • /teamadd <team> [<displayname>]
    • /teamempty <team>
    • /teamjoin <team> [<members>]
    • /teamleave [<members>]
    • /teamlist [<team>]
    • /teamoption <team> <option> <value>

/testfor/testforblock and /testforblocks

  • Now part of /execute.

/toggledownfall

  • It was always used to stop the rain, then make you frustrated in a minute when it’s raining again.
  • Use /weather.

/tp and /teleport

  • /tpis now an alias of /teleport (much like /w, /msg and /tell).
  • Coordinates are now relative to the executor, as with all other commands.
  • The syntax of /tpremains, but with the behavior of /teleport.

/trigger

  • /trigger<objective> is a new syntax as a shortcut for /trigger <objective> add 1.

/weather

  • If you don’t specify a time, it now defaults to 5 minutes (previously random).

Argument Types

Target selectors

  • More error handling has been introduced.
  • Arguments may now be quoted.
    • Things like limit=0, level=-10, gamemode=purpleare not allowed.
  • There’s no longer a “min” and “max” separate values, we instead support ranges.
    • level=10is level 10
    • level=10..12is level 10, 11 or 12
    • level=5..is anything level 5 or above
    • level=..15is anything level 15 or below
  • The arcane shorthand names have been renamed.
    • m-> gamemode
    • lor lm -> level
    • ror rm -> distance
    • rxor rxm -> x_rotation
    • ryor rym -> y_rotation
    • c-> limit
  • x, y, z, distance, x_rotation, y_rotationare now doubles and allow values like 34
    • xand z are no longer center-corrected.
      • This means x=0no longer equates to x=0.5.
    • gamemode(previously m) no longer allows numerical or shorthand IDs.
    • limit(was c) No longer allows negative values.
      • Use sort=furthest
    • The nameargument now supports spaces (as long as it’s quoted).
    • Multiple of the same argument in target selectors is now possible.
      • tag=foo,tag=bar,tag=!bazmatches someone with foo, bar and not baz.
      • type=!cow,type=!chickenmatches something that isn’t a cow and isn’t a chicken.
      • type=cow,type=chickenisn’t allowed, because something cannot both be a cow and chicken.
    • You can specify the sorting.
      • sort=nearestis the old default, sorting by distance (default for @p)
      • sort=furthestis the reverse of that (previously you’d use c=-5 for this)
      • sort=randomfor random sorting (default for @r)
      • sort=arbitraryis a new option to not sort the result (default for @e, @a)
    • Specifying scores now looks like scores={foo=1,bar=1..5}
    • You can test for advancements with advancements={foo=true,bar=false,custom:something={criterion=true}}
      • truefor “they completed the advancement”, false for “they have not completed the advancement”
      • Alternatively, pass a block of specific criteria to test for (again, true/false)

Blocks

  • Wherever a <block>, optionally [<data>]and optionally [<nbt>] was required, it’s now a single <block> argument that looks like this:
    • stone
    • minecraft:redstone_wire[power=15,north=up,south=side]
    • minecraft:jukebox{RecordItem:{…}}
    • minecraft:furnace[facing=north]{BurnTime:200}
  • ID is required (though just as before, if namespace isn’t set it defaults to minecraft:).
  • States are inside [], comma-separated and must be properties/values supported by the blocks. They are optional.
    • minecraft:stone[doesntexist=purpleberry]is a syntax error, because stone doesn’t have doesntexist.
    • minecraft:redstone_wire[power=tuesday]is a syntax error, because redstone_wire’s power is a number between 0 and 15.
  • NBT tag is inside {}, and works just like you’d expect. It’s optional.
  • In the context of “conditions”/testing for blocks, only the states you provided will be tested.
    • If you test redstone_wire[power=15], it only checks power but ignores other states such as north.
  • In the context of setting blocks, any states you provided will be set but anything missed out will default depending on the block.
    • If you set redstone_wire[power=15], it will set powerto 15 but north will be a default value (in this case, set to none).
  • There is no such thing as block data value in 1.13. It’s either a different blocks, or a state.

Items

  • Wherever an <item>, optionally [<data>]and optionally [<nbt>] was required, it’s now a single <item> argument that looks like this:
    • stone
    • minecraft:stick{display:{Name:”Stick of Untruths”}}
  • ID is required (though just as before, if namespace isn’t set it defaults to minecraft:).
  • NBT tag is inside {}, and works just like you’d expect. It’s optional.
  • There is no such thing as item data value or item damage value in 1.13.
    • Damage, where applicable, is being moved into nbt.
    • Any other information is either a separate item or a property in nbt.

Other

Options

  • Removed 3D Anaglyph completely

Controls

  • The name of keybindings now describes the actual key (e.g. ‘LBUTTON’ -> ‘Left Button’, ‘BACKSLASH’ -> ‘\’)

Resource packs

  • The default resource pack can now be moved up and down on the resource pack selection screen.

Planned additions

Commands

/modifyitem

  • Replaces /enchant.
  • Syntax not set in stone yet

Planned changes

General

Crafting

  • Customizable crafting recipes
    • Originally planned to be added in 12.

Unconfirmed features

These features are not confirmed for 1.13, but they were mentioned or showcased by developers during development. Main article: Mentioned features

  • The ability to change biome dependent colors(such as foliage, water, and the sky) without needing mods.
  • The new ^notation to use coordinates based on the rotations of entities.
  • Ability for the recipe book to show smelting recipes.
    • Customizable furnace recipe files.
  • Suggesting tab-completions will be added at command input.
  • Recipe book design might be changed.
  • /save-all, /save-onand /save-off will be replaced by /save, /save enable and /save disable.
  • /ban, /ban-ip, /pardonand /pardon-ip will be replaced by other commands.

 

Popular search:

Facebook Comments