Thread: Lonestar config made easy.

So I got to thinking, why don't we move certain constants into an .ini file of sorts.

I'd be willing to write the code, and was thinking something along the lines of this:


dod_extend_limit 3
dod_map_vote_list file.txt
dod_max_ping 300

something like this, so it would be simple for admins to customize the lonestar portions of the server without having to read the code.

what's wrong with server cvars?

Nothing.

It just kinda hit me that it might be easier to put them all in settings file (or have them be set in the settings file) so constants could be changed easily.
Completely up to you.

I'd rather not. Most admins know cvars.

What we could use though is a GUI editor for the json data config files though. Maybe make it a web one embedded in lonestar-admin....

Originally Posted by Ewok

I'd rather not. Most admins know cvars.

What we could use though is a GUI editor for the json data config files though. Maybe make it a web one embedded in lonestar-admin....

Like, change cvars on the fly thru the web interface?

And I was talking about moving all the cvars to an "ini" file, so that each option we create is easily accessable/changeable. Kinda like a server config.

Originally Posted by Imisnew2

Like, change cvars on the fly thru the web interface?

And I was talking about moving all the cvars to an "ini" file, so that each option we create is easily accessable/changeable. Kinda like a server config.

So you don't need to change configs in individual .py files, Just one central #noted LS config file.

I'm confused. Your asking for a "server config", which is exactly what cvars give you. Admins shouldn't have to edit .py files; they should setup lonestar cvars in their existing server configs....

Originally Posted by Ewok

I'm confused. Your asking for a "server config", which is exactly what cvars give you. Admins shouldn't have to edit .py files; they should setup lonestar cvars in their existing server configs....

Oh ok.
So the constants declared in the .py files are just like "defaults"?

Is there a list of cvars somewhere? Tagged with that they do.

Originally Posted by Imisnew2

Oh ok.
So the constants declared in the .py files are just like "defaults"?

exactly. The first parameter to each of them is the cvar name that an admin can use to control it. The next parameter is the default value.