PrismarineJS / PrismarineJS/node-minecraft-protocol
Feature: Separate debug mode flags for blobs
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 290
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 7
Description
Is your feature request related to a problem? Please describe.
Currently, with DEBUG= I see nothing, and with DEBUG=minecraft-protocol, my logs are cluttered with long data URLs from the ping response's favicon.
Describe the solution you'd like
Standard debug mode should avoid dumping large chunks of binary(-like) data. Those blobs should be printed only with additional flags. In my case, since even login fails, I don't know what else might be there beyond the favicon, but I imagine someone who wants to debug player skins may want to not enable the flag for chunk data.
Describe alternatives you've considered
Current work-around: Filter output through sed.
Additional context
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the DEBUG handling and packet logging entry points, focusing on the ping response favicon and other binary-like data such as chunk data or player skins. Define separate opt-in flags for these blobs while keeping standard debug output readable, then verify that the default and additional flag behaviors match the requested logging separation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100