Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Testing using the vanilla client ? #281

Open
1 of 3 tasks
rom1504 opened this issue Oct 9, 2015 · 5 comments
Open
1 of 3 tasks

Testing using the vanilla client ? #281

rom1504 opened this issue Oct 9, 2015 · 5 comments
Labels

Comments

@rom1504
Copy link
Member

rom1504 commented Oct 9, 2015

Might be fun to test some things. Problems to solve:

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

@rom1504
Copy link
Member Author

rom1504 commented Dec 17, 2015

https://github.com/octalmage/robotjs might be interesting

@rom1504
Copy link
Member Author

rom1504 commented Feb 27, 2016

What would be really interesting here would be just connecting the vanilla client to the vanilla server through nmp proxy and to listen on errors. (automatically, in a test)

Running the proxy is a much better test than what we have currently.

@rom1504
Copy link
Member Author

rom1504 commented Mar 21, 2016

https://github.com/rom1504/node-minecraft-wrap can now download the jar

@rom1504
Copy link
Member Author

rom1504 commented Jul 17, 2017

@rom1504
Copy link
Member Author

rom1504 commented Jul 18, 2017

only thing missing for this is automating the connection to a given server PrismarineJS/node-minecraft-wrap#14

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant