PrismarineJS / PrismarineJS/node-minecraft-protocol
Test client against 3rd party server software
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 290
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 7
Description
Along the lines of adding more testing https://github.com/PrismarineJS/node-minecraft-protocol/issues/281, would also be good to add automated tests with the clients connecting to various third-party server software out there, to catch any bugs with node-minecraft-protocol's interaction with their implementations (bugs could either be theirs or ours).
Notable server software (non-Forge, for that see https://github.com/PrismarineJS/node-minecraft-protocol-forge/issues/5):
- vanila Minecraft
- SpigotMC
- SpongeVanilla
- Glowstone++
- Cuberite
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 reading issue #281 and the linked Forge testing issue to understand the existing automated-testing approach. Review the listed SpigotMC, SpongeVanilla, Glowstone++, and Cuberite targets and determine how client connections would be run against each. Done means automated coverage exists for the selected unchecked server implementations and distinguishes client bugs from server incompatibilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- networking, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100