mirror of
https://github.com/arcadiadevs/playerservers-wiki.git
synced 2024-11-29 06:35:33 +01:00
36 lines
1.7 KiB
Markdown
36 lines
1.7 KiB
Markdown
# Max plugins limitation
|
|
|
|
## Introduction
|
|
|
|
We know that making a permission-based plugins limitation system is a crucial to our customers and could be greately used for online stores in order for them to earn money for Ranks & Perks, so we've implemented a permission-based plugin limitation system. In this tutorial, you'll learn how to configure it for your needs.
|
|
|
|
## Tutorial
|
|
|
|
In order to begin, you'll need to change a few config options. Make sure your plugin-limiting part of the config looks as following:
|
|
|
|
```yaml
|
|
plugin-limiting:
|
|
# Should we use permissions for max-plugins management? If set to true, your
|
|
# players should have playerserver.plugins.<amount>. The max amount of plugins
|
|
# that you could give to a single server is 20000. You can also give them
|
|
# playerserver.plugins.unlimited - for unlimited plugins. If the player
|
|
# has no permission, he'll be able to have unlimited players.
|
|
#
|
|
# NOTE: If you use permissions, and you change player's permissions,
|
|
# their server will need to reboot in order for changes to take place.
|
|
use-permissions: true
|
|
|
|
# What is the max players each server should have?
|
|
max-plugins-per-server: 20
|
|
```
|
|
|
|
By enabling use-permissions, the plugin will ignore max-plugins-per-server option and will use permission-based plugin limiting system.
|
|
|
|
The next thing you'll wanna do is to give all the groups that have `playerserver.manage` permission a new permission as following: `playerserver.plugins.<amount>`. Here's an example in LuckPerms:
|
|
|
|
```yaml
|
|
/lp group default permission set playerserver.plugins.10
|
|
```
|
|
|
|
If your groups have parent permission, the plugin will give the player the largest possible amount of plugins by their permission.
|