67f2c40 fix: invalidate assets cache if configuration or i... - zlataovce
a41922e fix: remote image revalidation error - zlataovce
9c1d1dd fix: prevent format workflow from uploading build... - zlataovce
f44d110 feat: update for Paper 26.1 (#741) - Strokkur424
ded3b45 Update paperDevBundle dependency format in userdev... - Wuason6x9
b774723 chore(paper): document dynamic build version fetch... - Strokkur424
b9850ff chore(paper): include .build in Maven version rang... - Strokkur424
7cd5ede chore(paper): cleanup project setup Gradle label - Strokkur424
bb684e0 chore(paper): cleanup project setup main class des... - Strokkur424...
#docs
2177 messages · Page 3 of 3 (latest)
d25619c feat(paper): document Pathfinder and Mob Goal APIs... - olijeffers0n
[PaperMC/docs] branch deleted: feat/document-mob-goals
It's as Lulu said. Dialog tag key modification stuff is purposefully not documented on this page due to no companion page explaining the concept in-detail being present yet. This would be added as soon as the tag flatten events are documented properly.
Please remove this section for now.
LGTM once you remove the dialog registry key addition section, which will be added at a later time, as explained in my review comment.
Couldn't you just use the backticks here too instead of the <code> tag, or am I missing something?
9343356 chore(paper): don't mention world name explicitly - Lulu13022002
In light of the fact that the vanilla debugging commands are now accessible, I would like to suggest adding them to the Permissions page.
The "/chase" command can be enabled using the "CHASE_COMMAND" debug property, while the rest of them can be enabled using the "DEV_COMMANDS" debug property.
where it should act on all worlds or just the sender's current world. This also affects World time API.
Should add what it currently includes: Mob spawning, random block ticking, thunder, ice and snow creation
274d0a1 feat(paper): document world config for unsupported... - Doc94
b68f110 feat(paper) document global config for misc.max-tr... - Doc94
This PR adds documentation for the particles added in 26.2 update. All particles are related to the new geyser feature.
Starting off as a draft, because the particle names aren't confirmed and missing Javadoc links for options and whatnot.
This PR handle a mention in discord related to a few docs still use the old world structure reference for config files.
[PaperMC/docs] Pull request approved: #767 feature(adventure): add notes about archival of -platform
could also use a destructive banner like on the Waterfall pages if the asides don't grab attention enough
"Support's" is not grammatically correct, "supports" should be used.
Just a single character fix I noticed when reading the page.
please fix it also for the other occurrences, otherwise LGTM
Oh right that message is duplicated for all unmaintained platforms. I think that's all of them.
19b43b3 chore: "Support's" should be "Supports" (#768) - Cubicake
https://github.com/PaperMC/Paper/pull/13927
Vanilla unload as much as chunks as possible, if there still gets time before next tick. However Moonrise does not check for tick time
So I'm not sure if I should put vanilla value for min-chunk-unload-count
TODO: Someone make the Copy Markdown button more pretty
This pull request introduces a new agent-docs plugin for the Astro project, enabling documentation pages to be exported as Markdown files and adding a "Copy Markdown" button to each page. It also sets up special routes to provide both an index and a full export of all documentation in Markdown format, making the docs more accessible for LLMs and agentic tools.
The most important changes are:
Plugin Integration and Configuration:
- Added the
agent-docsplugin to the Astro configuration, which sets up custom integrations and overrides thePageTitlecomponent to include a "Copy Markdown" button. (astro.config.ts,src/plugins/agent-docs/index.ts) [...
Idk if this is possible nicely, but serving user agents, that have send an accept header with markdown as a higher prior than html, the markdown content would be a nice feature.
Hi! I’d like to work on this issue. I’ll update the bug fixes page to clarify that enabling the tripwire hook duplication option does not guarantee that every duplicator design will work, and I’ll include the referenced implementation/design links.
Summary
- Clarifies that enabling tripwire hook duplication does not make every duplicator design work
- Explains that designs relying on a same-tick door update may still fail because of Paper's block physics handling
- Links the maintainer explanation, original implementation, and tested duplicator design
Testing
- Ran
pnpm exec prettier src/content/docs/paper/admin/misc/paper-bug-fixes.md --check - Ran
pnpm run build - Confirmed all internal links are valid
Closes #712
This class was removed in Adventure 5.x and is generally not relevant any more due to modern MC using Java >9.
Hi! I’d like to work on this issue. I’ll update the entity-activation-range documentation to explain how the miscellaneous range affects dropped items, the behavior users may see outside that range, and how to restore vanilla ticking behavior.
Summary
- Expands the documentation for the miscellaneous entity activation range
- Clarifies that dropped items are affected by this setting
- Explains that reduced ticking outside the range may cause items in water streams to lag or rubber-band
- Documents how setting the value to
0or less disables activation-range throttling for loaded miscellaneous entities
Testing
- Ran
pnpm exec prettier "src/config/paper/spigot.yml" --check - Ran
pnpm run build - Confirmed all internal links are valid
Closes #713
With the migration of the adventure javadocs to https://jd.papermc.io/ this PR manage to use the jd component for point to that docs and also update the javadoc url in the adventure section (used for the j icon)
the only "issue" is the whole module reference like (jd:adventure:net.kyori.adventure.api:net.kyori.adventure.sound.Sound.Emitter#self()) maybe can be good include all the modules like adventure_api: { url: "https://jd.papermc.io/adventure", module: "net.kyori.adventure.api" }, and then use (jd:adventure_api:net.kyori.adventure.sound.Sound.Emitter#self()) but its just for have less text in the component....
https://docs.papermc.io/paper/dev/debugging/
that page could mention the -Ddisable.watchdog=true system prop and maybe mention https://modrinth.com/mod/timeoutout for client timeouts
to improve the debugging experience
context: #general message
and #docs-website message
[PaperMC/docs] New branch created: lilfix/tofile
The command only works lowercase.
It seems like either "Id" or "Name" has to be present for it to be valid. It doesn't have to be "Id"
e80d5e1 Add vanilla debugging commands and their... - Mickey42302
`GEYSER_BASE` and `GEYSER_POOF` particles function identically, differing only in appearance. They use
Starting values of `xd` and `zd` are in the range `[-0.1, 0.1]`, while `yd` is in the range `[0.0, 0.2]`.
You put the other number ranges into code blocks too, so I'd repeat it here.
I have no idea why the deployment build fails in CI, as it works perfectly fine locally with pnpm build, which is also what the CI does. I wish you the best fixing it, Doc!
Error: Received dead status for Javadoc link "jd:adventure:net.kyori.adventure.api:net.kyori.adventure.chat.ChatType.Bound"
I think the CI env runs with some extra checks?
Oh yeah, appending CI=true before the build command does make it run into the same problem. Thanks for the heads-up, cat. Will look if I can figure this out.
c942fc2 chore(paper): clarify tripwire hook dupl... - charlierichards13
This is a good clarification, however at the same time, this general explanation holds true for all entity types. I think you should move the "general" description onto the parent entity-activation-range key and keep only the issues this may cause for items in specific in the misc description.
I find your wording kinda odd and too technical, I think rephrasing it to just "messages/commands per second" is much clearer for the average reader.
description: "Defines how many messages per second a player must send to be kicked for spamming. To disable this, set to 0."
description: "Defines how many commands per second a player must send to be kicked for spamming. To disable this, set to 0."
Thanks for the review! I moved the general activation-range explanation to the parent entity-activation-range key and kept the misc description focused on the dropped-item behavior in water streams.
I also reran:
pnpm exec prettier "src/config/paper/spigot.yml" --checkpnpm run build
I guess there are too many server panels out there. Not really much to describe
df33728 feat(misc): Pufferpanel Java Update (#780) - Chamogelastos
I guess it needed a bit rephrasing
The current example for github workflow its outdated, this PR just update that with latest version and actions deps.
I don't think removing it entirely is the best option here. Instead add a notice that is discontinued. The forums are still up and contain old, but useful threads.
You don't need whitespace in asides. I also reccomend using caution instead.
:::caution
After careful consideration and due to limited usage, we’ve made the decision to discontinue the PaperMC forums. Moving forward, we recommend using Hangar for plugin uploads, and for all other community discussions and support, please join us on Discord.
:::
Why the extra whitespace here?
Should we do it as a "note" or "caution" would be better
I don't think removing it entirely is the best option here. Instead add a notice that is discontinued. The forums are still up and contain old, but useful threads.
But as a means of getting in contact with anyone, a read-only forum is useless.
I believe this calls for a caution. Note is more useful for stuff like "oh btw this thing does this small thing as well". Caution is more like "hey before you go ahead, this thing does something you should know about".
Danger is "dont do anything before reading this"
The only reason I used whitespaces is beause it is used throughout the docs. I also believe it would be more fitting as a note
I don't think removing it entirely is the best option here. Instead add a notice that is discontinued. The forums are still up and contain old, but useful threads.
But as a means of getting in contact with anyone, a read-only forum is useless.
+1 this section is for contact, even not sure if the twitter can be consider a good way to contact....
I remember the website mention a email for contact
I believe the current one is a decent middleground between those two
I believe the current one is a decent middleground between those two
for me im not sure... Because next to that notice still says you can use for support/contact when its read only and the final of all says the first two are the most check...
Maybe a docs team oppinion can be good
for me im not sure... Because next to that notice still says you can use for support/contact when its read only and the final of all says the first two are the most check...
Maybe a docs team oppinion can be good
I mean they always have the last talk
Yea IMO the Twitter section should also have a warning seeing that the last post is from 2022.
And instead maybe link to the news page?
But I don't even think that really fits in a 'Contact Us' page
Also there's this idk if it is actively watched though: https://forums.papermc.io/misc/contact
The last twitter post was in May, twitter just hides most posts if you're not signed in.
Adds the documentation for https://github.com/PaperMC/Paper/pull/14089 should it get merged.
"default" defaults to 5. Set to 0 to disable the catchup.
I mean, overall I initially expected the behavior to be
final long catchup = 1L + io.papermc.paper.configuration.GlobalConfiguration.get().misc.catchupTicks.or(4);
instead of
final long catchup = (long)Math.max(
1,
io.papermc.paper.configuration.GlobalConfiguration.get().misc.catchupTicks.or(5)
);
when I first saw that option. That said, if this is the intended behavior, it would be good to document that the minimum effective enabled value is 2, or at least mention that setting it to 1 is equivalent to 0.