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

more options in server configuration #45

Open
mushis opened this issue Jun 6, 2020 · 0 comments
Open

more options in server configuration #45

mushis opened this issue Jun 6, 2020 · 0 comments

Comments

@mushis
Copy link

mushis commented Jun 6, 2020

The plan is to abandon the "old" nquakesv linux installer, but I think it will be used for many more years, because of its simplicity and people are used to it.
here's a suggestion on how to improve it.

in the script, the scripts ask us how many ports we want to run. I suggest that we add an advanced menu option in that prompt.

the advanced menu, when selected, would print more options to the qwsv configuration.
here's a quick mockup of how it would look,:

Number of KTX ports setup: 0
Add a port using the prompt below

Options:
a) supports bots [SELECTED]
b) default instagib
c) default hoonymode (normal ktx only)
d) default midair (normal ktx only)
e) default race (normal ktx only)
z) don't publish to masterserver (for lans or private events)

Add port:
1) normal KTX
2) FFA only
3) CTF only
4) Clan Arena only

type X to exit.
Your command: _

This would add more flavours to KTX, the current server listing is so bland.
I thought this advanced menu would be nicer if it was on a separate screen, refreshing the menu (with clear and rendering the menu again) when the user inputs a command.
when the user eXited, the script continued where it was before.
More options can be added ofc.
any advanced bash user could do this, I see this as an independent section of the install_nquake.sh script.

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

1 participant