PrismarineJS / PrismarineJS/node-minecraft-protocol
Testing using the vanilla client ?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 290
- Avg merge
- 4d 8h
- Merged PRs (30d)
- 7
Description
Might be fun to test some things. Problems to solve:
- download the jar (see https://github.com/Mojang/LegacyLauncher)
- making xvfb work in circle ci
- run the client and connect it to a server in cli
See an example of usage of xvfb (and some automation stuff) in travis ci there
Some of this should probably go in minecraft-wrap.
Might want to look at https://github.com/exitedprotek/Nodejs-Minecraft-Launcher/blob/master/app/app.js
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 reviewing the completed jar download and the remaining CircleCI xvfb and CLI connection tasks. Compare the linked Travis xvfb script and Node.js Minecraft Launcher example, and check whether the work belongs in minecraft-wrap. Done means the vanilla client can run in the test environment and connect to a server from the CLI.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- ci-cd, cli, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100