Optimized performance and resolved multiple bugs

fixed issues

Fixed Y-level height detection to properly match WorldGuard regions Proper

fixed world settings issues in safezone protection

feat: performance improve, WorldGuard fixes, and combat improvements

feat: major performance improvements

fix: WorldGuard detection and API hook issues

feat: added combat logout punishment & reward commands

fix: item restrictions not applying correctly

fix: language folder generation on first load

chore: added missing messages & improved config handling

🚀 Performance Update & Bug Fixes

• Improved overall plugin performance and efficiency
  Thanks to iiAhmedYT for contributing ❤️

• Fixed several reported bugs

• Corrected duplicate Ender Pearl cooldown message issue

Add:

• Added configuration caching system to improve performance
• Added UXM Claims integration with runtime detection (no compile dependency)
• Added combat claim entry prevention
• Added PvP protection inside claims
• Added owner and trusted combat exceptions in claims
• Added teleport prevention into claims during combat
• Added per-world claim protection settings
• Added intelligent TTL caching for claim lookups
• Added advanced ender pearl glitch protection system
• Added micro-teleport exploit prevention
• Added barrier / bedrock / portal pearl protection
• Added tight-space teleport safety checks
• Added separate ender pearl cooldown system
• Added configurable event priority system
• Added dynamic event handler registration
• Added EventPriorityManager for caching and validating priorities
• Added /celestcombat eventpriority command to view current priorities
• Added Elytra combat restrictions (equip, shift-click, and glide prevention)
• Added automatic Elytra removal when combat starts
• Added CombatAPI method disconnectPlayerSafely(Player player)
• Added /celestcombat safeDisconnect admin command

Fix:

• Fixed performance issues caused by repeated config lookups
• Fixed EssentialsX GUI command bypass
• Fixed Elytra being usable during combat
• Fixed ender pearl block-stuck teleport edge cases
• Fixed potential claim lookup performance issues

Improve:

• Improved plugin compatibility with other plugins using configurable event priorities
• Improved combat and teleport handling stability
• Improved item restriction handling during combat
• Improved combat start handling logic
• Improved overall plugin performance during player movement checks

CelestCombat Update

🛠 Fixes & Improvements

1. Fixed Flying Detection Bug

Players who are knocked back or launched during combat will no longer be incorrectly pulled back to the ground.

The plugin now properly distinguishes between:

• Knockback or combat launch (allowed)
• Intentional flight attempts (blocked)

This prevents false positives during PvP.

2. Removed Language Folder System

The previous multi-file language folder system has been completely removed.

It has been replaced with a simpler and cleaner configuration:

• A single messages.yml file now controls all messages.

This makes editing and managing messages much easier.

3. Fully Configurable Message System

All plugin messages are now highly customizable.

Supported features:

• Chat messages
• Titles
• Subtitles
• Action bars
• Sounds

Additional capabilities:

• Hex color support: &#RRGGBB
• Legacy color codes: &c, &a, etc.
• Placeholders: %player%, %time%, and more
• Per-message enable/disable options

⚡ Summary

This update improves PvP accuracy, simplifies configuration, and provides a powerful new customizable messaging system.

CelestCombat-Pro v1.2.0 — Major Performance Optimization Update

Overview

This update introduces major performance improvements to the WorldGuard safe-zone protection system and fixes issues with combat command blocking.

The focus of this release is reducing CPU usage during player movement and combat interactions, making the plugin significantly more efficient on servers with many players.

Expected performance improvement: up to 90% reduction in CPU usage for safezone barrier detection.

Performance Improvements

WorldGuard Safezone Barrier Optimization

The safezone detection and barrier visualization system has been heavily optimized.

Estimated CPU usage improvement

Before ~1.60% server thread usage

After ~0.15–0.20% server thread usage

These improvements are most noticeable on PvP servers with many players in combat near protected regions.

Reduced Vertical Scanning

Barrier detection previously scanned a large vertical range.

The scan height is now limited to 4 blocks relative to the player.

Benefits:

• Reduces location checks significantly
• Improves safezone border detection performance
• Lowers CPU usage during movement events

Barrier Update Early Exit

Barrier updates now stop immediately if the barrier layout has not changed.

This prevents unnecessary operations such as:

• recalculating barrier locations
• sending redundant block updates
• iterating over barrier collections

Location Object Reuse

Location objects are now reused during scanning instead of creating new instances.

Previously each update could create hundreds of Location objects.

This change removes a major source of memory allocation and reduces garbage collection pressure.

Optimized HashSet Usage

Barrier tracking collections have been optimized to avoid unnecessary HashSet creation.

Collections are now created only when required.

Packed Cache Keys

Safezone caching now uses bit-packed long keys instead of string concatenation.

Previous cache format:

world:x:y:z

New cache format:

long packedLocationKey

Benefits:

• eliminates string allocations
• improves map lookup speed
• significantly reduces memory overhead

Bug Fixes

Combat Command Blocking

Commands defined in the combat blacklist were not always blocked due to case-sensitive comparisons.

Command matching is now fully case-insensitive.

Example commands that are now correctly blocked:

• /tpa
• /TPA
• /Tpa
• /spawn
• /SPAWN

Wildcard patterns continue to function as expected.

Example configuration:

blocked_commands:
  - tpa
  - spawn
  - team*

Technical Improvements

Object Allocation Reduction

The update removes hundreds of unnecessary object allocations during player movement events.

Key improvements include:

• removing Location cloning inside loops
• eliminating string-based cache keys
• optimizing HashSet usage
• reducing safezone scanning volume

Expected Server Impact

Example scenario: 50 players moving in combat near safezones

Before update ~1.60% CPU usage

After update ~0.15–0.20% CPU usage

This results in smoother gameplay and reduced server load during PvP.

Recommendation

This update is strongly recommended for servers running practice PvP, combat-focused gameplay, or large player counts.

Updating will significantly improve movement handling and safezone barrier performance.

fix: remove combat timers on kill and improve combat handling

Combat timers are now cleared for both killer and victim on death Silent removal prevents unnecessary combat messages Handles indirect combat-related deaths correctly fix: add PlaceholderAPI support

Added PlaceholderAPI repository and dependency Implemented 10 combat and cooldown placeholders Registered expansion with proper error handling Added PlaceholderAPI as a soft dependency fix: optimize combat system and clean up code

Optimized combat map cleanup logic Reduced unnecessary iterations and memory usage Removed unused fields and deprecated API usage Simplified combat cause detection

Celest Combat Pro Update

After months, a new update is finally out.

• Fixed an issue where players could use Wind Charge + W to enter the safe zone while in combat

• Fixed safe zone protection so players inside it do not take damage from any explosives (minecarts, TNT, etc.)

Combat and safe zones now work properly. Please report bugs with clear steps or video.