Simon Ledoux simon511000

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

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.

Type-Safe React Context

By using ReturnType we don't have to manually write type for Context

See also gist for SolidJS https://gist.github.com/JLarky/a46055f673a2cb021db1a34449e3be07

And original tweet https://twitter.com/JLarky/status/1554152932425117697

Introduction

This is a guide to deploying Nextcloud behind a Caddy reverse proxy, both running in Docker containers (an official Nextcloud one and a caddy-docker-proxy one), with the goal of implementing as much as possible via docker-compose files. This is much more difficult than it should be, for a variety of reasons:

As with Docker versions of software in general, documentation of the software does not always apply to the Docker versions, and the Docker documentation does not always include the Docker equivalent ways of doing things.
Docker images do not always expose the desired configuration knobs of the underlying software.
Nextcloud requires special configuration to run correctly behind a reverse proxy (and again, some of the instructions for this configuration requires modification for

Native wayland support is now working consistently for me in VSCode, giving much better text rendering. Unfortunately, it's still hidden behind some command-line flags.

By adding some files to /usr/local/*, you can ensure that VSCode always launches with these flags.

Adding launch flags to VSCode

Assuming that the VSCode launcher is /usr/bin/code-oss (as is the case in Arch):

Create /usr/local/bin/code-oss with the following content:

Autorestic Discord Backup Report

Replace your webhook in the WEBHOOK_URL variable.
Optionally set MENTION_ON_FAIL to True and set DISCORD_USER_ID if you wish to be @mentioned when a job fails.
Add the script to the success & failure hooks in Autorestic, like so:

locations:
  my-location:
 from: /data

	{
	"type": "minecraft:block",
	"pools": [
	{
	"rolls": 1,
	"entries": [
	{
	"type": "minecraft:alternatives",
	"children": [
	{

	# this file contains keys needed for decryption of file system data (WUD/WUX)
	# 1 key per line, any text after a '#' character is considered a comment
	# the emulator will automatically pick the right key
	541b9889519b27d363cd21604b97c67a # example key (can be deleted)

	d7b00402659ba2abd2cb0db27fa2b656 # Common
	805e6285cd487de0faffaa65a6985e17 # Espresso Ancast
	b5d8ab06ed7f6cfc529f2ce1b4ea32fd # Starbuck Ancast

	9a164ee15ac7ceb64d3cc130094095f6 # 007 Legends [EUR, NUS]