minecraft-packet-debugger
minecraft-packet-debugger copied to clipboard
Test the app on windows
Does everything work on windows?
nope
C:\Users\me>mcpd C:\Users\me\AppData\Roaming\npm\node_modules\mcpd\lib\config.js:56 save(defaultConfig).then(({ error }) => { ^ ReferenceError: save is not defined at Object.
hmm What's your node version?
C:\Users\me>node -v
v12.16.1
hmm seems to work well on 13.11.0 but I'll fix it
OK thankw
@zRattly update mcpd and check now ;)
trying
Tryed connecting, crashed my minecraft lol
For now 1.12.2 is hardcoded ;/
oh, tryed joining with 1.8.9 lol
but there are some errors in gui and console
{"statusCode":500,"code":"ENOENT","error":"Internal Server Error","message":"ENOENT: no such file or directory, open 'C:\Users\giova\public\index.html'"} this is the web error
UnhandledPromiseRejectionWarning: Error: ENOENT: no such file or directory, mkdir 'C:\Users\me\AppData\Roaming\mcpd\Config' at Object.mkdirSync (fs.js:840:3) at C:\Users\giova\AppData\Roaming\npm\node_modules\mcpd\lib\config.js:59:12 (node:4568) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict
(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:4568) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (this is in the console)
@zRattly should've fixed those two errors
still an issue in the latest release
@Ethan-Vann, there's an open PR for that #10
@Ethan-Vann, @zRattly any news after #10 has been merged?
should have tried this before. just switched to arch to test back then. is the npm build outdated? grabbing with npm produces same error but getting from source is working now
Yup, use the github version
Now we need to update NPM package and close this issue
@Saiv46 so you confirm it working?
Yep.
@wvffle Fixed package version still not published :/
Thanks for reminding me that. Currently I have no spare time for mineflayer related projects. Lots of work and also studies :/
I'll publish it in a minute
Edit: already done, @Saiv46