HyperPerms

# 🛠️ HyperPerms 2.9.6 — OP recognition hotfix (Hytale 0.5.2)

Quick but important fix: on Hytale **0.5.2**, HyperPerms admins could show up as **"not OP" in‑game** even though their permissions were correct. **2.9.6 fixes it.** If you updated to 2.9.5 and your staff lost OP, grab this now.

> **Download:** <https://github.com/HyperSystems-Development/HyperPerms/releases/tag/2.9.6&gt;

## What was happening

Hytale 0.5.2 decides operator status by **group membership** (it checks if you're in `hytale:Admin`), not by a permission check. HyperPerms routes everything through its own resolver, so admins were never seen in `hytale:Admin` → game reported "not OP."

## The fix

- Anyone whose HyperPerms groups grant the **`*`** node (your `admin`/`owner` ranks) is now reported to Hytale as OP automatically. **Grant `*` → you're OP.**

- Reverted the 2.9.5 "authoritative provider" change that made this worse.

- Your groups, permissions, and resolution behavior are otherwise unchanged.

## 📥 Update

1. Download **HyperPerms-2.9.6.jar** from the release.

2. Replace the old HyperPerms jar in your `mods/` folder.

3. Restart the server. (No config changes — your data carries over.)

**Requirements:** Hytale 0.5.2+ • Java 25

**Full changelog:** <https://github.com/HyperSystems-Development/HyperPerms/compare/2.9.5...2.9.6&gt;

Heads-up for heavily-modded servers: other plugins built for older Hytale builds may still throw errors on 0.5.2 (removed `Player` API methods) — those need updates from their own authors, separate from HyperPerms.