Crates

A crate is a row in the database with an id, a display name, an icon, a list of opening costs, its rewards, a guarantee, an animation and an audience. It is built and edited from /cratesadmin — also /cratesa — and placed on blocks with a wand. There is no file to write a crate in.

The crate list

/cratesadmin opens Crates: one item per crate, sorted by id, with its animation, reward count, the blocks it stands on and its state.

The bottom row holds Create crate, Server history (the latest openings of every crate, see Openings), Keys (see Keys and costs) and, in the corner, Settings.

Settings

Settings opens ExyliaLib's settings screens for this plugin: config.yml, tiers.yml and every animations/<id>.yml, key by key, without editing the files. Back returns to the crate list. It needs exyliacrates.admin (or ExyliaLib's exylialib.config). The same files are also offered in ExyliaLib's browser editor, /exylialib editor ExyliaCrates, and an edit applied from there runs the crates step of a reload. See Web editor.

Creating a crate

Create crate asks for an id: lowercase letters, numbers, - and _, up to 64 characters; spaces become underscores. The new crate starts with:

Deleting a crate

Deleting takes the crate off every block it stood on and removes its row. Its keys stay, for other crates to take, and so do players' balances of them and the history.

The overview

A crate's overview shows its state at the top and one button per section underneath. Every change is saved the moment it is made, and every block of the crate is redrawn with it.

General

Rewards

Opening

Placing crates

Presence → Crate wand (or shift + left-click on the crate list) hands you the wand for that crate: a BLAZE_ROD by default (settings.wand-material) carrying the crate's id.

Any block works — a chest, an ender chest, a beacon, a slab. The block itself is not changed: it becomes clickable as a crate and is guarded by ExyliaLib's clickable-block module, which keeps players from breaking it and keeps a chest or barrel from opening its own inventory. When the block is a chest, its lid opens at the start of an opening and closes at the end.

The wand only works for holders of exyliacrates.admin. A wand click on a crate block is always a wand click, never an opening or a preview. One crate can stand on any number of blocks, in any world; each block is stored with the server it is on.

The floating icon

Over every crate block the crate's icon turns slowly and bobs, drawn per player with packets, for players within idle.radius blocks (24 by default). It is redrawn every idle.interval-seconds (8): one pass of the loop.

Presence → Floating icon: right-click shows or hides it; left-click opens a form with:

Its size and outline are server-wide: idle.scale and idle.glow in config.yml. While an opening plays on the block, the icon steps aside for everybody watching it.

idle.effects adds effect lines played at every crate once per pass — particles, sounds — for whoever stands there. Empty by default. Setting idle.interval-seconds to 0 turns the whole loop off, icon included.

The hologram

Above every crate block floats a hologram, by default:

VOTE
▎ Keys » 3
➥ Right click to open

Its lines are hologram-lines in lang/<language>/messages.yml. %crate% is the display name and %keys% the reader's own count of the crate's key — each viewer sees their own number, refreshed every second. It counts key items carried plus the balance, of the first key the crate's cost names; a crate that takes no key reads 0.

Presence → Hologram moves it by X, Y and Z blocks from where hologram.offset-y puts it (1.6 above the block). hologram.enabled: false draws none. While an opening plays on the block, the hologram hides for everybody watching it.