Complete.Org: Mailing Lists: Archives: freeciv-dev: August 2001:
[Freeciv-Dev] Re: Server cmd line: set var used to mean set var 0
Home

[Freeciv-Dev] Re: Server cmd line: set var used to mean set var 0

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Arien Malec <arien_malec@xxxxxxxxx>, freeciv-dev@xxxxxxxxxxx
Subject: [Freeciv-Dev] Re: Server cmd line: set var used to mean set var 0
From: Thue <thue@xxxxxxx>
Date: Fri, 3 Aug 2001 22:04:27 +0200

On Friday 03 August 2001 21:58, Arien Malec wrote:
> Until very recently, I used to be able to use:
>
> set huts
>
> on the server command line, which the server would interpret as:
>
> set huts 0
>
> This no longer works with latest CVS. I assume this is related to the
> recent patches disabling, then re-enabling the set var=n behavior.
>
> I don't know if the shortcut described above was a feature or a bug,
> but it was convenient....
>
> Arien

It was disabled intentionally.
It used to be that when the server couldn't read something that 
should be a number it assumed the value was 0. But this meant that all 
kinds of typos could result in setting a value to 0.

-Thue


[Prev in Thread] Current Thread [Next in Thread]