Documentation
1. Configuration (config.yml)
You can customize the plugin behavior and visuals in the config.yml file.

General Settings
prefix: The tag displayed before all plugin messages.
missingPerms: Message shown when a player tries to use a command or feature without permission.
title-color: Hex color used for the GUI title.
action-blocked: Message sent when a player attempts to perform an action that is currently disabled (blocked) by EventManager.
event-broadcast: Broadcast message sent to players when a feature is enabled/disabled.

Supported placeholders:
%player% = admin/staff who toggled the setting
%status% = enabled/disabled status text
%event% = name of the toggled mechanic (example: PvP, Chat, Hunger)

status-enabled: Text used in broadcast messages when a feature gets enabled.

status-disabled: Text used in broadcast messages when a feature gets disabled.

2. Commands & Usage
EventManager uses a main command with two sub-commands:

/eventmanager gui
Opens the EventManager GUI panel where staff can toggle event mechanics.

/eventmanager reload
Reloads the plugin configuration (config.yml) without restarting the server.

3. Event Control Logic (How it works)
EventManager is designed for smooth and fast event hosting by allowing staff to enable/disable key Minecraft mechanics.

Toggle System

• Each GUI item represents a server mechanic (Chat, PvP, Hunger, Damage, Movement, Weather, etc.)
  
  
• Clicking an item toggles the mechanic:
  • ✅ Enabled = Allowed
    
    
  • ❌ Disabled = Blocked

Blocking Actions
If a mechanic is disabled, EventManager will block the related action.

Broadcast System
Whenever a staff member enables/disables a mechanic, EventManager sends an information to the chat (visible for everyone).

4. Permissions Table
eventmanager.gui
Allows opening and using the EventManager GUI (toggling mechanics).

eventmanager.admin
Allows bypass for disabled events.