Using LuckPerms Verbose - Revision history

Mesemi at 05:10, 24 August 2025

2025-08-24T05:10:12Z

← Older revision		Revision as of 05:10, 24 August 2025
Line 51:		Line 51:

	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.		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}}~~


	{{Staff}}		{{Staff}}
	[[Category:Staff]]		[[Category:Staff]]

Mesemi at 05:09, 24 August 2025

2025-08-24T05:09:48Z

← Older revision		Revision as of 05:09, 24 August 2025
Line 54:		Line 54:
	== <big>'''Frequently Asked Questions?'''</big> ==		== <big>'''Frequently Asked Questions?'''</big> ==
	{{DEFAULTSORT:LuckPerms Verbose}}		{{DEFAULTSORT:LuckPerms Verbose}}


	{{Staff}}		{{Staff}}
	[[Category:Staff]]		[[Category:Staff]]

Mesemi at 05:09, 24 August 2025

2025-08-24T05:09:15Z

← Older revision		Revision as of 05:09, 24 August 2025
Line 54:		Line 54:
	== <big>'''Frequently Asked Questions?'''</big> ==		== <big>'''Frequently Asked Questions?'''</big> ==
	{{DEFAULTSORT:LuckPerms Verbose}}		{{DEFAULTSORT:LuckPerms Verbose}}
			{{Staff}}
	[[Category:Staff]]		[[Category:Staff]]

Nacho at 06:03, 26 July 2025

2025-07-26T06:03:00Z

← Older revision		Revision as of 06:03, 26 July 2025
Line 53:		Line 53:

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

Nacho at 05:54, 26 July 2025

2025-07-26T05:54:51Z

← Older revision		Revision as of 05:54, 26 July 2025
Line 2:		Line 2:
	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.		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.		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.		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.
Line 36:		Line 36:
	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 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.		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> ==		== <big>Verbose Filters</big> ==
Line 43:		Line 43:
	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.		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 ~~=====~~		'''Some examples'''

	* <code>Luck & (essentials \| worldedit)</code> - Matches any checks made against "Luck" that start with "essentials" or "worldedit"		* <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>Luck & !anticheat</code> - Matches any checks made against "Luck" that do not start with "anticheat"
Line 52:		Line 51:

	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.		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> ==
	[[Category:Staff]]		[[Category:Staff]]

Nacho at 05:47, 26 July 2025

2025-07-26T05:47:29Z

← Older revision		Revision as of 05:47, 26 July 2025
Line 1:		Line 1:
			== '''<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.		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.		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 ~~monitor~~ '''permission''' checks in real time, providing valuable insights during '''debugging''' and '''configuration'''.		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.

	== How does Verbose work ==		== <big>How does Verbose work</big> ==
	{\| class="wikitable"		{\| class="wikitable"
	!Command		!Command
Line 37:		Line 38:
	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.		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 ==		== <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.		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.

Nacho at 05:42, 26 July 2025

2025-07-26T05:42:51Z

← Older revision		Revision as of 05:42, 26 July 2025
Line 37:		Line 37:
	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.		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 ====		== 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.		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.

Line 49:		Line 49:

	[[File:Verbose command filter.png\|center\|thumb\|1105x1105px\|Command Action: <code><nowiki>/lp verbose record Nacholebraa & (essentials \| worldedit)</nowiki></code>]]		[[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.		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]]		[[Category:Staff]]

Nacho at 05:41, 26 July 2025

2025-07-26T05:41:27Z

@@ Line 26: / Line 26: @@
 |}
 The first argument enables/disables the system, and the second sets up the filter.
 [[Category:Staff]]

Nacho at 01:26, 30 June 2025

2025-06-30T01:26:19Z

@@ Line 1: / Line 1: @@
-Dis a test will work on later xoxoxoxox
+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.
-Nacho
+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'''.
 [[Category:Staff]]

Nacho at 05:12, 29 June 2025

2025-06-29T05:12:05Z

← Older revision		Revision as of 05:12, 29 June 2025
Line 3:		Line 3:

	Nacho		Nacho
			[[Category:Staff]]