SMP Utilities – Command Wiki

Overview

SMP Utilities is a mod designed to enhance the experience of creating and managing SMP (Survival Multiplayer) servers in Minecraft.

The main purpose of the mod is to restrict and control items, blocks, and even entire mods, while allowing administrators to create whitelists for specific players so they can bypass these restrictions.

---

Admin Items

Absurd Damage Sword

A sword with extremely high damage. It essentially executes /kill on any mob it hits.

Ban Sword

A sword that kicks or bans players when used against them.

• Attack without Mending → kicks the player
• Attack with Mending enchantment → permanently bans the player

Chapolin Colorado's Sledgehammer

A special weapon with zero damage but extreme knockback. Hitting any entity launches them far away without killing them. Has infinite durability and is fire resistant.

Little Poop

A throwable item. No further mechanical effect beyond being thrown.

Realm Coin

A collectible/currency item for server economy or event use.

Mind Wrench

A special weapon with zero damage and infinite durability.

• Left-click (attack) on a mob → applies permanent Slowness 255 (invisibly, no particles/icon), effectively freezing the mob in place.
• Right-click (interact) on a mob → toggles the mob's AI:
  • If AI is currently enabled → disables it and marks the mob with the MindWrenched tag.
  • If AI is currently disabled (previously wrenched) → re-enables it and removes the tag.

Useful for posing or freezing mobs for decoration, events, or screenshots.

Security Block

An unbreakable block intended for admin use.

---

Table of Contents

1. Introduction
2. Main Commands
3. Permission System
4. Restriction Types
5. Detailed Commands (idrestrict, idcontrol, idlock)
6. Whitelist Management
7. Practical Examples
8. Configuration Files
9. Frequently Asked Questions
10. Item Customization (/lore and /rename)
11. /objective
12. Potions & Effects
13. Waystone Suppression

---

Introduction

SMP Utilities provides three main control systems for administrators:

/idrestrict

Blocks the use of items, blocks, or mods.

Players can still keep the item in their inventory, but cannot use it.

---

/idcontrol

Blocks the possession of items or mods.

If a player has the item in their inventory, it will be automatically removed.

---

/idlock

Combines both systems.

Players cannot possess or use the item.

---

All commands require operator (OP) permission or permission level 2.

---

Main Commands

Basic Structure

/command <action> <type> <id>

---

Available Actions

• disable
  Bans an item, block, or mod for all players, except those with a whitelist permission for that item or its mod.

• enable
  Removes an item, block, or mod from the ban list. If the mod of origin is still banned, players without individual permission remain restricted.

• global disable / global enable
  global disable explicitly marks an item as individually banned, overriding mod-level whitelist permissions. global enable adds the item as a global exception — usable by all players even if its mod is banned.

• status
  Checks the status of an item, block, mod, or player.

• list
  Shows all restricted items, blocks, or mods.

• allow
  Adds a player to the whitelist for an item or mod. Whitelisted players can use, hold, equip, and place the item even if it is globally banned or its mod is banned.

• deny
  Removes a player from the whitelist.

• allowlist check
  Checks a player's permissions.

• allowlist clear
  Removes all permissions from a player.

---

Target Types

Commands can target four different types:

• item — Any item in the game. Example: minecraft:diamond
• block — Blocks in the game. Example: minecraft:stone
• mod — An entire mod. Example: thermal
• item-block — Something that is both an item and a block. Example: minecraft:dirt

---

Permission System

Restriction Levels

idrestrict

The player can possess the item, but cannot use it.

---

idcontrol

The player cannot possess the item. It will be automatically removed from the inventory.

---

idlock

The player cannot possess nor use the item.

---

Player Whitelist

You can allow specific players to bypass restrictions.

Examples:

/idrestrict allow player item minecraft:diamond
/idcontrol allow player mod thermal
/idlock allow player all

---

Whitelist Types

There are four types of permissions:

• item — Allows a specific item.
• block — Allows a specific block.
• mod — Allows all items from a mod.
• all — Allows all mods (available in all three systems).

---

Priority Rule

Individual bans always override player whitelist permissions.

If a specific item is banned with disable item or global disable item, no player can use or possess it, even if they have whitelist permission for the entire mod.

Example:

• Mod aether is banned
• Player ddogo is whitelisted for mod aether
• Admin bans aether:some_item individually
• Result: ddogo cannot use aether:some_item despite the mod whitelist

---

Restriction Types

Item Restriction

/idrestrict disable item minecraft:diamond_sword

Players can still possess the sword but cannot use it.

---

Block Restriction

/idcontrol disable block minecraft:tnt

Players cannot keep TNT in their inventory.

---

Mod Restriction

/idlock disable mod thermal

Nobody can use or possess items from that mod.

---

Item-Block Restriction

Used for things that are both items and blocks.

/idlock disable item-block minecraft:dirt

Dirt will be restricted as both an item and a world block.

---

Allowing ALL Mods

Allows a player to ignore all mod restrictions.

/idcontrol allow player all
/idlock allow player all

---

Global Exceptions

When a mod is banned globally, you can allow specific items/blocks even while keeping the mod banned:

/idlock global enable item aether:golden_amber

This adds aether:golden_amber as a global exception — everyone can use it despite the mod being banned.

To remove the exception, ban the item directly:

/idlock global disable item aether:golden_amber

---

/idrestrict

Blocks the use of items, blocks, and mods. Players can still keep the item, but cannot interact with it.

Behavior of disable / global disable / enable / global enable

| Command | Effect |
|---|---|
| /idrestrict disable item <id> | Bans the item for all players except those whitelisted for that item or its mod |
| /idrestrict global disable item <id> | Same as above — explicitly marks the item as individually banned, overriding mod whitelist |
| /idrestrict enable item <id> | Removes the item from the ban list. If the mod is still banned, players without individual permission remain restricted |
| /idrestrict global enable item <id> | Adds the item as a global exception — usable by all players even if its mod is banned |

Usage Examples

/idrestrict disable item minecraft:elytra
/idrestrict disable block minecraft:enchanting_table
/idrestrict disable mod twilightforest
/idrestrict disable item-block minecraft:dirt
/idrestrict global enable item twilightforest:some_item
/idrestrict status item minecraft:diamond
/idrestrict status player PlayerName
/idrestrict list

---

What idrestrict blocks

• Using items
• Eating or drinking
• Placing blocks
• Breaking blocks
• Interacting with blocks
• Attacking entities with the item
• Equipping armor
• Equipping Curios accessories

---

What idrestrict does NOT block

• Having the item in inventory
• Picking the item up from the ground
• Crafting with the item
• Trading the item in interfaces

---

/idcontrol

Blocks the possession of items or mods. Restricted items are automatically removed from the inventory.

Examples

/idcontrol disable item minecraft:diamond
/idcontrol disable mod create
/idcontrol allow player all
/idcontrol deny player all

---

What idcontrol blocks

• Having the item in inventory
• Picking the item up from the ground
• Equipping the item
• Holding the item in any slot

---

Special Behavior

When an item is restricted with idcontrol:

1. The item is removed from the player's inventory
2. It is dropped on the ground with the tag smp_controlled_item
3. Items with this tag cannot be picked up again
4. The check runs every game tick

---

/idlock

Combines idrestrict + idcontrol. This is the most restrictive system. Players cannot use or possess the item.

Examples

/idlock disable item minecraft:diamond_sword
/idlock disable block minecraft:crafting_table
/idlock disable mod mekanism
/idlock allow player all
/idlock global enable item mekanism:some_item
/idlock status item minecraft:diamond
/idlock list

---

What is restricted

• Using items
• Possessing items
• Picking items from the ground
• Equipping items
• Placing blocks
• Breaking blocks
• Interacting with related objects

---

Whitelist Management

Check a player's permissions:

/idrestrict allowlist check PlayerName
/idcontrol allowlist check PlayerName
/idlock allowlist check PlayerName

Check permissions of all online players:

/idrestrict allowlist check
/idcontrol allowlist check
/idlock allowlist check

Remove all permissions:

/idrestrict allowlist clear PlayerName
/idcontrol allowlist clear PlayerName
/idlock allowlist clear PlayerName

---

Practical Examples

Survival Server with Restrictions

/idrestrict disable item minecraft:elytra
/idrestrict disable item minecraft:totem_of_undying

/idcontrol disable block minecraft:tnt
/idcontrol disable block minecraft:bedrock

Whitelist for VIPs:

/idrestrict allow VIP_Player item minecraft:elytra

---

Themed Server (No Magic)

/idlock disable mod ars_nouveau
/idlock disable mod mana-and-artifice

---

Mod Maintenance

Temporarily disable a mod:

/idcontrol disable mod problem_mod

Re-enable later:

/idcontrol enable mod problem_mod

---

Restrict Mod but Allow Specific Items

/idlock global disable mod aether
/idlock global enable item aether:golden_amber
/idlock global enable item aether:zanite_gemstone

Both items will be usable by everyone even though the rest of the mod is banned.

---

Configuration Files

Data is saved inside the world folder under serverconfig/smp_utilities/:

idrestrict

• id_restrict_config.dat — banned items, blocks, mods
• id_restrict_whitelist.dat — per-player whitelists
• id_restrict_exceptions.dat — global exceptions

idcontrol

• id_control_config.dat — disabled items and mods
• id_control_whitelist.dat — per-player whitelists
• id_control_exceptions.dat — global exceptions

idlock

• id_lock_config.dat — locked items, blocks, mods
• id_lock_whitelist.dat — per-player whitelists
• id_lock_exceptions.dat — global exceptions

Waystone Suppression

• waystone_suppression_config.toml — suppressed mod patterns, banned items and blocks

---

Frequently Asked Questions

What is the difference between the commands?

idrestrict — The player can possess the item but cannot use it.

idcontrol — The player cannot possess the item.

idlock — The player cannot possess or use the item.

---

What is the difference between disable and global disable?

Both ban the item for all players who lack whitelist permission. The difference is in priority: global disable explicitly marks the item as individually banned, ensuring it overrides mod-level whitelist permissions. Use global disable when banning a specific item from a mod that is otherwise allowed.

---

What is the difference between enable and global enable?

enable removes the item from the ban list. If its mod is still banned, players without individual permission remain restricted.

global enable adds the item as a global exception — it becomes usable by everyone, regardless of whether the mod is banned.

---

Can I combine the commands?

Yes. All systems are independent. You can use idrestrict for light restrictions, idcontrol for medium restrictions, and idlock for severe restrictions.

---

Can a player whitelist bypass an individual item ban?

No. Individual item/block bans always take priority over mod whitelist permissions. Even if a player has permission for a mod, a specific item banned with disable item cannot be used or held.

---

Does it work with Curios?

Yes. The mod integrates with the Curios API. Restricted items are detected in Curios slots, are automatically removed, and cannot be equipped.

---

/rename and /lore

The mod includes commands to customize items using consumable tickets.

---

/rename

Renames the item the player is holding. Requires a Rename Ticket.

/rename <color> normal <name>
/rename <color> <format> <name>
/rename <color> <format1> <format2> <name>
/rename <color> <format1> <format2> <format3> <name>

Examples:

/rename red normal Fire Sword
/rename gold bold Royal Shield
/rename blue italic Magic Potion
/rename dark_red strikethrough Cursed Item
/rename green bold italic Lucky Amulet

Using this command consumes a Rename Ticket:

---

/lore

Adds a description (lore) to the item the player is holding. Requires a Lore Ticket.

/lore <color> normal <text>
/lore <color> <format> <text>
/lore <color> <format1> <format2> <text>

Examples:

/lore dark_gray normal A very rare item.
/lore gold bold Forged by ancient kings.
/lore blue italic Said to bring luck.
/lore dark_red strikethrough Forbidden item.

Using this command consumes a Lore Ticket:

---

/objective

Displays a persistent message on the action bar of players. Useful for showing objectives, rules, or events during gameplay.

Requires permission level 4 (server operator).

---

Syntax

/objective global <color> <format> <text>
/objective player <player> <color> <format> <text>
/objective clear
/objective clear <player>

---

Examples

/objective global gold bold Defeat the Ender Dragon!
/objective global red normal Do not use Waystones today.

/objective player Steve blue italic Find 5 diamonds.
/objective player Alex green bold italic Complete your quest!

/objective clear
/objective clear Steve

---

Behavior

• The objective is shown on the action bar (above the hotbar).
• It is sent every tick to ensure it stays visible and doesn't fade.
• When a player joins the server, their stored objective is automatically shown.
• Player-specific objectives take priority over the global objective.
• Clearing the global objective does not remove player-specific objectives.

---

Available Colors and Formats

The following color and format options are available for /rename, /lore, and /objective:

Colors:

black, dark_blue, dark_green, dark_aqua, dark_red, dark_purple, gold, gray, dark_gray, blue, green, aqua, red, light_purple, yellow, white

Formats:

normal, bold, italic, underlined, strikethrough

Combinations:

bold italic, bold underlined, bold strikethrough, italic underlined, italic strikethrough, bold italic underlined, bold italic strikethrough

---

Potions & Effects

SMP Utilities adds two custom potion effects.

---

Waystone Suppression

Effect color: Purple (#ae37d5)
Category: Beneficial

While active, the player cannot use or interact with items, blocks, or mods listed in the waystone_suppression_config.toml.

Designed to block teleportation mods (such as Waystones) during specific game moments or events.

Potions available:

• Potion of Waystone Suppression
• Splash Potion of Waystone Suppression
• Lingering Potion of Waystone Suppression
• Arrow of Waystone Suppression

---

Imbalance

Effect color: Dark magenta (#3b4c5b inverted)
Category: Beneficial (but mechanically negative)

Reduces the player's knockback resistance by -(amplifier + 1) per tick. At amplifier 0 (level I), removes 1 point of knockback resistance. At higher levels the reduction scales accordingly.

Designed to make players much more vulnerable to knockback, for use with items like the Chapolin Colorado's Sledgehammer.

Potions available:

• Potion of Imbalance
• Splash Potion of Imbalance
• Lingering Potion of Imbalance
• Arrow of Imbalance

---

Waystone Suppression

The Waystone Suppression system restricts teleportation and movement items/blocks for players under the Waystone Suppression effect.

---

Configuration File

Located at: serverconfig/smp_utilities/waystone_suppression_config.toml

[blacklist]
# disables teleport mods (blocks breaking, use of blocks and items, and/or equipping armor)
WaystoneSuppression = ["waystones:*", "balm:*", "endermanoverhaul:*"]

[banned_items]
# individual item IDs to ban (cannot equip in armor or curios slots; drops if equipped)
BannedItems = ["minecraft:ender_pearl", "minecraft:chorus_fruit", "all_in_one:enchiridion", "relics:chorus_inhibitor", "relics:enders_hand", "relics:spatial_sign"]

[banned_blocks]
# individual block IDs to ban (cannot place, break, or interact with) remove the '#' to enable it; minecraft:tnt is just an example, you can remove it
# BannedBlocks = ["minecraft:tnt"]

---

Pattern Format

• modid:* — bans all items and blocks from that mod
• modid:item_id — bans a specific item or block

---

What it blocks (while effect is active)

• Placing or breaking blocks from banned mods
• Using banned items
• Equipping banned items as armor or in Curios slots (items are dropped)
• Interacting with banned blocks
• Attacking with banned items

---

Default Suppressed Content

By default, the following mods are suppressed:

• waystones:* — all Waystones mod content
• balm:* — all Balm mod content (Waystones dependency)
• endermanoverhaul:* — all Enderman Overhaul mod content

And these individual items are banned:

• minecraft:ender_pearl
• minecraft:chorus_fruit
• all_in_one:enchiridion
• relics:chorus_inhibitor
• relics:enders_hand
• relics:spatial_sign

---

SMP Utilities — Keep your server organized.