Re: [Warzone-dev] Why do we allow changing of ports on releases?

On 5/4/09, Kreuvf wrote: > Dennis Schridde wrote: > > OBJECTION! > > > > There are various valid reasons to use different hosts and ports, incl. > > firewalls, tunnels, forwards, private games and possibly others. > > > > --DevU > > I second this. Additionally this type of functionality has

Re: [Warzone-dev] Why do we allow changing of ports on releases?

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Dennis Schridde wrote: > OBJECTION! > > There are various valid reasons to use different hosts and ports, incl. > firewalls, tunnels, forwards, private games and possibly others. > > --DevU I second this. Additionally this type of functionality has

Re: [Warzone-dev] Why do we allow changing of ports on releases?

Am Sonntag, 3. Mai 2009 22:56:09 schrieb bugs buggy: > Is there any valid reason why we allow the masterserver port and the > gameserver port to be changed via the config file? > > I can understand the masterserver name, since that could change, but > the ports shouldn't be able to be switched to s

[Warzone-dev] Why do we allow changing of ports on releases?

Is there any valid reason why we allow the masterserver port and the gameserver port to be changed via the config file? I can understand the masterserver name, since that could change, but the ports shouldn't be able to be switched to something else IMO. If no objections, I plan to disable that f