Jump to content

OpenMod Commands & Command Permissions


- Alex -

Recommended Posts

  • Community Leader

  • Member ID:  1
  • Group:  Community Leader
  • Followers:  11
  • Topic Count:  211
  • Topics Per Day:  0.06
  • Content Count:  508
  • Content Per Day:  0.15
  • Reputation:   36
  • Achievement Points:  4808
  • Solved Content:  0
  • Days Won:  36
  • Joined:  07/11/17
  • Status:  Online
  • Last Seen:  
  • Device:  Windows

OpenMod Commands & Command Permissions
Finding, Granting & Troubleshooting Command Access
GGU Public Technical Knowledge Base

Public Knowledge Base:
This article is written for both GGU administrators and the wider server-hosting community. General instructions are platform-neutral where possible; GGU-specific practices are identified separately.

 

Applies To

  • OpenMod administrators
  • Plugin developers

 

Prerequisites

  • OpenMod installed
  • A command or plugin to inspect

 

What You’ll Accomplish

Understand how OpenMod command access is determined and troubleshoot denied commands.

 

Command Permissions

OpenMod automatically assigns permissions to commands rather than requiring plugin authors to invent a separate general-use permission check for every command. The developer documentation recommends using the command metadata and permission system consistently.

 

Find a Command's Permission

help <command>

Use the command's help output and plugin documentation to determine its base permission and syntax.

 

Child / Additional Permissions

A plugin may register more specific child permissions for sensitive behavior inside a broader command. This allows a command to remain generally usable while particular operations require stronger access.

 

Actor Restrictions

Commands can be limited to appropriate actor types such as players or console. A command that manipulates an in-game player should not assume every possible command actor is a game player.

 

Troubleshooting Permission Denied

  1. Confirm the command name and syntax.
  2. Use help to identify the permission.
  3. Confirm the user has the intended role.
  4. Check role inheritance.
  5. Look for explicit deny rules.
  6. Confirm the plugin is actually loaded.
  7. Test again after correcting the role.

 

Avoid

  • Granting a global wildcard merely to fix one denied command.
  • Creating duplicate roles for individual users.
  • Assuming the display name of a command is its permission string.
  • Editing a plugin binary/source merely to work around a permission configuration issue.

 

GGU Implementation Notes

GGU should document command permission mappings for in-house plugins alongside the plugin's public/admin documentation. Game Team roles should be granted the smallest command set necessary for their responsibilities.

 

Upstream References

 

Golden Gamers United — Public Technical Knowledge Base
General guidance first. GGU implementation details second.

Alex Thunderhunter

Alex — Founder & Systems Architect

Building the community, one server at a time.

Community Leader
Link to comment
Share on other sites


  • Replies 0
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.