DemocracyCraft Wiki - User contributions [en-gb]

Using LuckPerms Verbose

2025-07-26T06:03:00Z

Nacho:

== '''<big>Introduction</big>''' ==
When working on StateCraft or DemocracyCraft it's important to note with with various levels of plugins and permissions it's useful to have a tool that can help clarify what all is happening to a specific player. The verbose tool can be utilize to narrow down specific permission nodes that may or may not be documents publicly.

Troubleshooting permission issues for players '''or''' exploring which permissions plugins are using, it can be difficult to find accurate information. All custom plugins deployed within the MCN network have formal documentations maintained by network leadership however, a quick fix can be done through the verbose feature of LuckPerms.

Verbose in LuckPerms is designed to help with this by allowing you to track '''permission''' checks in real time, providing valuable insights during '''debugging''' and '''configuration'''. The moments in time when you get stumped trying to figure out ''why'' something is not properly displaying. It's important to remember most issues will be a permissions issue for visibility limitations OR improperly being configured through the plugin directly.

== <big>How does Verbose work</big> ==
{| class="wikitable"
!Command
!<code><nowiki>/lp verbose <on/record|off/upload> [filter]</nowiki></code>
|-
!Option
!Description
|-
|<code>on</code>
|Turns the verbose overlay on, notifies you in chat that it's enabled.
|-
|<code>record</code>
|Same as “on”; however, you will not be notified via chat.
|-
|<code>off</code>
|Just disables the system, and clears any matches from memory.
|-
|<code>upload</code>
|Same as "off", but will upload the results to the web viewer for easier analysis, and provide you with a link.
|}
The first argument enables/disables the system, and the second sets up the filter.

The '''<code>/lp verbose command</code>''' allows you to check the permissions of a specific command in-game without any chat-spam or web viewer. To use it, you simply run '''<code>/lp verbose command <username> <command></code>''' and LuckPerms will run the following steps:

# Will turn on verbose for the user in question, using the filter for that user.
# Will force the user to run the command you specify.
# Will turn verbose off.[[File:Verbose command functionality.png|center|thumb|902x902px|Command Action: <code>/lp verbose command Nacholebraa /gmc</code>]]

This sequence of rapid events will result in the permissions that were checked appearing in chat, without the usual spam. This is especially useful if you need to fine permissions for a command that is not well documented if at all.

This command will sudo<ref>''Running a command through another player using their permissions.''</ref> the user to run the command specified. As a result, there are additional permissions required to use this functionality. You can find these permissions within by running the Verbose commands OR checking out the LuckPerms Permission page.

== <big>Verbose Filters</big> ==
The filter is an expression used to match permission entries, and ignore entries you don't need. It could just be a player name, or much more advanced.

A filter string will match the start of the permission being checked, or the users full name. You can use <code>&</code> (and), <code>|</code> (or), and <code>!</code> (not / negate) to setup expressions. Parenthesis <code>( )</code> are also supported.

'''Some examples'''
* <code>Luck & (essentials | worldedit)</code> - Matches any checks made against "Luck" that start with "essentials" or "worldedit"
* <code>Luck & !anticheat</code> - Matches any checks made against "Luck" that do not start with "anticheat"
* <code>anticheat & !anticheat.check</code> - Matches checks on all users starting with "anticheat" but not starting with "anticheat.check"

[[File:Verbose command filter.png|center|thumb|1105x1105px|Command Action: <code><nowiki>/lp verbose record Nacholebraa & (essentials | worldedit)</nowiki></code>]]

The web viewer allows you to view the '''same''' information visible in-game just in a cleaner view overall. In certain cases it's easier to review various permissions checks through the Web Viewer than in-game. But it's totally optional and up to the individual running the command.

== <big>'''Frequently Asked Questions?'''</big> ==
{{DEFAULTSORT:LuckPerms Verbose}}
[[Category:Staff]]

Using LuckPerms Verbose

2025-07-26T05:54:51Z

Nacho:

Using LuckPerms Verbose

2025-07-26T05:47:29Z

Nacho:

== '''<big>Introduction</big>''' ==
When working on StateCraft or DemocracyCraft it's important to note with with various levels of plugins and permissions it's useful to have a tool that can help clarify what all is happening to a specific player. The verbose tool can be utilize to narrow down specific permission nodes that may or may not be documents publicly.

Whether you're troubleshooting permission issues for players or simply exploring which permissions plugins are checking, it can be difficult to find accurate information. All custom plugins deployed within the MCN network have formal documentations maintained by network leadership however, a quick fix can be done through the verbose feature of LuckPerms.

Verbose in LuckPerms is designed to help with this by allowing you to track '''permission''' checks in real time, providing valuable insights during '''debugging''' and '''configuration'''. The moments in time when you get stumped trying to figure out ''why'' something is not properly displaying. It's important to remember most issues will be a permissions issue for visibility limitations OR improperly being configured through the plugin directly.

== <big>How does Verbose work</big> ==
{| class="wikitable"
!Command
!<code><nowiki>/lp verbose <on/record|off/upload> [filter]</nowiki></code>
|-
!Option
!Description
|-
|<code>on</code>
|Turns the verbose overlay on, notifies you in chat that it's enabled.
|-
|<code>record</code>
|Same as “on”; however, you will not be notified via chat.
|-
|<code>off</code>
|Just disables the system, and clears any matches from memory.
|-
|<code>upload</code>
|Same as "off", but will upload the results to the web viewer for easier analysis, and provide you with a link.
|}
The first argument enables/disables the system, and the second sets up the filter.

The '''<code>/lp verbose command</code>''' allows you to check the permissions of a specific command in-game without any chat-spam or web viewer. To use it, you simply run '''<code>/lp verbose command <username> <command></code>''' and LuckPerms will run the following steps:

# Will turn on verbose for the user in question, using the filter for that user.
# Will force the user to run the command you specify.
# Will turn verbose off.[[File:Verbose command functionality.png|center|thumb|902x902px|Command Action: <code>/lp verbose command Nacholebraa /gmc</code>]]

This sequence of rapid events will result in the permissions that were checked appearing in chat, without the usual spam. This is especially useful if you need to fine permissions for a command that is not well documented if at all.

This command will sudo the user to run the command specified. As a result, there are additional permissions required to use this functionality. You can find these permissions within by running the Verbose commands OR checking out the LuckPerms Permission page.

== <big>Verbose Filters</big> ==
The filter is an expression used to match permission entries, and ignore entries you don't need. It could just be a player name, or much more advanced.

A filter string will match the start of the permission being checked, or the users full name. You can use <code>&</code> (and), <code>|</code> (or), and <code>!</code> (not / negate) to setup expressions. Parenthesis <code>( )</code> are also supported.

===== Some examples =====

* <code>Luck & (essentials | worldedit)</code> - Matches any checks made against "Luck" that start with "essentials" or "worldedit"
* <code>Luck & !anticheat</code> - Matches any checks made against "Luck" that do not start with "anticheat"
* <code>anticheat & !anticheat.check</code> - Matches checks on all users starting with "anticheat" but not starting with "anticheat.check"

[[File:Verbose command filter.png|center|thumb|1105x1105px|Command Action: <code><nowiki>/lp verbose record Nacholebraa & (essentials | worldedit)</nowiki></code>]]

The web viewer allows you to view the '''same''' information visible in-game just in a cleaner view overall. In certain cases it's easier to review various permissions checks through the Web Viewer than in-game. But it's totally optional and up to the individual running the command.
[[Category:Staff]]

Using LuckPerms Verbose

2025-07-26T05:42:51Z

Nacho:

When working on StateCraft or DemocracyCraft it's important to note with with various levels of plugins and permissions it's useful to have a tool that can help clarify what all is happening to a specific player. The verbose tool can be utilize to narrow down specific permission nodes that may or may not be documents publicly.

Whether you're troubleshooting permission issues for players or simply exploring which permissions plugins are checking, it can be difficult to find accurate information.

Verbose in LuckPerms is designed to help with this by allowing you to monitor '''permission''' checks in real time, providing valuable insights during '''debugging''' and '''configuration'''.

== How does Verbose work ==
{| class="wikitable"
!Command
!<code><nowiki>/lp verbose <on/record|off/upload> [filter]</nowiki></code>
|-
!Option
!Description
|-
|<code>on</code>
|Turns the verbose overlay on, notifies you in chat that it's enabled.
|-
|<code>record</code>
|Same as “on”; however, you will not be notified via chat.
|-
|<code>off</code>
|Just disables the system, and clears any matches from memory.
|-
|<code>upload</code>
|Same as "off", but will upload the results to the web viewer for easier analysis, and provide you with a link.
|}
The first argument enables/disables the system, and the second sets up the filter.

The '''<code>/lp verbose command</code>''' allows you to check the permissions of a specific command in-game without any chat-spam or web viewer. To use it, you simply run '''<code>/lp verbose command <username> <command></code>''' and LuckPerms will run the following steps:

# Will turn on verbose for the user in question, using the filter for that user.
# Will force the user to run the command you specify.
# Will turn verbose off.[[File:Verbose command functionality.png|center|thumb|902x902px|Command Action: <code>/lp verbose command Nacholebraa /gmc</code>]]

This sequence of rapid events will result in the permissions that were checked appearing in chat, without the usual spam. This is especially useful if you need to fine permissions for a command that is not well documented if at all.

This command will sudo the user to run the command specified. As a result, there are additional permissions required to use this functionality. You can find these permissions within by running the Verbose commands OR checking out the LuckPerms Permission page.

== Verbose Filters ==
The filter is an expression used to match permission entries, and ignore entries you don't need. It could just be a player name, or much more advanced.

A filter string will match the start of the permission being checked, or the users full name. You can use <code>&</code> (and), <code>|</code> (or), and <code>!</code> (not / negate) to setup expressions. Parenthesis <code>( )</code> are also supported.

===== Some examples =====

* <code>Luck & (essentials | worldedit)</code> - Matches any checks made against "Luck" that start with "essentials" or "worldedit"
* <code>Luck & !anticheat</code> - Matches any checks made against "Luck" that do not start with "anticheat"
* <code>anticheat & !anticheat.check</code> - Matches checks on all users starting with "anticheat" but not starting with "anticheat.check"

[[File:Verbose command filter.png|center|thumb|1105x1105px|Command Action: <code><nowiki>/lp verbose record Nacholebraa & (essentials | worldedit)</nowiki></code>]]

The web viewer allows you to view the '''same''' information visible in-game just in a cleaner view overall. In certain cases it's easier to review various permissions checks through the Web Viewer than in-game. But it's totally optional and up to the individual running the command.
[[Category:Staff]]

Using LuckPerms Verbose

2025-07-26T05:41:27Z

Nacho:

When working on StateCraft or DemocracyCraft it's important to note with with various levels of plugins and permissions it's useful to have a tool that can help clarify what all is happening to a specific player. The verbose tool can be utilize to narrow down specific permission nodes that may or may not be documents publicly.

Whether you're troubleshooting permission issues for players or simply exploring which permissions plugins are checking, it can be difficult to find accurate information.

Verbose in LuckPerms is designed to help with this by allowing you to monitor '''permission''' checks in real time, providing valuable insights during '''debugging''' and '''configuration'''.

== How does Verbose work ==
{| class="wikitable"
!Command
!<code><nowiki>/lp verbose <on/record|off/upload> [filter]</nowiki></code>
|-
!Option
!Description
|-
|<code>on</code>
|Turns the verbose overlay on, notifies you in chat that it's enabled.
|-
|<code>record</code>
|Same as “on”; however, you will not be notified via chat.
|-
|<code>off</code>
|Just disables the system, and clears any matches from memory.
|-
|<code>upload</code>
|Same as "off", but will upload the results to the web viewer for easier analysis, and provide you with a link.
|}
The first argument enables/disables the system, and the second sets up the filter.

The '''<code>/lp verbose command</code>''' allows you to check the permissions of a specific command in-game without any chat-spam or web viewer. To use it, you simply run '''<code>/lp verbose command <username> <command></code>''' and LuckPerms will run the following steps:

# Will turn on verbose for the user in question, using the filter for that user.
# Will force the user to run the command you specify.
# Will turn verbose off.[[File:Verbose command functionality.png|center|thumb|902x902px|Command Action: <code>/lp verbose command Nacholebraa /gmc</code>]]

This sequence of rapid events will result in the permissions that were checked appearing in chat, without the usual spam. This is especially useful if you need to fine permissions for a command that is not well documented if at all.

This command will sudo the user to run the command specified. As a result, there are additional permissions required to use this functionality. You can find these permissions within by running the Verbose commands OR checking out the LuckPerms Permission page.

==== Filters ====
The filter is an expression used to match permission entries, and ignore entries you don't need. It could just be a player name, or much more advanced.

A filter string will match the start of the permission being checked, or the users full name. You can use <code>&</code> (and), <code>|</code> (or), and <code>!</code> (not / negate) to setup expressions. Parenthesis <code>( )</code> are also supported.

===== Some examples =====

* <code>Luck & (essentials | worldedit)</code> - Matches any checks made against "Luck" that start with "essentials" or "worldedit"
* <code>Luck & !anticheat</code> - Matches any checks made against "Luck" that do not start with "anticheat"
* <code>anticheat & !anticheat.check</code> - Matches checks on all users starting with "anticheat" but not starting with "anticheat.check"

[[File:Verbose command filter.png|center|thumb|1105x1105px|Command Action: <code><nowiki>/lp verbose record Nacholebraa & (essentials | worldedit)</nowiki></code>]]

The web viewer allows you to view the '''same''' information visible in-game just in a cleaner view overall. In certain cases it's easier to review various permissions checks through the Web Viewer than in-game. But it's totally optional and up to the individual running the command.
[[Category:Staff]]

File:Verbose command filter.png

2025-07-26T05:38:24Z

Nacho:

verbose filter example

File:Verbose command functionality.png

2025-07-26T05:31:45Z

Nacho:

Functionality of /lp verbose command

Using LuckPerms Verbose

2025-06-30T01:26:19Z

Nacho:

Using LuckPerms Verbose

2025-06-29T05:12:05Z

Nacho:

Dis a test will work on later xoxoxoxox

Nacho
[[Category:Staff]]

Using LuckPerms Verbose

2025-06-29T05:05:22Z

Nacho: Created page with "Dis a test will work on later xoxoxoxox Nacho"

Dis a test will work on later xoxoxoxox

Nacho

Category:Staff

2025-06-29T04:50:37Z

Nacho:

Anything relating to staff documentation.

Individual staff members should '''NOT''' be categorized here.

Category:Staff

2025-06-29T04:44:24Z

Nacho:

Anything relating to staff documentation.

Individual staff members should '''NOT''' be categorized here.
[[Category:LuckPerms]]