Skip to content

chore: cleanup config files #642

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.

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
wants to merge 5 commits into
base: main
Choose a base branch
from
Open

Conversation

Strokkur424
Copy link
Member

Description

This PR cleans up the config files shown on the docs in order to be in-sync with the current ones. Including:

  • Sorting entries to be in-sync with how the server generates the config.
  • Adding and removing various changed/removed entries.

Goal

The goal of this PR is to ease a users orientation between actual server files and the documentation.

- Sorted entries to be in-sync with how the server generates the config.
- Updated fix-entity-position-desync to send-full-pos-for-item-entities.
- Documented prevent-negative-villager-demand.
- Sorted all entries by the order they appear in, generated by the server.
- Removed the no longer existing entities-target-with-follow-range key.
I say cleanup, but really, it was already cleaned up nicely. Just removed an excessive newline lol
Moved up the icanhasbukkit entry to be above the placeholder entry
I feel like I just touched every single of those 750 lines because holy jesus christ
the Spigot config generates in a more random pattern than I have ever seen before.
The generation of the Spigot config could be used as a reference for modern system
which rely on unexplainable randomness in order to encrypt data. Similar to the
wall of 100 lava lamps in the cloudflare office. Instead of lava lamps, they could
seriously just use the Spigot config file. Wow.
Copy link

github-actions bot commented Aug 13, 2025

built with Refined Cloudflare Pages Action

⚡ Cloudflare Pages Deployment

Name Status Preview Last Commit
papermc-docs ✅ Ready (View Log) Visit Preview 5b8f9ea

disable-noteblock-updates:
default: "false"
description: >-
Whether to disable any form of block updates for note blocks on the
server. Disabling block updates leads to note blocks no longer updating
their block state, allowing for technically invalid note blocks to remain
in the world, which might be useful for mapmakers.
which might be useful for mapmakers.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This got lost (should be part of disable-chorus-plant-updates)


- = 0: Always tab-complete all available commands

- \\> 0 only tab-complete commands after n characters are typed. This
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you fix the escape and formatting here while you're at it?

zombie-aggressive-towards-villager:
default: "true"
description: Whether zombies try to seek out and attack villagers.
dragon-death-sound-radius:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe note what happens in relation to the new gamerule (applies to the other similar option)

@Lulu13022002 Lulu13022002 linked an issue Aug 13, 2025 that may be closed by this pull request
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Outdated configuration options for Paper
2 participants