-
Notifications
You must be signed in to change notification settings - Fork 19
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
Ask if scenario should be started as network game when opeing c4Scenario file #86
Comments
This isn't an engine issue, but an issue of starting the engine with the correct arguments, which would require multiple explorer shell entries. However, Windows 11's new context menu sucks with them. |
What if opening a scenario via the shell just launches it with |
I'm just talking about displaying the dialig if clonk.exe is called with the c4Scenario as only argument. That's the case when double clicking on it. Workflow idea is following:
I don't want to change the behaviour if the user starts a cli and explicitly says |
And I would like to give a concrete use case: scenarios that are not in the clonk folder, but e.g. in the download directory, because you have to quickly host the hastily downloaded scenario from ccan.de, as the network code at the other host is once again causing problems. (Problems from a friend 😉) |
Yes, that’s basically what I am talking about. Although I thought that the file association can include arguments. And in that case I would specify the arguments there as |
So you mean the file extention association in the windows registry for example? And instead a dialog there's always a lobby without masterserver registration opened? I would be okay with both options |
@Fulgen301 is working on this at https://github.com/legacyclonk/LegacyClonk/tree/shell which would also solve the issue at it's best way. |
When double clicking on a .c4s file clonk starts the scenario without network as singleplayer session with currently activated players.
I suggest to ask the user over a dialog wether
The text was updated successfully, but these errors were encountered: