Is your feature request related to a problem?
Yes. When a datapack produces recurring errors (e.g. during /reload or ticking), Paper logs these errors every time they occur.
While this behavior is correct from a debugging perspective, it creates significant log spam on production servers, making it harder to notice real issues such as plugin errors or crashes.
Currently, the only way to suppress these messages is by modifying log4j2.xml, which:
- Requires deep knowledge of Log4j2 internals
- Is error-prone for non-technical server administrators
- Gets reset or forgotten during server updates
Describe the solution you'd like.
Add a simple, admin-friendly way to control datapack logging verbosity, such as:
logging:
datapack-errors: false
- Or a predefined logger name documented clearly in the Paper docs, so admins can easily override it in
log4j2.xml
The goal is not to hide datapack errors by default, but to give server owners a supported, low-friction way to reduce log noise when they already understand the cause.
Describe alternatives you've considered.
- Editing
log4j2.xml directly — works, but is too complex for most users
- Disabling the datapack entirely — not always feasible (e.g. required by map or gameplay)
- Using external log filtering tools — overkill for small servers
Other
This is primarily a quality-of-life improvement for server administration, not a request to change datapack validation behavior.
Vanilla Minecraft itself does not provide a UI or config for this, so Paper is in a good position to improve the experience without breaking compatibility.
Is your feature request related to a problem?
Yes. When a datapack produces recurring errors (e.g. during
/reloador ticking), Paper logs these errors every time they occur.While this behavior is correct from a debugging perspective, it creates significant log spam on production servers, making it harder to notice real issues such as plugin errors or crashes.
Currently, the only way to suppress these messages is by modifying
log4j2.xml, which:Describe the solution you'd like.
Add a simple, admin-friendly way to control datapack logging verbosity, such as:
paper.ymloption like:log4j2.xmlThe goal is not to hide datapack errors by default, but to give server owners a supported, low-friction way to reduce log noise when they already understand the cause.
Describe alternatives you've considered.
log4j2.xmldirectly — works, but is too complex for most usersOther
This is primarily a quality-of-life improvement for server administration, not a request to change datapack validation behavior.
Vanilla Minecraft itself does not provide a UI or config for this, so Paper is in a good position to improve the experience without breaking compatibility.