The authorization system determines which commands players can use on Minecraft servers. A non-OP player cannot use many management commands. On professional servers, instead of giving everyone OPs, controlled permissions are given with permission plugins such as LuckPerms.

When the authorization system is configured incorrectly, players cannot use commands, admin privileges do not work, market or claim commands become inaccessible, or normal players may receive more privileges than necessary.

1. What is OP?

OP, that is, operator authority, is the high administrative authority on the Minecraft server. The OP player can use many commands.

To give OP from console:

op OyuncuAdi

To remove OP:

deop OyuncuAdi

OP list ops.json is kept in the file.

cat ops.json

2. op-permission-level Setting

OP authorization level can be determined in server.properties.

op-permission-level=4

In general terms:

• 1: Low level powers
• 2: Basic management commands
• 3: More management commands
• 4: Highest OP authority

For some commands, OP level is important. If some commands do not work even though it appears OP, this value should be checked.

3. What is LuckPerms?

LuckPerms is one of the most widely used permission management plugins on Minecraft servers. Player groups, permission node values, prefix/suffix and world-based permissions can be managed.

Basic command after LuckPerms is installed:

lp

Example to give group to player:

lp user OyuncuAdi parent set vip

To add permission to the group:

lp group vip permission set essentials.fly true

4. What is Permission Node?

Permission node is a special authority name that represents permission to use a command or feature.

Examples:

• essentials.home - /home command
• essentials.sethome - /sethome command
• worldedit.* - WorldEdit full powers
• luckperms.user.info - LuckPerms user information

Each plugin's permission node list is included in its documentation. If the wrong node is written, the authorization will not work.

5. What to Check If the Player Cannot Use Commands?

• Is the player in the right group?
• Has the correct permission node been given to the group?
• Is permission set to true?
• Could negative permission have been given?
• Is the plugin providing the command active?
• Are there any world-based authority restrictions?
• Has the setting been applied after server restart/reload?

To see the player's authorization check with LuckPerms:

lp user OyuncuAdi info

6. Negative Permission Problem

An authorization in LuckPerms false If it is set to true, it may be blocking even if it comes from another group.

Example:

lp group default permission set essentials.fly false

In this case, the fly command may not work even if the player receives authorization from another group. Negative powers should be used with caution.

7. World Based Authority Problems

On some servers, authorizations may only be valid within a certain world. While the player can use commands in the survival world, they may not be able to use them in the spawn world.

Example of world-based authority:

lp group vip permission set essentials.fly true world=spawn

If the command does not work in only one world, world context checks must be made.

8. Should You Use OP or LuckPerms?

It is not right to manage all permissions with OP on professional servers. OP should be used mostly for founders and technical managers. Player, guide, VIP, moderator and admin privileges should be separated with systems such as LuckPerms.

Recommended structure:

• default: Normal player powers
• VIP: Extra player commands
• moderator: Limited powers such as ban, mute, kick
• admin: Broad management powers
• owner: Full administrative powers

Common Mistakes

• Giving OP to normal players
• Spelling the permission node name incorrectly
• Not realizing that the plugin providing the command is not working due to missing dependency
• Not checking negative permission values
• Forgetting world-based authority restrictions
• Establishing group hierarchy without planning

FAQ

I authorized the player, but the command does not work, why?
It may be caused by wrong permission node, negative permission, world-based restriction or the relevant plugin not working.

Isn't it practical to give OP to everyone?
It seems practical but it is very dangerous. The OP player can cause serious damage to the server.

Is a restart required to change LuckPerms?
Most LuckPerms commands are instantaneous. However, it is better to restart for plugin installation or major configuration changes.

Safety and Operations Recommendations

• Check OP's list regularly.
• Give players only the permissions they need.
• Use wildcard powers carefully.
• Document authority groups.
• Manage moderator and admin rights in separate groups.

This article is specially prepared for PvPServer.