Complete.Org: Mailing Lists: Archives: freeciv-ai: May 2003:
[freeciv-ai] Re: improve diplomat logging + bugfix
Home

[freeciv-ai] Re: improve diplomat logging + bugfix

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: "Per I. Mathisen" <per@xxxxxxxxxxx>
Cc: freeciv-ai@xxxxxxxxxxx
Subject: [freeciv-ai] Re: improve diplomat logging + bugfix
From: Gregory Berkolaiko <Gregory.Berkolaiko@xxxxxxxxxxxx>
Date: Tue, 6 May 2003 13:06:50 +0100 (BST)

On Tue, 6 May 2003, Per I. Mathisen wrote:

> On Tue, 6 May 2003, Gregory Berkolaiko wrote:
> > > -  time_to_dest /= ut->move_rate;
> > >    time_to_dest *= (time_to_dest/2); /* No long treks, please */
> > >
> > >    /* Almost kill_desire */
> > >    want = (p_success * gain - p_failure * loss) / 100
> > > -         - SHIELD_WEIGHTING * time_to_dest;
> > > +         - SHIELD_WEIGHTING * (time_to_dest / ut->move_rate);
> > >
> > > If time_to_dest is == ut->move_rate, the penalty for long treks is never
> > > applied, leading to ballooning want in this case.
> >
> > You logic escapes me.
> >
> > If
> >     time_to_dest is == ut->move_rate
> > it means the diplomat can reach the city in one move. So it's nice and
> > convenient to bribe. Why is it any worse than any other city which we
> > can reach in one move?
> 
> It isn't so much about ttd == move_rate, but rounding the results too
> early. A penalty which was meant to be there didn't kick in.

Huh?  Why do you want to penalise city which is 2 moves away more than a 
city 2 (sic!) moves away.  If the only difference is that in the second 
city the diplomat would have some moves left.  But if it does the bribing 
he would have no moves left anyway!  And would probably be dead too!

G.



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