NoMHPlugins

Automatically disables Minehut's bundled plugins — like MinehutCosmetics and MinehutFilter — the moment your server starts, with no panel access, no config editing on their end, and no restarts required to manage it.

Minehut installs a handful of its own plugins on every server by default, and there's often no reliable in-game toggle for them (and the panel toggle can be finicky or grayed out depending on your server's state). NoMHPlugins solves this the clean way: it calls Bukkit's own PluginManager#disablePlugin() — the exact same method the server itself uses when a plugin is unloaded normally. No reflection tricks, no event-cancelling hacks, no editing other plugins' files. It just tells the server "this plugin is off," the same way the server would do it itself.

Features

• Disables plugins automatically on startup — no need to run a command every time your server restarts.
• Fully configurable target list — defaults to MinehutCosmetics and MinehutFilter, but you can add or remove any plugin by name.
• Runs after everything else has loaded — waits exactly one tick after startup, guaranteeing every other plugin (including the ones you're targeting) has already finished initializing before it acts.
• Live management, no restart needed — add new targets, re-run the disable pass, or check what's currently loaded, all from in-game or console.
• Safe by design — if a targeted plugin isn't installed or its name doesn't match, it's simply skipped and logged. Nothing else on your server is touched.

Commands

Permission: nomhplugins.admin (defaults to op).

Installation

1. Drop NoMHPlugins.jar into your /plugins folder.
2. Restart your server (a /reload isn't enough — a full restart guarantees the correct plugin load order).
3. Check your console log for confirmation lines like Disabled 'MinehutCosmetics'.

Configuration

The target list lives in config.yml and defaults to:

target-plugins:
  - MinehutCosmetics
  - MinehutFilter

Edit it directly and restart, or just use /nomh disable <name> to add a plugin on the fly — no restart needed for that.

Notes

• Plugin names are case-sensitive and must match exactly what Bukkit reports. Use /nomh list instead of guessing.
• This disables the target plugin in memory for that server session — it doesn't delete or modify its files. If your host re-enables it on a future restart, NoMHPlugins will just quietly disable it again automatically every time it starts.