08-25-2017, 11:10 PM
After re-reading your post, I'm hopefully starting to understand what you're reporting. Correct me if I'm wrong.
You start debugging in ZBS (F5, or menu Project -> Run)
Cuberite is started for you by the ZBS Cuberite plugin
You cannot connect to Cuberite using the Minecraft client, nor access the webadmin pages using your browser.
Does Cuberite say "Startup complete, took XYZ ms"? If not, does it report anything in the console? It may take some time for it to start when it is started for the first time (generating worlds etc.)
If you start Cuberite normally (without ZBS), does it start up and can you connect?
Is there a Cuberite server instance already running when you start debugging? (two Cuberite instances from the same folder cannot run at the same time)
If you do a "netstat -nlat", are the debugger's Cuberite ports listed in the output?
You start debugging in ZBS (F5, or menu Project -> Run)
Cuberite is started for you by the ZBS Cuberite plugin
You cannot connect to Cuberite using the Minecraft client, nor access the webadmin pages using your browser.
Does Cuberite say "Startup complete, took XYZ ms"? If not, does it report anything in the console? It may take some time for it to start when it is started for the first time (generating worlds etc.)
If you start Cuberite normally (without ZBS), does it start up and can you connect?
Is there a Cuberite server instance already running when you start debugging? (two Cuberite instances from the same folder cannot run at the same time)
If you do a "netstat -nlat", are the debugger's Cuberite ports listed in the output?