OrbisGuard | Region Management

[0.7.8] - 2026-02-04

Added

Console command support - All region commands now work from the server console using -w <world> to specify the target world. This brings OrbisGuard in line with WorldGuard's console functionality.

Console-supported commands:

• /rg list -w world - List regions in a world
• /rg info spawn -w world - Show region info
• /rg flag spawn pvp deny -w world - Set flags
• /rg remove spawn -w world - Delete regions
• /rg addmember spawn PlayerName -w world - Add members
• /rg addowner spawn g:admin -w world - Add owners (including groups)
• /rg removemember spawn PlayerName -w world - Remove members
• /rg removeowner spawn g:admin -w world - Remove owners
• /rg setpriority spawn 10 -w world - Set priority
• /rg save, /rg load, /rg reload, /rg status, /rg flags - No -w needed

Subtitle placeholders - The titleSubtitle config option now supports placeholders:

• %region% - Region ID (e.g., spawn, arena, __global__ for wilderness)
• %player% - Player's display name
• %uuid% - Player's UUID
• %world% - World name

Example config: "titleSubtitle": "Entering %region%"

Fixed

Server crash when teleporting between worlds - Fixed IllegalStateException: Invalid entity reference crash in EntityEntryProtectionSystem when players teleport between worlds

Thread-safety crash on /rg save and /rg load - Fixed Assert not in thread crash when running save/load commands. Commands were using CompletableFuture.runAsync() which dispatches to ForkJoinPool instead of the main server thread. Now executes synchronously on the calling thread.

__global__ region not existing for all worlds - The __global__ region is now automatically created and persisted for every world when it loads. Previously, the global region only existed in memory for new worlds and wasn't saved to disk, causing it to be missing after server restarts. Now when a world is added, OrbisGuard initializes and saves the global region immediately.

entity-entry flag removing decorative entities - The entity-entry=deny flag no longer removes decorative/display entities. Previously it would remove NPC models, item models, and holograms. Now it skips:

• Intangible entities (holograms, display entities)
• Invulnerable entities (protected decorations)
• Pure model displays (ModelComponent without NPCEntity - item models, NPC model decorations)

Only actual NPCs/mobs with AI behavior are now affected by entity-entry protection.

Excessive permission checks on player movement - Entry/exit protection was checking permissions and fetching player groups on every block movement, even when players weren't crossing region boundaries. This caused excessive LuckPerms/Hytale permission lookups with many players online. Now follows WorldGuard's approach:

• Entry/exit checks only run when crossing region boundaries (entering or exiting a region)
• Player groups are fetched lazily - only when actually needed for membership checks
• Protection hooks are only checked when hooks are registered and player enters a region
• Players walking within the same region or in wilderness trigger zero permission lookups

Commands crashing from in-game chat - Fixed IllegalStateException: Assert not in thread! crash when running commands like /rg info from in-game chat. The issue was that store.getComponent() requires the world thread, but Hytale dispatches all commands to ForkJoinPool. Now uses Universe.get().getPlayerByUsername() and playerRef.getWorldUuid() for thread-safe player/world resolution.

WiFlowPlaceholderAPI not detected - Fixed integration detection failing even when WiFlowPlaceholderAPI was installed. The issue was twofold:

• Used wrong classloader - now uses PluginManager.get().getBridgeClassLoader() to access classes from other plugins (Hytale plugins are isolated)
• Checked too early - detection now deferred to 3 seconds after startup when all plugins are loaded

Mixin integration not detected - Fixed status showing mixins as "not installed" even when OrbisGuard-Mixins was loaded by Hyxin. Early plugins with Hyxin don't run as full JavaPlugins, so the system property was never set. Now detects by checking if orbisguard-mixins*.jar exists in the earlyplugins/ directory.

Changed

Internal performance optimizations