GlymeraLift

# GlymeraLift - Changelog

## v6.0.0 (2026-11-07) — Multi-floor lifts with a floor menu

- **Two new blocks: Lift Shaft and Lift Door.** Stack the shaft, and put a Lift Door into the column wherever a floor is - as many as you like (up to 20). A door is one item two blocks high: it places its upper half itself (so it needs a free cell above it) and comes back as one door when you break either half. Shaft blocks stay shaft blocks. Press use on any door: with two doors the lift rides straight to the other one, with three or more a small menu opens and you pick the door you want - the door you are at is marked. Doors are counted from the bottom, door 1 is the lowest.

- **No more see-through ride:** the new shaft and door blocks have inner faces, so inside the lift you see the cage and the doors instead of the world behind them. The topmost block of a column is closed at the top.

- **Recipes:** 2 iron bars make 4 Lift Shaft blocks or 2 Lift Doors at the Workbench. Both sit in the creative tab next to the other doors.

- **The classic Lift block keeps working** for everything already built: same block, same behaviour (bottom door up, top door down). It is no longer craftable and no longer in the creative tab - new lifts are built from Shaft + Door.

- **Config** now lives in the plugin's data folder (`mods/Glymera_GlymeraLift/config.json`, an old `plugins/GlymeraLift/config.json` is taken over once) and starts with an `_info` line that explains every key. New key `testCommands` (headless checks only, leave `false`).

- **`/glift`** shows the version and a one-line help.

- Tested on Hytale 0.7.6. **Upgrade:** delete the old jar from `mods/`, drop in the new one, restart. Existing lifts and configs carry over.

## v5.0.0 (2026-11-05) — English chat messages

- **The two messages the lift shows in chat are now in English.** They appear when a column is too short ("The lift needs at least 4 blocks stacked on top of each other (2 per door).") and when you click the shaft instead of a door ("This is the shaft - use a door at either end of the column."). Both had been German since the first release - thanks for the report on Discord.

- Nothing else changes: block ids, recipe, behaviour and code are untouched. No configuration change.

- **Upgrade:** delete the old jar from `mods/`, drop in the new one and keep the plugin's data folder. Restart the server.

## v4.0.0 (2026-10-12) — Hytale 0.7.0 (Update 7)

- **Rebuilt for Hytale 0.7.0 (Update 7 / Chapter 1).** Requires server 0.7.0 or newer; this version does not run on 0.6.x, and the previous version does not run on 0.7.0 (the server removed the old block and chunk API).

- Migrated to the 0.7.0 world API: block reads and writes now go through the chunk store and block sections (`BlockOperations`), chunk ticking through the engine's new marker component, spawn points through the asynchronous spawn provider.

- **Mod icon added** (`icon-256.png` in the jar) so the plugin shows its picture in the world's mod list instead of a question mark.

- **Upgrade:** delete the old jar from `mods/`, drop in the new one and keep the plugin's data folder — configs and saved data carry over unchanged. Restart the server.

## v3.0.0 (2026-09-18) — Door parts hidden from the creative inventory

- **The three internal lift door parts no longer appear in the creative item library** (variant flag). The Lift block itself stays in the library; doors are still built by the plugin.

- Nothing else changes: block ids, recipe and code are untouched.

## v2.0.0 (2026-08-28) — Hytale 0.6.0 (Update 6)

- **Rebuilt for Hytale 0.6.0 (Update 6).** Requires server 0.6.0 or newer; this version does not run on 0.5.x, and older versions of this plugin do not run on 0.6.0.

- Migrated to the 0.6.0 APIs (network protocol hytale/3, new command-permission API, block/chunk/entity API changes). Everything that was open to players before is open to players again.

- **Upgrade:** delete the old jar from `mods/`, drop in the new one and keep the plugin's data folder — configs and saved data carry over unchanged. Restart the server.