From f65f4a7a490ba66e2afb200794983f48bfb307b2 Mon Sep 17 00:00:00 2001
From: Gteeri <hayrullaevmaga@gmail.com>
Date: Thu, 14 May 2026 17:35:50 +0600
Subject: [PATCH] feat: add collapsible sections for config files (#124)

Added <details> tags to wrap configuration file sections, allowing users to collapse sections they don't need. This makes navigation easier, especially for users who only use specific server software.
---
 README.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/README.md b/README.md
index fdac487..a528708 100644
--- a/README.md
+++ b/README.md
@@ -39,6 +39,9 @@ It's key to remember that the overworld, nether and the end have separate world
 
 ## Networking
 
+<details>
+<summary>server.properties</summary>
+
 ### [server.properties]
 
 #### network-compression-threshold
@@ -47,6 +50,11 @@ It's key to remember that the overworld, nether and the end have separate world
 
 This allows you to set the cap for the size of a packet before the server attempts to compress it. Setting it higher can save some CPU resources at the cost of bandwidth, and setting it to -1 disables it. Setting this higher may also hurt clients with slower network connections. If your server is in a network with a proxy or on the same machine (with less than 2 ms ping), disabling this (-1) will be beneficial, since internal network speeds can usually handle the additional uncompressed traffic.
 
+</details>
+
+<details>
+<summary>purpur.yml</summary>
+
 ### [purpur.yml]
 
 #### use-alternate-keepalive
@@ -58,10 +66,15 @@ You can enable Purpur's alternate keepalive system so players with bad connectio
 > Enabling this sends a keepalive packet once per second to a player, and only kicks for timeout if none of them were responded to in 30 seconds. Responding to any of them in any order will keep the player connected. AKA, it won't kick your players because 1 packet gets dropped somewhere along the lines  
 ~ https://purpurmc.org/docs/Configuration/#use-alternate-keepalive
 
+</details>
+
 ---
 
 ## Chunks
 
+<details>
+<summary>server.properties</summary>
+
 ### [server.properties]
 
 #### simulation-distance
@@ -78,6 +91,11 @@ This is the distance in chunks that will be sent to players, similar to no-tick-
 
 The total view distance will be equal to the greatest value between `simulation-distance` and `view-distance`. For example, if the simulation distance is set to 4, and the view distance is 12, the total distance sent to the client will be 12 chunks.
 
+</details>
+
+<details>
+<summary>spigot.yml</summary>
+
 ### [spigot.yml]
 
 #### view-distance