GlymeraChunkLoader - Changelog

v4.0.0 (2026-07-06)

New: Placeable Chunk Loader block (requested by xXTheHumbleXx)

• A physical Chunk Loader block in the style of a small grandfather clock: stone base, bronze housing with a clock face on all four sides, and a status lamp on top.
• Click to toggle: one click activates it — the lamp turns green and the chunk the block stands in stays loaded and ticking, exactly like /cl load. Click again to turn it off — the lamp turns red and the chunk unloads normally.
• Made for server stores: there is intentionally no crafting recipe. Server owners hand the item out via /cl give [player] or sell it through their store/economy plugin (item id: Glymera_Chunk_Loader).
• Owner protection: only the placer (or an OP) can toggle or remove the block. Removing it always returns the item.
• Per-player limit: new config option maxLoadersPerPlayer (default 3, -1 = unlimited, OPs are exempt) caps how many loader blocks each player can place.
• Restart-safe: placed loaders and their on/off states survive server restarts; active chunks are re-pinned automatically on boot.
• Grief-safe bookkeeping: if the block is destroyed by something that bypasses normal breaking (explosions, area tools), the plugin notices, releases the chunk and returns the item to the owner if they're online.
• New OP command /cl blocks lists all placed Chunk Loader blocks with owner and status.
• Accurate hitbox: collision and the aiming outline match the actual clock shape (half a block wide, about 3/4 high) instead of a full block — you can stand right next to it and aiming at it feels precise.

Fixed

• Config saving is now crash-safe (write-to-temp-then-rename).

v2.0.0 (2026-04-21)

Bug Fixes

• Fixed /cl load <radius> not accepting positional argument: The command rejected calls like /cl load 3 with the error "The wrong number of required argument was specified. Expected; 0, actual; 1" and forced users to use the named-arg syntax /cl load --radius=3. This contradicted the documented usage /cl load [radius].
• Fixed /cl test off with the same root cause: Stopping the tick-test clock required /cl test --off=off instead of the documented /cl test off.

Technical Details

• Root cause: Hytale's withOptionalArg(...) produces an OptionalArg that is parsed as a named argument (--name=value) only, not as a positional token. There is no positional-optional arg type in the command API.
• Fix: Split each affected command into two usage variants via addUsageVariant() (same pattern as /poi in GlymeraLocate):
  • LoadCommand stays no-arg (radius = 0, loads just the chunk the player is standing in)
  • New LoadRadiusCommand variant accepts a positional RequiredArg<Integer> radius (0-16)
  • TestCommand stays no-arg (starts the test)
  • New TestOffCommand variant accepts a positional RequiredArg<String> ("off") to stop the test
• Shared load logic extracted to static helper applyLoad(...) to avoid duplication between the two load variants.

v1.0.0 (2026-04-11)

• Initial release
• Force-load chunks that stay active without player presence (survives restarts)
• /cl load [radius], /cl unload, /cl list, /cl status, /cl reload
• /cl test tick-test clock (1 Rock_Stone per 60s into a nearby chest)
• Persistent JSON config at plugins/GlymeraChunkLoader/config.json
• Uses Hytale's native WorldChunk.addKeepLoaded() API with 5-second maintenance task