Complete.Org: Mailing Lists: Archives: freeciv-dev: June 2003:
[Freeciv-Dev] Re: TECH_(UN)KNOWN problems in client diplomat code.
Home

[Freeciv-Dev] Re: TECH_(UN)KNOWN problems in client diplomat code.

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: freeciv-dev <freeciv-dev@xxxxxxxxxxx>
Subject: [Freeciv-Dev] Re: TECH_(UN)KNOWN problems in client diplomat code.
From: "Per I. Mathisen" <per@xxxxxxxxxxx>
Date: Mon, 30 Jun 2003 13:57:01 +0000 (GMT)

On Mon, 30 Jun 2003, Bursig Rafal wrote:
> When I open meeting with other player, I can offer him all
> my tech but I know ( I run other client) that most of them he has.

Correct. This is because you do not know what techs he already has.

> I use such code but it don't work when we have no info about other
> player techs (without embassy).
>
> if (get_invention(pPlayer0, i) == TECH_KNOWN &&
>   (get_invention(pPlayer1, i) == TECH_UNKNOWN ||
>    get_invention(pPlayer1, i) == TECH_REACHABLE)) {
>
> Should client block tech exchange ability when we haven't emabssy with
> other player ?

No. When you don't have embassies to each other, you can give away techs
to the other player but not request them nor filter away techs he already
has.

(We might keep a tab on what we can reasonably expect player X to know
about player Y's techs, and send that. Player X knows that player Y has
tech Z if he gave it to him. This way this tech can be filtered away from
the list of techs. But instead of going to such contortions, I'd rather
either bad tech exchange w/o embassy or give knowledge of techs w/o
embassy.)

  - Per



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