[mohaa] bf1942 and mohaa updates.

[Richard Harrison]

Does this rely on the private clients variable being set to = the maxclients
variable? If so then its still really the Private password which is intended
for internal clan use. I am trying to get the concept of the public password
and private password working.

Anyway in the hope its not I will try it soon :)

Still seems a 'workaround' and not solving the problem :(

Cheers for the tip.

Hazzie.

-----Original Message-----
From: Steve Beck [mailto:spbeck at 2laurelbank.nildram.co.uk]
Sent: 12 October 2002 16:20
To: mohaa at icculus.org
Subject: Re: [mohaa] bf1942 and mohaa updates.


here is a tip to get a public password set on your server

in the server1.cfg file (or whatever yours is called add the line

sv_privatePassword xxxx

xxxx can be whatever u like...

after you restert your server u can type the following in the console to set
a password

rcon Password yyyyyy where yyyyy is the password u want. (note it dont have
to be the same as what you set in the cfg file)

when u rcon restart your server is passworded with whatever u set yyyyyy to.

to unset

rcon Password ""

or simply shut down and restart your server.

I hope you all find this usefull


----- Original Message -----
From: "Richard Harrison" <richardnharrison at btinternet.com>
To: <mohaa at icculus.org>
Sent: Saturday, October 12, 2002 3:20 PM
Subject: RE: [mohaa] bf1942 and mohaa updates.


> Ryan,
>
> a few suggestions (I am not sure if they fall into the conversion type
arena
> or the general development arena which you might not be able to do).
>
> 1) Is it possible to get the whole pure server thing running properly?
>
> 2) How's about getting the whole password protection system working
> correctly. Unless I am doing things wrong the only way I can password
> protect my server is to bump up the Private clients to the maxclients
number
> and then issue a private password to all (even the other clan) to play. I
> have never been able to put a general public password in to the server and
> it to work.
>
> 3) Better player logging information
> Showing what team they joined
> Showing who they killed
> Showing what weapon they used
> The reverse of those two who killed the player and with what weapon which
> should help routing out TK'ers.
>
> 4) Can we have a way of saying which weapons are available at any one
time?
> i.e. I only want people to be able to use the rifle.
>
> 5) This is more of a question leading onto a request. When I issue a
maplist
> command does it display what's on my local machine or what's on the
server?
> If its on the server is there any chance of being able to issue a map
change
> for the server by double clicking on the map name in that list that
appears.
>
> 6) A Demo facility
>
> 7) Commands to individual players such as
> T 3 <Chat string>
> Meaning Talk to player 3.
>
> 8) A way to prevent people from going to spectator mode (handy to prevent
> those people who just like to get the occasional spying session in when in
a
> match mode).
>
> 9) One that all developers hate (me included) documentation on all the
> commands and variables. (ok stop laughing :)
>
> Some of those are more developments and your TOR probably means its out of
> scope, but maybe there is an odd one that could be implemented. If out of
> all of them I would like to see 1, 2 & 3 the most.
>
> Cheers,
>
> Hazzie.
>
> -----Original Message-----
> From: Ryan C. Gordon [mailto:icculus at clutteredmind.org]
> Sent: 12 October 2002 01:54
> To: mohaa at icculus.org
> Subject: [mohaa] bf1942 and mohaa updates.
>
>
>
> > is there a linux-bf1942 mailing list that perhaps we can join? to speak
> > about it :)
>
> Your wish is my command.
>
> Send a blank email to bf1942-subscribe at icculus.org to get on the list.
>
> (Note that the linux version is NOT done yet, so there isn't much to talk
> about.  :)   But better than to talk on the MOHAA list.)
>
> But since this IS a mohaa list, let's talk about that.
>
> I'm going to be looking at the expansion pack code soon (contracts were
> FedEx'd today), so if you've got any requests, please state them now, and
> I'll see what I can get in there.
>
> --ryan.
>
>
>
>