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

Handle soldat:// URI #5

Open
helloer opened this issue Dec 22, 2020 · 1 comment
Open

Handle soldat:// URI #5

helloer opened this issue Dec 22, 2020 · 1 comment

Comments

@helloer
Copy link

helloer commented Dec 22, 2020

As a user I want to easily run the game via soldat:// uri. Format of soldat uri is: soldat://server_ip:server_port/server_password
server_port and server_password are optional.

Example:

soldat://8.8.8.8
soldat://127.0.0.1:23073/serverpass
@rzaba0
Copy link
Collaborator

rzaba0 commented Jan 26, 2021

I've added support for soldat:// links. Registering of soldat:// protocol works on Windows. It could also be added on Linux and macOS, but it requires different approaches.

Features:

  • Pasting soldat:// link in Server IP field in Lobby tab fills up all fields, but does not start the game.
  • Launcher can receive a soldat:// link as a command-line argument (./soldat-launcher soldat://127.0.0.1:23074). If you run the launcher like this, it fills up the fields in Lobby tab and starts the game right away.
  • We allow only one process of the launcher to run at a time. If you run the launcher while there is an instance running already, we just restore the window and handle command-line arguments (if any) from there. The reason is that we don't want to spawn a new launcher every time you click a soldat:// link.
  • Registering of soldat:// protocol on Windows. Clicking on a soldat:// link will run the launcher with the link as a command-line argument.
  • Registering of soldat:// protocol on Linux
  • Registering of soldat:// protocol on macOS

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

No branches or pull requests

2 participants