minecraft-debugger
minecraft-debugger copied to clipboard
Mojang
Very troublesome user experience
Hi there. Once I got this extension finally working, it was very pleasant. But wow, I have never seen an extension take so many steps to get working!!
The readme is helpful, but opening a powershell terminal, pasting in the most bizarre random command I've ever seen (pasting random commands from the internet, very secure and recommended practice right?), configuring a JSON file, copying a UUID from my manifest into VSCode, starting a debug session, then finally running a command in-game was not a fun time! And believe me that the errors you get if you miss a step, if they exist at all, aren't super helpful. I'd be hard-pressed to remember all of those steps just to debug a small issue on a random test world.
I'd like to live in a world where this extension works totally out of the box. You open minecraft and vscode, and the diagnostics tab works right away. You open your pack folder and set a breakpoint, and it hits. No weird commands or finicky configuration except in unusual setups. Just a bit of feedback from a grateful but frazzled user. 🙂
Definitely good feedback.
A few things are in the pipe around helping the developer know if something is misconfiguration or get the connection configured more easily.
Unfortunately TypeScript + source maps will always introduce a little bit more complexity due to how different build steps are, but that doesn't mean we should strive for easy of use.
FYI the latest release adds the ability to pick the pack you're debugging when you go to attach the debugger. This should really help with the "copy this random UUID" scenario.
Latest VSCode extension has some usability improvements, including a prompt for the target pack and additional logging. Keep in mind that this will require waiting for the next release of MC. If you can think of anything else that would make on-boarding easier, please let us know. Closing this issue and thanks for the feedback.
