[Freeciv-Dev] Re: (PR#4387) The Return of the Rand() Moves

["rwetmore@xxxxxxxxxxxx" <rwetmore@xxxxxxxxxxxx>]

This behviour should be optional, i.e. one should be able to turn it on or
off depending on how one wants to play the game.

Whether or not the AI deals with rand() moves correctly or just always
assumes a stall, is independent and something the AI team can decide on
their own.

Certainly, flushing moves for real players that try this is *VERY* bad.
The attempt should fail with no side effects for real players when the
option is turned off, just like moving into invalid terrain.

Cheers,
RossW
=====

Per I. Mathisen wrote:
> On Tue, 10 Jun 2003, Raimar Falke wrote:
> 
>>>Unfortunately, I really don't see a way of computing the real average time
>>>in PF.
>>
>>To clarify this: it is easy to calculate the weighted cost of a single
>>step if you have a "concrete" state (turn and moves left are
>>integers). However after the first step such you don't have this. You
>>have something like (turn=0,moves_left=1.47). So it is hard/imopssible
>>to calculate the weighted cost of the next step.
> 
> 
> I've gone back and reread the debate about rand() movement. I think it is
> time to remove rand() moves. Clearly pf does not handle it as effortlessly
> as it was advertised back then and which was part of the reason why the
> debate died off.
> 
> So I repeat the suggest that seemed to be the majority opinion at the
> time: The rand() test is replaced by FALSE iff moves_left != move_rate. So
> attempting to move into terrain with move_cost > moves_left merely causes
> you to waste your remaining movement points in this case.
> 
>   - Per
> 
> 
> 
>