pluginmsg instead of bungee (#9)

Tobi406 2019-04-01 17:00:18 +02:00 committed by Luck
parent 17cbb21bec
commit ca48ace672
2 changed files with 5 additions and 4 deletions

@ -71,7 +71,8 @@ This means that `storage-method` should be set to 'mysql', 'mariadb', 'postgresq
The "Messaging Service" is a feature within LuckPerms which allows servers to notify other servers within the network whenever changes are made. It also allows log entries to be dispatched across the network.
* If you're running a small network with one BungeeCord proxy, then you should set this option to `bungee`.
* If you're running multiple servers which are not connected to one proxy, but use the same database set this option to `sql`.
* If you're running a small network with one BungeeCord proxy, then you should set this option to `pluginmsg`.
* If you're running a LilyPad network, set this to `lilypad`.
* If you're running a network with more than one BungeeCord proxy, then it is advisable to install a Redis server (if you're running a network with more than one proxy, I'll assume you already know how to do this!), and set this option to `redis`. Remember to fill out your Redis credentials after changing this option!
@ -83,6 +84,6 @@ A common misconception with the BungeeCord version is that it's a replacement fo
When LuckPerms is installed on a BungeeCord proxy, it does two things:
* It handles permissions checks made by **BungeeCord plugins**. It does *not* intercept or handle permission checks made by plugins on the backend server.
* It forwards update notifications and log messages around the network when `messaging-service` is set to 'bungee'.
* It forwards update notifications and log messages around the network when `messaging-service` is set to 'pluginmsg'.
This means that if you want LuckPerms to respond to permission checks on your backend Spigot or Sponge server, you need to install it there too, even if you have it on your proxy.

@ -44,8 +44,8 @@ A messaging service can be configured in the config, under the `messaging-servic
| Service | Description |
|---------|-------------|
| sql | Uses the SQL database to form a queue system for communication. This is chosen by default if remote SQL storage is in use. |
| bungee | Uses the plugin messaging channels to communicate via BungeeCord. LuckPerms must be installed on your proxy & all connected servers backend servers. Won't work if you have more than one BungeeCord proxy. |
| pluginmsg | Uses the plugin messaging channels to communicate with the proxy. LuckPerms must be installed on your proxy & all connected servers backend servers. Won't work if you have more than one proxy. |
| lilypad | Uses LilyPad Connect's PubSub system to communicate. |
| redis | Connects to a Redis instance and uses PubSub to communicate. |
It is also possible to provide your own implementation of this service via the LuckPerms API.
It is also possible to provide your own implementation of this service via the LuckPerms API.