ScriptIrc is built for Bukkit/Spigot
An agent-powered development engine.

Hi! A chat mute plugin is a common request. There are multiple ways to implement it, so let me confirm a few key requirements first to design the best structure for you.

Got it. You chose:

• Player mute (specific players)
• Supports permanent and temporary mutes
• Records a mute reason
• Supports manual unmute, auto unmute, and viewing the mute list
• Uses YAML file storage
• Command prefix: “mute”

Now please confirm the plugin name and version, then we can start development.

Alright—I'll initialize the project with default values. Now I will start creating the mute plugin project.

Now I will set up the commands required by the plugin. Based on the design, we need the following commands:

Now I will set up the permission nodes:

Great—the basic project info is set. Now I will create the full plugin project structure. First, let’s check the current structure:

Now I will start creating the full plugin code. First, I will create the data model class:

Create the data manager class:

Create the event listener:

Create the command executor:

Create the tab completer:

Now create the configuration file:

Create the data file template:

Now we need to update the main class file. Since we created another MuteManager class, we need to rename the original main class:

Delete the original main class file, because we already have the complete MuteManager class:

Now create the README.md file:

Now let’s check whether the project structure is complete:

Nice! Now let’s check whether the plugin.yml file is correct:

We need to update the main class path in plugin.yml. Since we deleted the original Mutemanager.java file, the main class is now MuteManager:

We also need to add the mutemanager.admin permission:

The project is complete! Here’s a quick summary of the mute plugin we created:

Project Summary

We have successfully created a full-featured mute plugin with the following highlights:

Core Features

1. Player mute - Mute specific players
2. Duration support - Permanent and temporary mutes (multiple time units supported)
3. Mute reason - Record the reason for each mute
4. Auto unmute - Automatically unmute when time expires
5. Manual unmute - Admins can unmute at any time

Admin Features

1. Mute list - View all muted players (paginated)
2. Mute info - View mute details for a specific player
3. Config reload - Reload config without restarting
4. Persistence - Store data in YAML files

User Experience

1. Smart tab completion - Auto-complete player names, durations, and reasons
2. Permissions - Complete permission control
3. Message hints - Muted players receive a prompt
4. Broadcasts - Configurable mute/unmute broadcast messages

Technical Implementation

1. Event listeners - Listen to chat and join events
2. Scheduled tasks - Automatically unmute expired mutes
3. Data model - A clear MuteData data model
4. Config management - A complete config.yml setup

File Structure

/src/main/java/io/Sriptirc_wp_1/mutemanager/
├── MuteManager.java      # Main class (lifecycle & data)
├── MuteData.java         # Mute data model
├── MuteListener.java     # Event listener
├── MuteCommand.java      # Command executor
└── MuteTabCompleter.java # Tab completer

/src/main/resources/
├── plugin.yml           # Plugin descriptor
├── config.yml           # Configuration
└── data.yml             # Data template

/README.md               # Usage guide

Ready to Test!

This project is ready to export and compile. You can:

1. Click “Export Project” to get the .sirc file
2. Place it into: plugins/ScriptIrc/scripts/src/
3. Run in server console: /scriptirc compiler MuteManager

After a successful build, the plugin will appear in plugins/ . Restart the server to use it.

Usage Examples

# Mute a player for 30 minutes
/mute Steve 30m Spamming

# Permanent mute
/mute Alex Insulting other players

# View mute list
/mutelist

# Unmute a player
/unmute Steve

# View mute info
/muteinfo Alex

# Reload config
/mutereload

The plugin will generate its config automatically. You can customize messages and broadcast settings as needed.