-
-
Notifications
You must be signed in to change notification settings - Fork 189
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
Strokkur424
wants to merge
7
commits into
main
Choose a base branch
from
chore/cleanup-configs
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
built with Refined Cloudflare Pages Action⚡ Cloudflare Pages Deployment
|
4b01a7d
to
8a2bca4
Compare
- 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.
8a2bca4
to
c7b2d40
Compare
zlataovce
approved these changes
Oct 3, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR cleans up the config files shown on the docs in order to be in-sync with the current ones. Including:
Goal
The goal of this PR is to ease a users orientation between actual server files and the documentation.