GlymeraLantern - Changelog

v2.0.0 (2026-04-26)

Bug Fixes

• Non-OP players could not use /lantern even with opOnly: false: The plugin's internal if (config.opOnly && !isOp(pr)) check inside execute() ran after Hytale's native command-permission gate. Since AbstractCommand.canGeneratePermission() defaults to true, the command system auto-generated a permission node at registration time that no regular player had — non-OPs were rejected with the engine's standard "You do not have permissions to use this command" message before the plugin code ever ran. The config.opOnly flag was effectively dead code for non-OPs.

Fix

• LanternToggleCommand now overrides canGeneratePermission() to return config.opOnly. Hytale's native permission gate is now driven directly from the config:
  • opOnly = false → no permission node generated → every player can use /lantern.
  • opOnly = true → permission node generated → only OPs (who hold the * wildcard) can use /lantern. Non-OPs receive the engine's standard no-permission message.
• Removed the redundant in-execute() check, the isOp() helper, and the PermissionsModule import. The native command gate is now the single source of truth — one mechanism instead of two.

Notes

• Changes to config.json require a server restart to take effect, because canGeneratePermission() is evaluated once at command-registration time during plugin setup().

v1.0.0 (2026-04-03)

• Initial release.
• /lantern toggles a DynamicLight component on the player entity (no blocks, no NPCs).
• Config: plugins/GlymeraLantern/config.json with opOnly flag.