Skip to content

Commit 9670779

Browse files
authored
chore: Mention library plugins in binary search (#402)
1 parent 3a55539 commit 9670779

File tree

1 file changed

+10
-1
lines changed

1 file changed

+10
-1
lines changed

docs/paper/admin/how-to/basic-troubleshooting.md

Lines changed: 10 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -69,7 +69,7 @@ If you don't have any backup of your world before the chunk version update, you
6969

7070
</details>
7171

72-
## Find the culprit
72+
## Finding the culprit
7373

7474
If you can't find the name of any plugin in the thread dump or stack trace, try these steps.
7575

@@ -98,6 +98,15 @@ To efficiently search for the plugin that is causing the issue, you can do the f
9898
4. **Repeat from the start with the suspect plugin group**
9999
Repeat the steps above with groups that have the plugin that is causing the issue.
100100

101+
:::danger
102+
103+
Some plugins that you install are not a typical plugin, but a library. These are installed like plugins,
104+
however tend to offer few user-facing features and are relied upon by other plugins for their
105+
functionality. If you disable a library, plugins that depend on it will not work properly. Common
106+
examples of these libraries are ProtocolLib, Vault providers, permission plugins, etc.
107+
108+
:::
109+
101110
## Check plugin updates
102111

103112
There is a chance that your problem is already fixed in the latest release or latest build of the plugin.

0 commit comments

Comments
 (0)