
Modrinth · Minecraft mod
DontUseCommand
designed to prevent players from using command events by modifying the configuration file.
Quick answer
Which DontUseCommand release matches 1.21.1 Forge?
DontUseCommand 1.0.1 targets 1.16, 1.16.1, 1.16.2 with Forge. Installation on the client is optional. Installation on the dedicated server is optional. No extra mods listed for this file.
Where it goes
Is DontUseCommand required on the client, server, or both?
Installation on the client is optional. Installation on the dedicated server is optional.
The source marks this as usable on both the client and server.
What else does DontUseCommand 1.0.1 need?
1.0.1 on 1.21.1 Forge. Every mod below is checked against that same setup.
This file does not list any required mods. Do not add a library just because a different file uses it.
This file does not list any required or optional mods.
Before you install it
Add DontUseCommand without breaking your instance.
Built for DontUseCommand 1.0.1 on 1.21.1 Forge. Pick another file and the loader, install side or required mods may change.
- 01
Stick to this file
Use 1.0.1. It targets 1.16, 1.16.1, 1.16.2 with Forge; another release may have different loader, side or dependency requirements.
- 02
Bring the mods it needs
This file does not list any required mods. Do not add a library just because a different file uses it.
- 03
Put it on the correct side
Installation on the client is optional. Installation on the dedicated server is optional.
- 04
Pick the file you checked
Use the “Get this file” button beside 1.0.1. It opens that exact file at the source.
About this project
What does DontUseCommand add?
Introduction
This is a small mod consisting of just three Java files (core events) designed to prevent players from using command events by modifying the configuration file. It is intended for use by integrated pack authors who do not want players to cheat.
Once this mod is installed, disabled commands cannot be used regardless of the player's game mode, and even server OP players cannot use them. However, if installed on a server, disabled commands can still be used through the command console.
Theoretically, it supports versions 1.13.x to 1.21.x. NeoForge is not supported
Usage
After entering the game, a file called "DUC.txt" will be automatically generated in the config folder, as shown in the image below:
Write down the command you want to disable in the file, which can be multiple commands without adding "/". For example:
tp
summon minecraft:zombie
gamemode creative
Tip: Line breaks are sufficient for each instruction, and sub instructions can be added, such as "gamemode creative", which will not disable other sub instructions such as "gamemode survival"
Restart your client or server, or use the/reload command to take effect.
Additional Information
If you have a large server, you can use LuckPerms instead. This mod is not suitable for server use. If you do not want to individually disable commands, you can use the "No Cheat" mod, which allows disabling all commands.
ModPack authors can change the mod's display name to "[Dependency]xxx (Do Not Delete)".
Project description from Modrinth.
Pick your setup
DontUseCommand by Minecraft version and loader
Choose the version and loader you play, then open the matching release.
1.21
1 loader build1.20.6
1 loader build1.20.5
1 loader build1.20.4
1 loader build1.20.3
1 loader build1.20.2
1 loader build1.20.1
1 loader build1.20
1 loader build1.19.4
1 loader build1.19.3
1 loader build1.19.2
1 loader buildShowing the newest 12 of 36 game versions. Older files are in the list below.
Check the dependencies, then try the file in a copied instance before changing a world you care about.
Recent files
DontUseCommand versions and loaders
1.0.1
DUC-V1.01-1.16.x-1.21.x-NoTips.jar
11 Aug 2024
1.0.1
DUC-V1.01-1.13.x-1.20.x-NoReloadAndTips.jar
11 Aug 2024
Looking for an older file? The official Modrinth project page is in Resources.