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

Allow trusted clients to change server settings #4114

Closed
DorpsGek opened this issue Sep 8, 2010 · 5 comments
Closed

Allow trusted clients to change server settings #4114

DorpsGek opened this issue Sep 8, 2010 · 5 comments
Labels
component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

DorpsGek commented Sep 8, 2010

Razmir opened the ticket and wrote:

Hi,
I thought of one feature, which could be useful for all players, who run dedicated multiplayer servers and who need to change some settings.
My idea:
Situation 1: I run ingame multiplayer server (I mean non-dedicated) - I can change all advanced settings easily via GUI.
Situation 2: On the other hand, when I am running dedicated server, I need to change all settings by typing sometimes quite long commands like (example):
settings construction.raw_industry_construction 2
in server console or even longer:
rcon rconpwd "settings construction.raw_industry_construction 2"
from connected client (for example when dedicated server is running on remote computer). Even worse is the fact, that I need to search for exact name of majority of settings before changing them, because I don't remember all exact names.
My solution would be some client-console command (lets say named sudo) which would allow to change settings from GUI of connected clients. I would type only:
sudo rconpwd
in connected client and it would allow me to change all settings from GUI as if in Situation 1. I hope it could internally send the same rcon commands to the server, so it would not be too hard to implement (but surely too hard to do it myself).
So, I pretty please, can you do it for us? (I hope it will sound like a good idea to you too.)
Thanks, Razmir.

Reported version: Version?
Operating system: All


This issue was imported from FlySpray: https://bugs.openttd.org/task/4114
@DorpsGek
Copy link
Member Author

planetmaker wrote:

My idea for the interface in this respect would be a setting similar to the company password which can already be automatically set upon creation to the chosen value, or similar, the nickname. Possibly one could add a setting 'rcon password' in the client-settings section of the adv. settings which takes the rcon password.


This comment was imported from FlySpray: https://bugs.openttd.org/task/4114#comment8752

@DorpsGek
Copy link
Member Author

TruePikachu wrote:

Are you referring to settings settable from "Advanced Options", or the settings only settable from console and openttd.cfg? If the former, then the command should be more like "su", as you're not really sudo-ing. If the latter, we should wait until someone makes a dialog which can change all settings (/me thinks of that one feature from Firefox)


This comment was imported from FlySpray: https://bugs.openttd.org/task/4114#comment8766

@DorpsGek
Copy link
Member Author

Razmir wrote:

I was refering only to settings settable from "Advanced settings" dialog, but only because it would (I hope) allow to reuse existing dialog without need of creating new one. It could be expanded later for all settings, but it is not necessary, there is most of often needed settings in that existing dialog.
And you are right, "su" name is closer to the logic than "sudo", but it does not matter, it was only example name...


This comment was imported from FlySpray: https://bugs.openttd.org/task/4114#comment8775

@DorpsGek
Copy link
Member Author

TruePikachu wrote:

Well, it should be relativly simple. I think that the only problem would be transferring the ENTIRE settings matrix (read: including client-specific settings) in a timely fashion. Otherwise, taking the other and more sane route, having client-specific settings change the local game, and game-specific option changes being sent to the server via RCON, it would easily be made as a patch, if the coding for the Advanced Options window allows


This comment was imported from FlySpray: https://bugs.openttd.org/task/4114#comment8779

@DorpsGek
Copy link
Member Author

andythenorth closed the ticket.

Reason for closing: Won't implement

Flyspray clean up: not a current goal for OpenTTD, more than 5 years old, and not obvious what should be done with this next, so closing. If this offends, discuss with andythenorth in irc. Thanks.


This comment was imported from FlySpray: https://bugs.openttd.org/task/4114

@DorpsGek DorpsGek added component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) enhancement labels Apr 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)
Projects
None yet
Development

No branches or pull requests

1 participant