Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Server selection list UI #29

Open
deathcap opened this issue Feb 8, 2016 · 2 comments
Open

Server selection list UI #29

deathcap opened this issue Feb 8, 2016 · 2 comments

Comments

@deathcap
Copy link
Member

deathcap commented Feb 8, 2016

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.)

@deathcap
Copy link
Member Author

deathcap commented Feb 8, 2016

Maybe not strictly necessary, the current default is actually (in clientmc.js):

    opts.url = opts.url || 'ws://'+document.location.hostname+':24444/server';

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)

@deathcap
Copy link
Member Author

deathcap commented Feb 9, 2016

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant