(08-25-2017, 11:10 PM)xoft Wrote: 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?
Thanks for you questions.
- I did not get a Startup complete and the program would terminate after I resumed debugging from the !EnableMobDebug.lua file.
- The console would not report anything. This was being performed on an already initialized Cuberite server and a first-run initialization.
- Cuberite would start normally without ZBS and I could connect.
- There was not an additional Cuberite server running ( looked via "ps" and "lsof" )
-- HOWEVER!
I have found out that if I edit the cuberite.lua ZBS package and redirect the debuggee output to the ZBS Output pane it works.
local pid = CommandLineRun(
Cmd, -- Command to run
ExePath:GetFullPath(), -- Working directory for the debuggee
true, -- <--- WORKS ON MAC! Redirect debuggee output to Output pane? (NOTE: This force-hides the Cuberite window, not desirable!)
true, -- Add a no-hide flag to WX
nil, -- StringCallback, whatever that is
nil, -- UID to identify this running program; nil to auto-assign
OnFinished -- Callback to call once the debuggee terminates
)