Skip to content

feat: add collapsible sections for config files (#124) #140

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Gteeri wants to merge 1 commit into
base: 1.21.11
Choose a base branch
from
Open

feat: add collapsible sections for config files (#124) #140

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 18 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand All @@ -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
Expand All @@ -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
Expand All @@ -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
Expand Down