Add paperweight compatibility section

.vitepress/config.mts

@@ -79,6 +79,10 @@ export default defineConfig({
               text: "Adventure",
               link: "docs/en/user_guide/advanced/adventure",
             },
+            {
+              text: "Paperweight Compatibility",
+              link: "docs/en/user_guide/advanced/paperweight",
+            },
           ],
         },
         {

docs/en/user_guide/advanced/adventure.md

@@ -1,10 +1,12 @@
 ---
 outline: deep
 title: Adventure
-next: false
 prev:
   text: "Create a Custom Server Mock"
   link: "/docs/en/user_guide/advanced/custom_server_mock"
+next:
+  text: "Compatibility with paperweight"
+  link: "/docs/en/user_guide/advanced/paperweight"
 ---
 
 # Adventure

docs/en/user_guide/advanced/paperweight.md

@@ -0,0 +1,35 @@
+---
+outline: deep
+title: Compatibility with paperweight
+next: false
+prev:
+  text: "Adventure"
+  link: "/docs/en/user_guide/advanced/adventure"
+---
+
+# Compatibility with paperweight
+
+MockBukkit is not compatible with the paperweight provided artifact (also known as NMS).
+Whenever these two artifacts are simultaneously provided at test time, you will stumble uppon
+multiple issues that stem from providing two separate server implementations at the same time.
+This is not possible to fix without completely rewriting MockBukkit!
+
+## The general pattern of these issues
+
+- Something has not been initialized
+- Two service providers can not be provided simultaneously
+
+## The solution
+
+There's no perfect solution, as it's impossible to have both dependencies at test time, but you can
+exclude the paperweight provided artifact at test time now with paperweight 2.
+
+```kts
+paperweight {
+  addServerDependencyTo = configurations.named(JavaPlugin.COMPILE_ONLY_CONFIGURATION_NAME).map { setOf(it) }
+}
+```
+
+::: warning
+With this, you can't use any NMS behavior during tests with MockBukkit
+:::