misode

The purpose of events is to have triggers without needing an advancement for it. This should go hand in hand with the current data driven files. We have been using advancements for a totally different reason than what they were intended for. And that's what we wanted to avoid from 1.13 onwards. A few advantages is they work for all entities, not only for players. They keep triggering, so you don't need to revoke the advancement.

Events are json files put in namespace/data/events Its structure is very similar to the current advancement structure of a criteria.

Event structure

This event would run namespace:foo for every zombie that hurts a player in a plains biome

{
  "event": {

misode

New Loot Table features in 1.14

This gist covers the changes to loot tables introduced in 18w43a, the first 1.14 snapshot. Check out this more in-depth loot table guide.

Last updated: 18w49a

Table of contents

• Loot table types
• Random integers
• Entry types
• New conditions

misode

Loot syntax

/loot can be separated into two major parts, target and source. Those two parts follow each other in the command. In snapshots prior to 18w45a, this command was named /drop

loot <target> <source>

Last updated: 18w45a

Target

The target defines where to drop the items. It has several arguments. The first argument is the target type. It's one of these options: spawn, replace, insert and give.

misode

Orbis 1.13 Technical Details

Orbis works by scanning chunks and performing actions based on certain features of that chunk, like its biome, terrain height and specific blocks in the world. All conditions are based on world generation to make sure everything is seed deterministic.

orbis:main

Every 16 ticks, Orbis does a few things.

• If a player with the gm4_orbis_active tag is in a chunk that has bedrock at y=0, it spawns a marker for that chunk, if there wasn't one already.
• For every player with the gm4_orbis_active tag, it generates the closest chunk that hasn't been generated yet. This calls the orbis:chunk/generate function.
• Kill every chunk that has been generated, but only if all four adjacent chunks have also been generated. This is because chunks use the biome of adjacent chunks to determine the final biome decision.

orbis:chunk/scan

misode

Creating custom items with a datapack and resourcepack

Creating the texture

misode

Generating pseudo random numbers

You need to run some commands once (or on every /reload).

scoreboard objectives add random dummy
execute unless score seed random matches -2147483648.. run scoreboard players set seed random 731031
scoreboard players set mult random 1664525
scoreboard players set incr random 1013904223
scoreboard players set #16 random 16

misode

Calculating the sqrt of a number

This method for calculating the square root uses an iterative algorithm known as the Babylonian method.

You need to run some commands once (or on every /reload).

scoreboard objectives add const dummy
scoreboard players set 2 const 2

scoreboard objectives add sqrt dummy

misode

Preventing Fall Damage

This method is based on PingiPuck's video

You need to run a command once (or on every /reload).

scoreboard objectives add falling minecraft.custom:minecraft.time_since_death 

You need to run these commands for every player every tick

misode

Minecraft Technical Wishlist

• Ability to detect block NBT within loot tables
• Addition of an optional loot table argument in /loot ... mine
• New entry type in loot tables that runs a function
• data resolve to resolve text components in NBT
• Loot table tags. With a new entry type loot_table_tag, similar to tag. It also has expand that acts the same.
• New entry type in loot tables that drops xp. If the loot table is used in a container, the container will store the xp, like it does currently with furnaces.
• New entry type in loot tables that will insert the loot table that you are replacing. For example if you want to add a new drop to a vanilla loot table without copying the vanilla loot table. This allows multiple datapacks to each add their own drops to an existing loot table. https://gist.github.com/misode/728b6251adfcdef5f71e50e51e002059
• Selecting sublists in NBT arrays with nbt paths. This could have the following syntax: Items[2..5]

misode

General Structure

{
  "trigger": string // one of the triggers mentioned below
  "predicate": {
    // trigger-specific properties
  },
  "actions": [
    {
 "action": string // one of "function", "advancement", ...