Complete.Org: Mailing Lists: Archives: freeciv-dev: January 2001:
[Freeciv-Dev] Re: [PATCH] Unit movement
Home

[Freeciv-Dev] Re: [PATCH] Unit movement

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: Raimar Falke <hawk@xxxxxxxxxxxxxxxxxxxxxxx>
Cc: freeciv development list <freeciv-dev@xxxxxxxxxxx>
Subject: [Freeciv-Dev] Re: [PATCH] Unit movement
From: Thue <thue@xxxxxxx>
Date: Sat, 13 Jan 2001 15:25:55 +0100

> > Dry-run is a bad idea, IMO. When doing AI calculations you need to test
> > lots of moves (just imagine finding a goto route), and asking the server
> > over a slow internet connection per consideration is not an option. Just
> > copy the 50 lines of code that do the check, dammit! :) Maybe put it into
> > common if you
>
> The conditions are unfortunately wide spread
> (unithand:handle_move_unit,unithand:handle_unit_enter_hut,
> unithand:handle_unit_move_request,
> unithand:handle_unit_establish_trade, unittools:can_unit_move_to_tile,
> unittools:try_move_unit, unittools:do_airline,
> unittools:move_unit). These methods consists of 585 lines in the
> unpachted version. 3/4 of these lines where checks (=438 lines).

I think you only need the code in can_unit_move_to_tile().

-Thue



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