ClipsEZRTP

📜 ClipsEZRTP – Changelog

This changelog documents changes made after 1.0.0, focusing on bug fixes, cleanup, and improvements added during testing and stabilization.

[Stable Update]

🔧 Fixed

• Fixed a critical startup crash when WorldGuard was not installed
  • Resolved NoClassDefFoundError caused by direct WorldGuard class loading
  • WorldGuard is now a true optional dependency
• Fixed incorrect WorldGuard API usage that caused compile-time and runtime errors
• Fixed the ability to stack multiple RTP warmups by spamming /rtp
• Fixed several internal warnings caused by unused variables and redundant logic
• Improved error handling so RTP fails gracefully instead of crashing

🧹 Cleaned Up

• Removed unused startLocation data from pending RTP logic
• Simplified movement-cancel and warmup handling
• Improved null-safety and internal flow for better maintainability

➕ Added

• Optional WorldGuard integration
  • Custom configurable StateFlag (default: clipsezrtp)
  • Ability to block RTP destinations inside specific regions
  • Fully optional and safe if WorldGuard is not installed
• Optional combat-tag blocking
  • Generic support via reflection (no hard dependency)
  • Supports common combat plugins, Bukkit metadata keys, and scoreboard tags
• New bypass permissions:
  • clips.rtp.bypass.cooldown
  • clips.rtp.bypass.cost
  • clips.rtp.bypass.combat
  • clips.rtp.bypass.worldguard
• Improved and expanded config.yml with:
  • Clear explanations for all settings
  • New sections for WorldGuard and combat-tag support

⚠️ Config Changes (IMPORTANT)

The config.yml file has changed in this update.

New configuration options were added, and existing options were reorganized and documented. If you continue using an old config, new features may not work correctly.

✅ How to get the new config.yml

Choose one of the following methods:

Option 1 (Recommended – clean install)

1. Stop the server
2. Delete plugins/ClipsEZRTP/config.yml
3. Start the server again
   → A fresh, updated config.yml will be generated automatically

Option 2 (Manual merge)

1. Start the server once to generate a new config.yml
2. Compare the new file with your old config
3. Copy your custom values (radius, cost, messages, etc.) into the new config
4. Restart the server

💡 Tip: Always keep a backup of your old config before deleting it.

⚙️ Improved

• Improved compatibility with Paper 1.21+
• Improved Java 17 compliance and stability
• Improved RTP safety checks (blocks, biomes, regions)
• Improved internal structure for future updates

✅ Result

• Plugin now loads correctly with or without WorldGuard
• No startup crashes
• No functional regressions from the original version
• Safer for public distribution and long-term maintenance