Skip to content

Changes

Page history
Update FAQ authored by Ruan's avatar Ruan
Show whitespace changes
Inline Side-by-side
FAQ.md
View page @ f9c9a501
......@@ -5,15 +5,15 @@
#### **Q:** Permissions are not working as expected. How can I fix this?
**A:**
If "**/litebans version**" indicates that LiteBans is running **under BungeeCord** and not Spigot:
If "**/litebans version**" indicates that LiteBans is running **under BungeeCord / Velocity** and not Spigot:
> **Your permissions plugin must be linked to BungeeCord** in order to work there.
> **Your permissions plugin must be linked to Bungee / Velocity** in order to work there.
> **LuckPerms has native BungeeCord support.** For this, it must be installed in the BungeeCord plugins folder. GroupManager and PEX do not.
> **LuckPerms has native BungeeCord support.** For this, it must be installed in the Bungee / Velocity plugins folder. GroupManager and PEX do not.
> If your permissions plugin is not linked to BungeeCord, your permissions will not function under BungeeCord. **If you can't accomplish this, install LiteBans under Spigot instead of BungeeCord**.
> If your permissions plugin is not linked to Bungee or Velocity, your permissions will not function there. **If you can't accomplish this, install LiteBans under Spigot instead**.
After installing your permission system under BungeeCord, **you need to link everything to the same MySQL database** (all of the backend instances and the BungeeCord instance must be connected). **By default, each instance uses its own database**, which means your permissions won't be synchronized until you've configured it to do so.
After installing your permission system under the proxy, **you need to link everything to the same MySQL database** (all of the backend instances and the proxy instance must be connected). **By default, each instance uses its own database**, which means your permissions won't be synchronized until you've configured it to do so.
**LuckPerms notice:** If you're using **server contexts** for server-specific permissions, the context becomes `server=bungee world=<server>` for Bungee plugins (you can view an online user's current context with `/lpb user <user> info`)
......@@ -23,6 +23,8 @@ A server context like `server=lobby` **WILL NOT APPLY FOR ANY BUNGEE PLUGINS**,
```
LuckPerms(Bungee): /lpb user <user> perm check litebans.ban
LuckPerms(Bungee): /lpb verbose on
LuckPerms(Velocity): /lpv user <user> perm check litebans.ban
LuckPerms(Velocity): /lpv verbose on
LuckPerms(Spigot): /lp user <user> perm check litebans.ban
LuckPerms(Spigot): /lp verbose on
PEX: /pex user <user> check litebans.ban
......@@ -52,7 +54,7 @@ If you want to make **specific** broadcasts silent:
Note that all IP-banned accounts are automatically banned by UUID **AND** IP address, so you don't need to ban players twice to prevent them from using that account on a different IP address.
**Disregard the following if your Bungee configuration has `online_mode: true`:**
**Disregard the following if your Bungee / Velocity configuration has `online_mode: true`:**
In offline-mode, UUIDs are generated based on player names, so players can change their UUID at any time by changing their name.
......@@ -122,9 +124,9 @@ If you have any form of DDoS protection which masks IP addresses (e.g. TCPShield
###### _Two messages for one action / double messages_
#### **Q:** I'm seeing duplicate broadcasts and notifications. How can I fix this?
**A:** If you have LiteBans installed under both Spigot and BungeeCord, then you will get duplicate notifications.
**A:** If you have LiteBans installed under both Spigot and Bungee/Velocity, then you will get duplicate notifications.
To fix this, set `local_messages: false` in the BungeeCord instance's `config.yml`.
To fix this, set `local_messages: false` in the Bungee/Velocity instance's `config.yml`.
Also: check the ban 'response' message in `messages.yml`, it's blank by default but that message is always sent (to the executor only) in addition to broadcasts if set.
......@@ -141,7 +143,7 @@ You can confirm this by testing whether **"/litebans:ban"** can tab-complete pla
Workarounds: give these permissions to the players who need tab-completion, or add [command aliases](https://gitlab.com/ruany/LiteBans/-/wikis/Command-Aliases) in commands.yml (/ban -> /litebans:ban)
**Under BungeeCord**, the permission **"litebans.tabcomplete"** is required to tab-complete players across the network.
**Under BungeeCord & Velocity**, the permission **"litebans.tabcomplete"** is required to tab-complete players across the network.
---
......@@ -212,7 +214,7 @@ You can reduce or disable this setting (by setting it to 0) if you don't want no
#### **Q:** How do I allow banned players to join the hub/lobby server?
**A:** (Spigot): Set this option on the lobby server instance: `disable_login_ban_check: true`. Any server which has this option set will allow banned players to log in.
**A:** (BungeeCord): Modify this option: `disable_login_ban_check_servers: []`. Any server added to this list will allow banned players to log in.
**A:** (Bungee/Velocity): Modify this option: `disable_login_ban_check_servers: []`. Any server added to this list will allow banned players to log in.
---
......@@ -333,7 +335,7 @@ Try running LiteBans on a test server with no other plugins installed.
**A:**
If you're using CraftBukkit instead of Spigot, and your server is in offline-mode, login events won't fire properly. This affects many plugins. Switch to Spigot or install under BungeeCord.
If you're using CraftBukkit instead of Spigot, and your server is in offline-mode, login events won't fire properly. This affects many plugins. Switch to Spigot or install under Bungee/Velocity.
Plugins that can allow banned players to join:
* Anti-Proxy (1.0.5)
......@@ -343,7 +345,7 @@ In offline-mode, plugins like [FastLogin](https://www.spigotmc.org/resources/fas
If you discover any plugins that can cause this problem, let me know and I'll add it to this list.
If you run LiteBans under BungeeCord, it should be much less likely for other plugins to interfere, as the proxy processes login events before the backend servers can, and there are less BungeeCord plugins than Spigot plugins.
If you run LiteBans under Bungee / Velocity, it should be much less likely for other plugins to interfere.
Lastly, ensure that the `disable_login_ban_check` option is not enabled in `config.yml` (It is disabled by default).
......
......