Minecraft Admin Commands and RCON Guide for Server Owners
Essential Minecraft Java admin commands for player management, world control, and remote server administration through the MANAfuel RCON console.
Open the RCON Console
Navigate to your Minecraft Java server in the MANAfuel dashboard and open the RCON Console tab. The console connects to your server on port 25575 with credentials pre-configured. Type any command and press Enter to execute. The console shows real-time server output including player joins, chat messages, and command results.
Grant Operator Permissions
Operators (ops) can use admin commands in-game. Add an operator with /op PlayerName from the RCON Console. Remove with /deop PlayerName. Operator levels (1 to 4) control what commands are available — level 4 grants full access including /stop and /op. Set the default op level in server.properties with op-permission-level. The ops.json file tracks all operators and their levels.
Manage Players
Kick a player with /kick PlayerName reason — they disconnect but can rejoin. Ban permanently with /ban PlayerName reason — they see the reason when attempting to reconnect. Unban with /pardon PlayerName. For IP-based bans, use /ban-ip address and /pardon-ip address. View all bans with the banned-players.json and banned-ips.json files in the File Manager.
Control the World
Set the time with /time set day (or night, noon, midnight, or a specific tick value). Control weather with /weather clear, /weather rain, or /weather thunder. Toggle game rules with /gamerule — common examples include /gamerule keepInventory true, /gamerule mobGriefing false, and /gamerule doDaylightCycle false. These commands execute instantly and affect all players.
Teleport and Spawn Items
Teleport a player with /tp PlayerName x y z or teleport one player to another with /tp Player1 Player2. Give items with /give PlayerName minecraft:diamond 64. Set spawn point with /setworldspawn x y z. For creative-mode testing, use /gamemode creative PlayerName and switch back with /gamemode survival PlayerName.
Monitor Server Performance
Check tick performance with the /debug command — start profiling with /debug start and stop with /debug stop to generate a performance report. Monitor connected players with /list which shows player count and names. Bob continuously monitors your server performance and surfaces alerts when tick rate drops below 20 TPS. If the server becomes unresponsive, Bob captures the state and offers a diagnostic summary.
