You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently voxel-clientmc is hardcoded to connect to ws://localhost:24444 (or whatever is set in opts.url), it should have some kind of user interface listing to select the server(s) to connect to.
Could also include server pinging (status packets or 0xfe legacy ping), pending wsmc support (showing a detailed server list with icon, players, description, etc.)
The text was updated successfully, but these errors were encountered:
with the intention that servers will run their own wsmc plugins served from their server, so the document hostname will point to the same server (however, non-'localhost' seems to be currently broken in wsmc: deathcap/wsmc#30)
To allow loading voxel-clientmc as a plugin in other apps (e.g. https://github.com/deathcap/voxelmetaverse), could perhaps default opts.url to undefined and if unspecified prompt the user, but set it to 'ws://'+document.location.hostname+':24444/server' in voxel-clientmc/app/app.js for the bundled wsmc jar usage.
Currently voxel-clientmc is hardcoded to connect to ws://localhost:24444 (or whatever is set in
opts.url
), it should have some kind of user interface listing to select the server(s) to connect to.Could also include server pinging (status packets or 0xfe legacy ping), pending wsmc support (showing a detailed server list with icon, players, description, etc.)
The text was updated successfully, but these errors were encountered: