TabEvent

A plugin for Paper/Purpur that stores a single current "event message" and serves it via the PlaceholderAPI placeholder %tabevent_message%. This allows you to display event announcements in TAB (e.g., in the header or footer) without reloading TAB or manually editing configuration files.

Requirements

• Paper/Purpur 1.21+
• Java 21
• PlaceholderAPI
• TAB (to display the placeholder itself)

Building

The project is built using Maven. Since there is no internet access to Maven Central / PaperMC / ExtendedClip repositories in this environment, the jar could not be built here — build it locally (or in your CI pipeline) where internet access is available:

mvn clean package

After building, the compiled jar will appear in target/TabEvent.jar.

Place it into your server's plugins/ directory and restart the server (or use a plugin manager for hot-reloading if available).

Commands

All commands require the tabevent.admin permission (granted to server operators by default).

| Command | Description |
| --- | --- |
| /tabevent set <message> | Set the current message (supports MiniMessage tags) |
| /tabevent clear | Reset the message to the default-message value from the config (or an empty string) |
| /tabevent get | Display the current message |
| /tabevent reload | Reload config.yml from disk |
| /tabevent lang <ru|en> | Change the plugin language on the fly |

Examples:

/tabevent set <red>⚔ PvP starts in 10 minutes!
/tabevent set <gradient:red:gold>⚔ PvP in 10 minutes!
/tabevent clear
/tabevent get
/tabevent reload
/tabevent lang en

Permissions

• tabevent.admin — Access to all plugin commands (default: op).
• tabevent.bypasscooldown — Bypass the cooldown on set/clear commands (default: op).

Configuration

File location: plugins/TabEvent/config.yml

message: "<gray>No events today."
default-message: ""
cooldown-seconds: 5
language: ru

• message — The current active message (updated automatically when using /tabevent set and /tabevent clear, saved to disk, and restored after server restarts).
• default-message — The message restored when executing /tabevent clear.
• cooldown-seconds — Cooldown period (in seconds) between message modifications (set/clear) for a single player. Set to 0 to disable. Cooldowns do not apply to the console, and players with the tabevent.bypasscooldown permission will bypass it.
• language — The plugin UI language: ru or en.

Multi-Language Support

Command messages (error messages, confirmations, etc.) are located in separate files:

plugins/TabEvent/lang/messages_ru.yml
plugins/TabEvent/lang/messages_en.yml

These files are generated automatically on the first startup using internal templates. You can edit them freely (including adding MiniMessage formatting tags) — changes will take effect after executing /tabevent reload or restarting the server.

You can switch the interface language in two ways:

1. Dynamic command: /tabevent lang en (immediately updates language in config.yml and applies the change without a restart).
2. Manual edit: Change language: ru to language: en in config.yml and execute /tabevent reload.

The %tabevent_message% placeholder is independent of the configured UI language — it always returns the raw string set via /tabevent set, regardless of the selected interface language.

Logging

Every modification (set, clear, reload) is logged to plugins/TabEvent/tabevent.log using the following format:

[2026-07-23 21:45:12] Steve: /tabevent set <red>⚔ PvP starts in 10 minutes!
[2026-07-23 21:50:03] Steve: /tabevent clear
[2026-07-23 22:01:44] CONSOLE: /tabevent reload

This log file is created automatically on startup and is updated in append mode, preserving history across server restarts.

Placeholder

%tabevent_message%

Returns the current stored message as-is, including MiniMessage tags (e.g., <red>⚔ PvP starts in 10 minutes!). Tag parsing into actual color and formatting is handled directly by TAB (which natively supports MiniMessage), preventing TabEvent from stripping any formatting tags.

Usage Example in TAB

header-footer:
  header:
    - ""
    - "%tabevent_message%"
    - ""

After executing /tabevent set ..., the header/footer in TAB will update automatically on the next PlaceholderAPI update tick (without requiring a /tab reload).