Back to mods
ZZCompat.jar project artwork

CurseForge · Hytale mod

ZZCompat.jar

ZZCompat is the ecosystem bridge between ZZCore and external permission providers. It centralizes external groups, nodes, and known players inside a dedicated ZZ ecosystem UI.

Choose a version Pick your version below, then grab the matching file.

Quick answer

Which ZZCompat.jar release should I use?

Updated 2 months ago
beta file ZZCompat.jar
Game version 0.5
Mod system Built-in Hytale mod system

ZZCompat.jar targets 0.5. Do not install it as a separate client mod. Enable it on the world host—the local server in singleplayer or the dedicated server in multiplayer. No required dependencies listed for this file.

Where it goes

Where should ZZCompat.jar be installed in Hytale?

Do not install it as a separate client mod. Enable it on the world host—the local server in singleplayer or the dedicated server in multiplayer.

Separate client mod Not supported
World host / dedicated server Required
Mod system for this release Built-in Hytale mod system
Required install it here Optional supported, not mandatory Not supported do not install here Source doesn’t say do not assume

Put Hytale mods on the world host or dedicated server. Singleplayer runs a local server too; Hytale does not use separate client mods.

What else does ZZCompat.jar need?

ZZCompat.jar. Change the file and its required mods may change too.

No required dependencies listed for this file

This file does not list any required mods. Do not add a library just because a different file uses it.

This file does not list any required or optional project dependencies. Check the creator notes before changing an existing world.

Before you install it

Add ZZCompat.jar without breaking your instance.

Built for ZZCompat.jar. Pick another file and the loader, install side or required mods may change.

  1. 01

    Stick to this file

    Use ZZCompat.jar. It targets 0.5; another release may target a different game build or dependency set.

  2. 02

    Bring the mods it needs

    This file does not list any required mods. Do not add a library just because a different file uses it.

  3. 03

    Enable it on the world host

    Do not install it as a separate client mod. Enable it on the world host—the local server in singleplayer or the dedicated server in multiplayer.

  4. 04

    Pick the file you checked

    Use the “Get this file” button beside ZZCompat.jar. It opens that exact file at the source.

About this project

What does ZZCompat.jar add?

ZZCompat

ZZCompat is the ecosystem bridge between ZZCore and external permission providers. It centralizes external groups, nodes, and known players inside a dedicated ZZ ecosystem UI.

What ZZCompat Does

  • Binds an external permissions provider on top of ZZCore, with LuckPerms as the main target.
  • Synchronizes external groups, namespaces, and catalogs detected in loaded plugins and jars.
  • Exposes a visual dashboard for groups, players, sections, permissions, and audit information.
  • Caches groups, permissions, and known-player data with configurable refresh behavior.
  • Lets staff enable or disable nodes and group membership from the UI.

Commands And Workflow

  • /permissionsbridge is the detected command surface for the module.
  • In practice, the main flow is UI-first from the ZZCore hub.
  • Reloading the module rebinds the provider, rescans namespaces, and clears caches.

Runtime Files And Data

  • config.json stores the active provider, cache behavior, refresh interval, and persisted external catalogs.
  • externalCatalogs lives inside config.json and is filled with discovered namespaces and prefixes.
  • Group, permission, and known-player caches are runtime-managed.

Visible Config Example

This is the kind of config.json file you will see when the module generates its settings:

{
  "version": 1,
  "provider": "auto",
  "cache": true,
  "refreshIntervalSeconds": 30,
  "externalCatalogs": []
}

The section below explains what each line changes in normal language.

Configuration Reference

Main Settings In config.json

  • version (number): internal config schema version.
  • provider (text): active provider mode. The current code accepts auto, luckperms, or none.
  • cache (true/false): enables runtime caching for groups, permissions, and player lookups.
  • refreshIntervalSeconds (number): refresh interval used by the bridge cache.
  • externalCatalogs (list of entries): persisted external namespace catalogs discovered or curated by the bridge.

External Catalog Entry Shape

  • id (text): stable catalog id.
  • name (text): display name for that external catalog.
  • prefixes (list): permission prefixes associated with the catalog.
  • permissions (list): explicit permission nodes associated with the catalog.

Permissions

  • permissionsbridge.use
  • permissionsbridge.admin

Installation

  1. Copy ZZCore.jar into the server mods folder first.
  2. Copy ZZPermissionsBridge.jar into the same server mods folder after that.
  3. If you want an external provider, make sure that provider is also installed and loaded, for example LuckPerms.
  4. Start Hytale.
  5. Open the ecosystem hub and verify that the provider binds correctly.

License

All Rights Reserved.

Redistribution, reposting, resale edits, or reuploading forks is not allowed without written permission from the author.

Project description from CurseForge.

Pick your setup

ZZCompat.jar releases for each Hytale build.

Choose the version and loader you play, then open the matching release.

1 available setups

Check the dependencies, then try the file in a copied instance before changing a world you care about.

Recent files

ZZCompat.jar releases and Hytale builds

3 of 3 releases match

Looking for an older file? The official CurseForge project page is in Resources.