PrismarineJS / PrismarineJS/node-minecraft-protocol

painting variants

Open
#1,083 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
1.4k
Forks
290
Avg merge
4d 8h
Merged PRs (30d)
7

Description

[v] The FAQ doesn't contain a resolution to my issue

Versions

  • minecraft-protocol: 1.36.1
  • server: paper 1.19
  • node: 17.3.1

Detailed description of a problem

Painting variant is always first, cant be viewed/modified

Expected behavior

Painting variants should be proxied too

Additional context

Video

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Reproduce the issue using minecraft-protocol 1.36.1 with a Paper 1.19 server and inspect how painting data is handled while proxying packets. Confirm that variants are preserved and can be viewed or modified, then add or update coverage for the observed behavior; the issue names no source file or test.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
networking
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.